Permissioned tokens (ERC-3643)
Transfer restrictions enforced in the smart contract: identity, investor category, jurisdiction and holding limits checked on every transfer.
Flagship · RWA tokenization
Infrastructure for tokenized private markets.
We are building a platform for issuing and administering real-world assets on-chain, for private-market assets such as fund interests, private credit and real estate. Investor eligibility is enforced by the token itself, and every step from issuance to redemption leaves an auditable record.
Status: In development
The problem
Private-market assets are still administered through transfer agents, spreadsheets and email. Ownership records live in several places, secondary transfers can take weeks, and each one has to be checked against investor eligibility, jurisdiction and lock-up rules by hand. Putting the asset on a public token does not fix that by itself: an unrestricted token cannot control who is allowed to hold it.
How we approach it
Transfer rules are treated as part of the asset rather than a check performed around it. Tokens follow the ERC-3643 permissioned token standard, so every transfer is validated against on-chain identity and eligibility rules before it settles. Identity verification stays with specialist KYC and AML providers, issuers keep the enforcement controls a regulated instrument needs, and every state change is recorded so an administrator or auditor can reconstruct any position at any point in time.
Capabilities
What it is being built to do.
KYC/AML integration
Eligibility recorded as on-chain identity claims after verification by established KYC and AML providers, so personal data stays off-chain.
Issuer and agent controls
Freeze, forced transfer and recovery of a holder’s position after key loss, designed into the contracts from the first deployment.
Asset lifecycle management
Issuance, investor onboarding, transfers and redemption handled as one lifecycle, with the token register as the single record of ownership.
Cross-chain settlement
Settlement across more than one network without losing the eligibility check, which is the constraint most cross-chain designs drop.
Audit trail
Every mint, transfer, freeze and burn recorded with the party that authorised it, so reconciliation and audit work from evidence.
Lifecycle
The asset lifecycle.
01 OnboardIssuer, asset and rules
02 VerifyInvestor KYC/AML claims
03 IssuePermissioned tokens
04 TransferChecked on every move
05 AuditComplete event history
06 RedeemBurn and settle
Who it is for
Built for.
Asset managers and fund administrators
Running fund interests and investor registers on infrastructure that enforces eligibility automatically.
Issuers of private credit and real estate vehicles
Offering tokenized exposure while keeping the transfer rules regulators expect.
Banks and financial institutions
Evaluating tokenization with an architecture that can be reviewed before anything is deployed.
Fintech platforms
Adding tokenized products without building compliance logic from scratch.
Related
Built on this work.
Case study: RWA tokenization and cross-chain settlement
ERC-3643 permissioned token contracts and cross-chain settlement for real-world asset tokenization, built in Solidity and Hardhat for Luxembourg-focused products.
Blockchain
Protocol, contract and integration work for cases where shared state has to be provable - with the gas, finality and upgrade constraints designed in from the start.
Software Engineering
Web, mobile, SaaS and enterprise systems built on durable foundations - clear domain models, typed boundaries and tested paths.
Cloud & Infrastructure
Cloud architecture, migration, DevOps and platform engineering - designed for predictable cost, fast recovery and deployments that are boring on purpose.
FAQ
Questions we get asked.
Representing ownership of a real-world asset, such as a fund interest, a loan or a property, as a token on a blockchain. The token becomes the register of who owns what, and rules about who may hold or transfer it can be enforced by the smart contract itself.
ERC-20 tokens can be sent to anyone. Regulated instruments cannot. ERC-3643 keeps a familiar token interface but checks every transfer against on-chain identity and eligibility rules, and gives the issuer the recovery and enforcement functions regulated assets need.
No. Identity verification is done by specialist KYC and AML providers. The platform records the outcome as an on-chain eligibility claim, so personal data is never written to the blockchain.
Not yet. It is in active development, building on our engineering work on ERC-3643 permissioned tokens and cross-chain settlement. We are speaking with issuers and asset managers who want to shape the first deployments.
ZettaCore Labs builds technology. It is not a broker, exchange, custodian, transfer agent or investment adviser, and nothing on this page is an offer of securities or investment advice. Issuers remain responsible for the licences, offering documents and approvals their jurisdiction requires.
Shape it with us.
We are looking for design partners who will use it in production. Tell us about your programme and we will show you where it stands.