SOVEX
CBDC Data Centers Sovereign AI Tokenization Deep Tech Architecture About Team Request access
Tokenization / Asset classes / Funds and private credit

Funds and private credit.

Fund units and private-credit instruments carried as programmable ledger objects — where subscription, servicing, waterfalls, and redemption execute as encoded logic rather than spreadsheet-and-email operations. The fund administrator's book and the register are the same object.

A fund unit is a live claim with its economic terms attached, not a line in an administrator's file

Ownership, class rights, and transfer restrictions travel with the unit as enforceable attributes on the ledger.

01

Share classes as encoded rights

Management-fee terms, hurdle rates, and distribution preferences differ by class and are written into each class as logic the servicing engine reads. A class's economics cannot drift from what investors were sold.

02

Subscription and NAV strike

Subscriptions are recorded against a NAV struck at a defined ledger height, giving an exact, non-repudiable link between capital in and units issued. The strike price and the allotment are one entry.

03

Transfer eligibility enforced

Accreditation, jurisdiction, lock-up, and side-letter constraints are enforced at transfer time, so an ineligible secondary transfer fails rather than requiring unwinding. The whitelist is the instrument, not a separate checklist.

04

Register as source of truth

The unit register is the administrator's book, eliminating the reconciliation between transfer agent, administrator, and custodian that today produces breaks. There is one holder record for everyone to read.

Commitments, drawdowns, and distributions run as programmable capital flows

The full commitment lifecycle is modeled on-ledger so that called, funded, and uncalled amounts are always a current state.

01

Commitment tracking

Each investor's total commitment, drawn amount, and remaining uncalled capital are ledger states updated by every call and return. There is no separate capital-account spreadsheet to reconcile against the register.

02

Atomic drawdowns

A capital call moves committed CBDC and updates the investor's funded position atomically, so a call is never recorded as met while the cash is still in flight. Defaulting investors are identifiable at the moment of failure.

03

Recallable distributions

Return-of-capital and recallable distributions adjust remaining commitment according to the encoded LPA terms, keeping recycling provisions consistent with the documents. Recallable amounts are tracked, not remembered.

04

Equalization on late close

Subsequent-close equalization interest and true-up flows are computed from the same encoded terms across all investors, removing bespoke manual math per closing. Late-comers are equalized by rule.

Loans and private-credit instruments carry their servicing schedules as executable terms

Interest accrual, amortization, and covenant states are native to the instrument, so servicing is deterministic and the loan tape is always current.

01

Encoded amortization

Principal schedules, interest bases, PIK toggles, and step-ups are written into the loan and executed by the servicing engine on schedule. The loan tape is generated from the instrument, not maintained beside it.

02

Deterministic accrual

Interest accrues against the encoded rate and day-count, giving every holder and auditor an identical accrued figure at any ledger height. Accrual disputes become impossible to sustain.

03

Covenant and rate resets

Floating-rate resets and margin ratchets tied to covenant tests update the instrument's terms as encoded conditions are met. A breach or a step is a ledger event with a timestamp, not a later discovery.

04

Participations and syndication

Loan participations and syndicated tranches are modeled as native sub-claims, so each participant's economics and voting rights are tracked without a lead-bank ledger of record. Secondary sales of participations settle atomically.

Distribution waterfalls execute as logic, not as a quarterly modeling exercise

Priority of payments, hurdles, and carry are encoded once and applied identically every period, with the calculation itself auditable.

01

Priority of payments

Senior fees, preferred return, return of capital, and catch-up execute in encoded sequence against available cash. The waterfall runs the same way every time, removing period-to-period modeling drift.

02

Carry and clawback

Carried interest accrues under the encoded hurdle and catch-up terms, with clawback exposure tracked as a running ledger state. The GP's carry and the LPs' clawback claim are two views of one computation.

03

Hurdle and IRR gates

Preferred-return hurdles and IRR gates are evaluated from the ledger's own cash-flow history, so the trigger for a tier is derived from settled facts. There is no external cash-flow file to trust.

04

Distribution atomicity

Once computed, distributions to every investor settle atomically in CBDC against the register snapshot, so no investor is paid on stale ownership. The payout and the entitlement are the same event.

Reporting, oversight, and residency are structural properties of the fund's ledger

Investors, auditors, and regulators verify against one tamper-evident record while the fund's data stays within its jurisdiction.

01

Investor reporting from source

Capital-account statements and position reports are derived directly from the ledger, so what an investor sees reconciles by construction to what the fund holds. Reporting is a read, not a reconstruction.

02

Auditor read access

Fund auditors verify holdings, flows, and waterfall math against the hash-chained record without needing administrator extracts. The audit trail is continuous rather than assembled at year-end.

03

Post-quantum instrument integrity

Long-lived closed-end vehicles are signed under ML-DSA-65 so that unit authenticity and servicing history remain verifiable across the fund's full term. The instrument's provenance outlives classical cryptography.

04

Jurisdictional residency

Investor identity data and the register reside within the mandated jurisdiction, keeping sensitive LP information under domestic control. Cross-border access is granted explicitly, never assumed.

Build it sovereign.

Talk to us about funds and private credit in a sovereign deployment.