pilot-lynkscap

Pilot Ozmium x LynxCap

Please enable JavaScript in your browser to complete this form.

- Step 1 of 9

SECTION 1 — LynxCap & Pilot Contact

Thank you for your interest in exploring an Ozmium pilot. The purpose of this short questionnaire is to help us understand LynxCap’s current product structure, investor/cashflow workflows and operational requirements so that we can calibrate the pilot around a real business need rather than building a generic technology demonstration. We are particularly interested in understanding how coupon or other periodic cashflows are currently calculated, allocated, distributed and reconciled for tokenized instruments. Please do not provide confidential investor information, personal data, wallet private keys, passwords, banking credentials or other sensitive information through this form. Aggregated, anonymized or sample data is sufficient at this stage.

1. Company Name *

2. Website / URL

3. Company Address

Address Line 1

Address Line 2

City

State / Province / Region

Postal Code

Country

Phone

3. Your name *

First

Last

4. Your role / function *

5. Email *

6. Other stakeholders who should be involved in the pilot

Investment / Fund Management
Operations
Finance
Legal / Compliance
Technology
Tokenization / Digital Assets
Investor Relations

SECTION 2 — Instrument to Be Considered for the Pilot

7. Which LynxCap instrument would you recommend using as the basis for the pilot? *

If “Other”, please specify *

8. Please briefly describe the instrument *

9. How is the instrument structured? *

Single tranche
Senior / Junior
Multiple seniority levels
Other waterfall structure
Other
Not applicable

10. What is the coupon / yield structure? *

Fixed coupon
Variable coupon
Fixed + variable components
Interest linked to another reference
Other

11. Coupon frequency

12. Approximate number of token holders for the selected instrument *

13. Approximate number of distribution channels

14. Which channels currently distribute / make the instrument available?

LynxCap directly
YouHodler
Tokinvest
Institutional / private distribution
Other digital-asset platform
Other
Not applicable

SECTION 3 — Current Coupon Lifecycle

We would like to understand what happens today from the moment a coupon becomes due until all eligible holders have been paid.

15. Please describe the current coupon-payment process from start to finish. *

16. Where is the authoritative record of the instrument’s terms maintained?

Legal / offering documentation
Internal LynxCap system
Spreadsheet
Tokenization platform
Smart contract
Custodian / administrator
Other

17. Where is the authoritative record of token holders / investor positions maintained?

LynxCap internal records
Tokenization platform
Blockchain / smart contract
Custodian
Distribution platform
Transfer agent / administrator
Multiple systems
Other

18. What determines who is entitled to a coupon?

Token balance at record date
Investor register
Custodian records
Platform balance
Other methodology

19. How is the record date determined?

20. How is coupon entitlement currently calculated?

21. Are there different coupon calculations by tranche, investor type or other category? *

22. If yes, please briefly describe the logic. *

SECTION 4 — Transfers, Eligibility & Exceptions

23. Can token ownership change between the coupon period and the record date? *

Yes
No
Don't know

24. If yes, how is the coupon entitlement determined when tokens have changed hands?

25. Are there investor eligibility restrictions that affect coupon payments?

Jurisdiction
Investor classification
KYC/AML status
Holding restrictions
Distribution-channel restrictions
Sanctions / compliance status
None
Other

26. How are exceptions currently handled?

Manual review
Spreadsheet
Internal system
Custodian / administrator
Distribution platform
Other

27. What are the most common operational exceptions?

Incorrect holder balance
Failed payment
Missing investor data
Ownership transfer close to record date
Eligibility issue
Calculation discrepancy
Payment reconciliation issue
Other

SECTION 5 — Payment Execution

What 7 What

29. What payment rails are currently used?

SEPA
SWIFT
Bank transfer
Custodian payment
Stablecoin / digital asset
Other

30. How are payment instructions generated?

Manually
Spreadsheet
CSV / payment file
API
Internal system
Bank platform
Other

31. Is payment approval required before execution? Field type: Yes / No

32. If yes, please briefly describe the approval workflow.

SECTION 6 — Reconciliation & Reporting

33. How is the coupon payment reconciled today?

34. Which systems or records need to be reconciled?

Legal instrument terms
Investor register
Token balances
Distribution platform
Bank payments
Custodian records
Accounting system
Internal spreadsheet
Other

35. What reporting is required after a coupon payment?

Investor statements
Payment confirmation
Internal reconciliation report
Accounting report
Compliance report
Audit trail
Issuer report
Other

36. How important is a complete, immutable audit trail of each cashflow event?

Critical
Very important
Important
Useful
Not currently a priority

37. What is currently the most time-consuming part of the coupon-payment process?

SECTION 7 — Pain Points & Desired Outcomes

38. What are the three biggest challenges LynxCap faces today when managing tokenized security cashflows? *

39. What would you most like Ozmium to improve? *

Third Choice
Investor entitlement calculation
Token-holder reconciliation
Eligibility management
Payment preparation
Payment orchestration
Reconciliation
Audit trail
Investor reporting
Multi-channel distribution
Automation
Exception management
Scalability
Other

40. If the pilot successfully solved one operational problem for LynxCap, what would be the most valuable one? *

41. How would you measure the success of the pilot?

Reduce manual work
Reduce reconciliation time
Reduce errors
Increase transparency
Improve auditability
Automate coupon calculations
Automate payment preparation
Support multiple distribution channels
Support additional tokenized instruments
Improve investor reporting
Other

42. Please provide any quantitative indication that could help us estimate the potential impact.

Examples: • Current hours per coupon cycle • Number of people involved • Number of investors • Number of transactions • Number of exceptions • Reconciliation time • Number of instruments expected to be supported Please use aggregated figures only.

SECTION 8 — Data & Integration

43. What data could LynxCap provide for the pilot?

Instrument terms
Sample token-holder positions
Anonymized investor records
Token balances
Historical coupon calculation
Historical payment data
Payment instructions
Reconciliation report
Other

44. Preferred data format

CSV
Excel
JSON
API
Database export
Other

45. Does LynxCap currently have APIs available for relevant data?

Yes
No
Not sure

46. If yes, which systems expose relevant APIs?

47. Is a sandbox / test environment available?

Yes
No
Not sure

48. Are there technical or security requirements that Ozmium should take into account?

SECTION 9 — Pilot Preferences

49. Which pilot approach would LynxCap prefer?

A. Synthetic Data Use a LynxCap-modeled instrument and completely synthetic holder data.
B. Anonymized Data Use an existing LynxCap instrument with anonymized / aggregated holder data.
C. Controlled Real Data Use a limited real instrument / dataset under appropriate controls.
D. Not yet determined

50. What would LynxCap consider the minimum acceptable outcome from the pilot?

51. Which part of the workflow should the pilot prioritize?

Instrument configuration
Holder / ownership data ingestion
Eligibility
Coupon calculation
Allocation
Payment instruction generation
Payment execution
Reconciliation
Audit trail
Reporting
Other

52. Would LynxCap be interested in testing the pilot with a representative existing instrument rather than a purely hypothetical structure?

Yes
No
Maybe

53. What constraints should we consider when defining the pilot?

Regulatory
Legal
Data privacy
Internal approvals
Technology
Security
Existing service-provider relationships
Timing
Other