Tokenization Engine.

Move fund units from static registers and spreadsheets into controlled smart contracts. Manage approved holders, transfers, NAV events, fees, and distributions through a live, auditable ownership layer.

Live stakeholder registerProgrammable controlsAPI ready

Tokenized units and a live register.

The core implementation provides the programmable ownership layer. Additional services can connect onboarding, settlement, exchange distribution, reporting, and managed administration.

Core engine

Tokenization

  • ✓ Fund and share-class configuration
  • ✓ ERC-6909 compatible unit architecture
  • ✓ Onchain stakeholder register
  • ✓ Whitelisting and transfer restrictions
Connected modules

Everything around the units

  • + Registry listing
  • + OmniClear settlement
  • + Exchange and distribution integrations
  • + NAV, fee, payout, and reporting workflows

Fund units that can move, settle, and enforce terms.

A smart-contract register makes ownership state available as live data and allows approved actions to follow the same rules every time.

↔

Controlled secondary transfers

Approved investors can transfer units inside whitelisting, lockup, jurisdiction, and eligibility restrictions set by the fund.

⌁

Distribution ready

The unit structure can be connected to eligible regulated venues, brokers, and distribution channels subject to their own review.

▦

Live cap table

Subscriptions, redemptions, transfers, and balances update the same ownership record instead of creating another reconciliation task.

§

Programmable terms

Transfer restrictions, eligibility rules, lockups, and fee logic can be represented as enforceable controls rather than manual reminders.

One ownership record that stays current.

The register is structured data that approved systems and agents can read. Every ownership event can be linked to supporting evidence and a transaction record.

  • Whitelisted holder addresses
  • Share-class balances and percentages
  • Subscriptions, redemptions, and transfers
  • Timestamped audit evidence
HolderUnitsOwnership
0x7a…4b212,50022.4%
0x91…e088,25014.8%
0xd3…7c15,0008.9%
0x4f…a193,1205.6%
+ 48 more approved holdersExample data

Connect one unit standard to multiple channels.

A tokenized share class can be prepared for approved exchanges, brokers, marketplaces, and direct investor channels without maintaining separate ownership systems for each one.

Venue access, eligibility, and listing remain subject to each venue, regulator, jurisdiction, and product structure.

Your fundProgrammable units
01

Regulated exchanges

Connect eligible products to approved digital-security venues.

02

Broker distribution

Support structured integration with approved broker and wealth channels.

03

Direct investors

Onboard, whitelist, and service investors through the fund’s own experience.

Fund administration connected to programmable ownership.

The tokenization layer does not replace investment strategy, valuation governance, or regulated oversight. It removes repeated recordkeeping and allows approved workflows to operate against one source of ownership truth.

01

NAV events

Load approved asset values and fee inputs, then record the resulting NAV event against the relevant share class.

02

Fees and distributions

Apply approved fee logic and prepare management fees, performance fees, income distributions, or redemption proceeds.

03

Audit trail

Link ownership actions to timestamps, transaction records, approvals, and supporting documents for review.

Accept subscriptions through supported fiat or stablecoin rails.

Investors can use an approved payment method while the fund receives the currency and settlement format suited to its operating model.

Learn about OmniClear →
◎

Stablecoin subscriptions

Approved wallets can subscribe using supported stablecoins after the required identity, eligibility, and transaction-screening steps.

$

Fiat remains supported

Wire transfers and other approved bank-payment methods can coexist with onchain subscriptions and update the same fund record.

⚡

Shorter settlement paths

Where supported providers and compliance controls allow it, stablecoin settlement can reduce intermediaries and processing delays.

An engine an approved agent can actually operate.

Every important action should be available through a controlled programmatic interface—not trapped behind a dashboard. That allows a managed agent to operate the lifecycle while smart-contract and application controls enforce the limits.

01

Actions exposed as controlled calls

Fund setup, holder approval, unit issuance, NAV events, and distributions can be integrated into an orchestrated workflow.

02

Machine-readable register

Balances, positions, and ownership events can be consumed as structured data instead of extracted from PDFs.

03

Open interfaces

Standards-based RPC, REST, and event interfaces reduce dependence on a proprietary manual portal.

04

Guardrails enforced by the system

Eligibility, whitelisting, lockups, and approval rules remain effective even when an agent is executing the workflow.

From current register to live architecture in three stages.

01

Define the fund and controls

Map share classes, holder requirements, jurisdictions, transfer restrictions, fees, operational roles, and governance approvals.

02

Configure and test

Deploy the unit architecture in a controlled environment, connect the required workflows, migrate agreed data, and test expected and exceptional cases.

03

Go live under governance

Activate the production register, document operating procedures, monitor transactions, and phase in additional automation when the controls are proven.

Questions about tokenization.

The final legal, tax, regulatory, custody, and technical design must be confirmed with the fund’s qualified advisers and service providers.

What does tokenizing a fund unit change?

The legal and regulatory nature of the fund remains determined by its structure and jurisdiction. Tokenization changes the ownership and operational record by representing approved units and transfer controls in programmable infrastructure.

Do investors need a wallet?

Wallet-based holding can be supported for eligible investors, while a fund may also retain assisted or fiat-compatible processes. The right model depends on the legal structure, custody approach, investor base, and distribution channels.

How are transfers controlled?

Whitelisting, eligibility, lockups, transfer restrictions, approval gates, and monitoring can be enforced at the application and smart-contract layers. Exact controls are configured for the fund and its advisers.

Can the engine connect to existing administrators and custodians?

Yes. The implementation is designed around approved systems and counterparties. Integration scope depends on available APIs, files, operating procedures, security policies, and provider cooperation.

Can an AI agent operate the engine?

A managed agent can execute approved programmatic steps when access, permissions, limits, approvals, and audit logging are defined. Sensitive or unusual actions can remain subject to human approval.

Map the ownership register, workflows, and controls before choosing technology.

Peregrine can review the current structure and design a staged tokenization architecture around the fund’s actual legal and operating requirements.