Keep tokenized assets compliant for life.
Every holder provably eligible, re-screened against live sanctions data, and blocked on-chain the moment they're not, and your firm never touches a single piece of investor PII.
● watching mempool for WRIT-001 transfers…
An eligible holder, a compliant transfer. Settled on-chain in one block, and the issuer never touched a passport.
Tokenizing the asset is easy. Staying compliant for its entire life is the blocker.
The honeypot
Conventional compliance forces the issuer to custody a mountain of investor PII: passports, accreditation, addresses. The data you collect to be compliant becomes the thing that gets you sued. It's a board-level reason institutions stall on tokenization.
Point-in-time KYC fails
Sanctions lists update. Accreditation lapses. Jurisdictions change rules. “Pass KYC once, you're in forever” is exactly the failure regulators keep fining firms for. Real compliance is a runtime engine, not a checkbox.
One compliance layer, across the asset's entire on-chain life.
01Prove privately
The investor proves eligibility in zero-knowledge: accredited, in-jurisdiction, not sanctioned. No document ever leaves their device.
02Gated on-chain
A signed credential lands on-chain. Every transfer is checked by a recipient-aware CEP-78 filter and denied by default.
03Re-screened at runtime
An autonomous agent re-screens holders against live sanctions and accreditation data — not a one-time check — and revokes the credential on-chain the moment a holder no longer qualifies.
04Provable to regulators
Any single compliance fact is provable to a regulator on demand via selective disclosure, without exposing the book.
A sanctioned wallet tries to receive the bond. Writ blocks it on-chain. Nobody ever saw their name.
The recipient was an active holder until a sanctions list updated. The agent re-screened, revoked the credential autonomously, and the very next transfer reverts on-chain, fail-safe by default. The enforcement is real; the identity is invisible.
A walkthrough of the real mechanism — the same recipient-aware CEP-78 filter that reverts a sanctioned transfer live on Casper testnet. Press the button.
● watching mempool for WRIT-001 transfers…
An eligible holder, a compliant transfer. Settled on-chain in one block, and the issuer never touched a passport.
No honeypot. Real continuity. On-chain enforcement.
Investor PII
Issuer custodies passports & accreditation docs, a breach lawsuit waiting to happen
Never custodied. Eligibility proven in zero-knowledge
Screening
Point-in-time KYC: pass once, in forever
Runtime re-screening against live data, by an autonomous agent
Enforcement
Off-chain checks and trust
Real on-chain CEP-78 transfer filter, denied by default
“You can't lie to it.”
Every eligibility decision is published as a proof anyone can verify. A false attestation can be challenged on-chain, and a quorum that signed it gets its bond slashed. The expensive cryptographic verification is paid only in a dispute, never on the happy path.
Security holds as long as the verifier quorum is honest or any single honest watcher challenges a bad attestation during the dispute window — a 1-of-N trust model the issuer can backstop itself.
Compliance is the pick-axe every RWA vertical needs.
Writ doesn't pick a vertical. It owns the job every vertical has to solve.
The honest claim, stated precisely.
Eligibility is proven in zero-knowledge, verified by a threshold of autonomous agents. The chain stores signed credentials, enforces compliance at every transfer via a native CEP-78 filter, and exposes published proofs for on-chain fraud challenge, with off-chain selective disclosure to regulators.
We never claim on-chain SNARK verification. On-chain pairing verification isn't cost-viable on Casper today, so Writ verifies off-chain and commits on-chain, and says so plainly. Honesty reads as senior.
ERC-3643-style compliance, native to Casper.
Casper has joined the ERC-3643 Association, the standards body for compliant RWA tokenization. Writ brings that institutional security-token model — identity, claims, compliance rules, transfer restrictions — to Casper's native account and weighted-multisig model, and is built to pay for live compliance data on demand. It sits dead-center on Casper's RWA and compliant-privacy thesis.