The transfer agent for verified real-world assets
Talon runs everything that happens after an RWA is issued — coupons, dividends, redemptions.
- On pay date, re-verifies every holder’s Cleanverse identity
- Pays compliant wallets directly
- Escrows the rest per-beneficiary until they re-verify
No eligible holder forfeits. No ineligible holder gets paid.
Your coupon survived a compliance freeze. You did not have to.
- 0% entitlement forfeited (we counted)
- Frozen ≠ expired, on-chain
- Audit export your lawyer will actually like
The problem
Every RWA project stops at issuance.
Tokenizing the asset is the easy part. What happens after — coupons, dividends, redemptions — is still a spreadsheet and a wire transfer. And because Cleanverse identity is revocable by design, a holder who was verified on the record date can be frozen, or let their A-Pass expire, by the pay date. Every real distribution hits this eligibility drift. Almost nothing on-chain handles it.
Step 01
Record date
Holder is verified and fully entitled to the payout.
Step 02
Pass lapses
Frozen or expired mid-flight — not the holder's fault.
Step 03
Pay date
The payout is due — and the issuer is trapped.
Pay them anyway
You just paid an unverified party — a direct compliance violation the issuer personally answers for.
Regulatory breach
Withhold it
You seized value they earned while fully verified. That's confiscation — and it breaks trust in the asset.
Theft of entitlement
Both branches are wrong — so today, issuers simply don’t distribute on-chain at all. Talon resolves it: pay where compliant, escrow where not, and release per-beneficiary the moment they re-verify.
How it works
Four layers. One lifecycle.
From live cap table to paid-out coupon — every step on-chain, every step attributable.
- 1
Live Cap Table
Every A-Token transfer is indexed into a live register, and each wallet's A-Pass status is polled against the Cleanverse API — staleness shown, never hidden.
- 2
Corporate Action Declared
The issuer declares a coupon, dividend, or redemption against a record block. The entitled holder set is committed on-chain as a running hash.
- 3
Pay-Date Re-Verification
At execution, every holder's eligibility is checked live. Verified on the record date is a claim — verified on the pay date is a payout.
- 4
Payout or Escrow
Still-verified wallets are paid directly. Lapsed wallets' entitlements are escrowed per-beneficiary — released the moment they re-verify.
Why it's different
Built for the moment every other project ignores.
Eligibility drift happens between the record date and the pay date — after the demo ends. Talon is the machinery for exactly that window.
Per-beneficiary escrow, never pooled
Every entitlement sits in its own sub-ledger under the holder's name. Release is just the real transfer retried — Cleanverse itself decides when the wallet is eligible again.
Frozen is not expired
A sanctioned wallet and a lapsed credential are different events. Each escrow is tagged with the actual on-chain revert reason — the audit trail never conflates them.
0% forfeited
Value earned while verified is never clawed back and never lost to expiry. The contract has no adminForfeit function at all.
Audit-ready by default
Every payout and every release exports with Travel-Rule attribution and the stored Cleanverse report — per beneficiary, per transaction hash.
Built on
Standing on verified rails.
Talon doesn't re-implement compliance — it composes it. Identity, assets, and settlement come from infrastructure that was built to be trusted.
Contracts deployed & frozen · Monad testnet
Watch a frozen holder get paid — legally.
The demo runs the full drift-and-recovery loop on real contracts: a holder gets frozen mid-distribution, doesn’t panic, keeps their entitlement safe in escrow, and claims it the second they re-verify — with a receipt so airtight the auditors get bored. No coupons were harmed in the making of this demo.