Living Instruments·Tokens that know what they own·● Pay what they earn·Prove what they claim·Respond to what happens·Living Instruments·● Pay what they earn·
PROOF://LIVING INSTRUMENTS · what makes a token alive · the 4 properties
Tokens that pay. Tokens that prove. Tokens that respond.
A living instrument is a token that knows what it owns, pays what it earns, proves what it claims, and responds to what happens in the world. The first financial instrument in history where every property is verifiable on-chain without trusting any intermediary.
§ The four properties
⬡
Knows what it owns
Every living instrument is backed by a verified on-chain record of its underlying asset. The title, the registry entry, the compliance proof. The token itself contains the claim to what it represents. Not a PDF in a data room — an on-chain attestation anchored to the asset.
◎
Pays what it earns
When the asset generates income — a horse wins a race, a carbon credit is certified, a property collects rent — the distribution fires automatically in JupUSD. No fund administrator. No quarterly statement. The yield is on-chain and auditable.
≡
Proves what it claims
Every claim made by the instrument — yield rate, asset value, certification status — is backed by an ORBITAL oracle receipt. The prediction was anchored before the outcome. The claim cannot be backdated.
↻
Responds to what happens
When the world changes — a certification lapses, a compliance deadline passes, a market event triggers — the instrument responds automatically. Transfer restrictions activate. Yield pauses. The instrument is alive to its context.
§ A living instrument vs a dead one
Dead instrument (current standard)
Living instrument (PROOF)
What backs it
A PDF in a data room. Trust the issuer.
What backs it
On-chain attestation linked to asset registry. Verifiable by anyone.
How yield distributes
Wire transfer quarterly, if and when the administrator decides.
How yield distributes
Automatic JupUSD distribution when the underlying event occurs.
Claim verification
Audit report from a firm you have to trust. No on-chain proof.
Claim verification
ORBITAL receipt anchored before outcome known. Chain verifiable.
Compliance enforcement
Lawyers. Manual checks. 90-day lock by agreement.
Compliance enforcement
Token-2022 transfer hook. KYC whitelist on-chain. 90d lock automatic.
NAV tracking
Monthly NAV statement from the fund administrator.
NAV tracking
Daily on-chain NAV via oracle feed. Auditable at any block height.
§ The mass primitives — how a living instrument is built
Entity
The legal container. SPV formed in the appropriate jurisdiction. Delaware series LLC, Cayman SIB, Próspera ZEDE. The token has a legal owner before it has investors.
Active
Ownership
Solana Token-2022 transfer hook. KYC whitelist enforcement on every transfer. 90-day lock periods. 499 max holder cap for Reg D compliance. The token knows who can hold it.
Pending keypair
Fiscal
Interest-bearing mint at configured yield rate. JupUSD distributions fire automatically on certification events or quarterly schedule. 25bps transfer fee. The token pays when the asset earns.
Pending keypair
Identity
ProofID: permanent_delegate with 3-of-5 compliance multisig. Sumsub KYC. Chainalysis AML. Reusable credential across all PROOF instruments. The token knows its holder.
Pending keypair
Consent
Confidential transfer with ZK proofs. Amount-hidden above 10k JupUSD threshold. Investor opt-in. GDPR-compliant privacy for institutional capital. The token respects its holder.
Pending keypair
All mass primitives except Entity are gated on oracle keypair generation: solana-keygen new --outfile oracle-keypair.json
What makes it living: When Puro.earth registers the certification on its public registry, the ORBITAL oracle receipt resolves. The Fiscal primitive fires: JupUSD distributes to token holders. The Transfer Hook enforces KYC. The Identity primitive checks wallets against the Chainalysis feed. The Consent primitive keeps institutional transfer amounts confidential.
The oracle's prediction — that Puro.earth certification will confirm ≥1,000 tonnes of verified carbon removal — was anchored to the receipt chain before any company read the output. The prediction hash is immutable. The chain cannot be backdated. Verify this receipt →