ENCLAVES treats trust as something to be bounded and made provable across law, process, and code. Five layers, gated issuance, and a federated network of jurisdiction-anchored Enclaves.
A full walkthrough: an issuer tokenizes a Grade-A Dubai office tower, the Enclave operator reviews and approves it, the ERC-3643 token is minted on-chain, and the asset goes live for investors.
Law provides enforceability, cryptography provides constraint, process provides continuity. No single layer is sufficient on its own.
Each Enclave is anchored in a jurisdiction whose law recognizes enforceable ownership structures and digital signatures. The issuer holds legal title until tokens are sold; the SPV governs transfers; the token ledger is contractually designated as the authoritative record of ownership, so ownership conveyed by the token is enforceable under local law.
Legal ambiguity in disputes, insolvency, cross-border claims.
Trust Classes define the verification standard for every asset. Multiple independent parties — registrars, custodians, brokers, legal counsel — submit timestamped, signed Verification Events. Single-party fraud becomes structurally infeasible.
Unilateral misrepresentation by issuer, custodian, or verifier.
Enclave Operators bond ENCL proportional to asset value and Trust Class (α ≈ 1.5%–20%). Verifiers bond against their attestations. Slashing on proven fraud, gross negligence, or intentional misrepresentation turns dishonesty into capital loss.
Cost of fraud underpriced relative to fraud gain.
Token issuance is gated by Mint Authorization Conditions: complete verification stack, active SPV, no unresolved encumbrances, bonded stake, cooling period elapsed. Smart contracts enforce automatically. There is no override path.
Discretionary issuance, governance backdoor, manual workaround.
Every asset exposes a Public Trust Certificate: Trust Class, Trust Score, jurisdiction, SPV, verifications, stake, encumbrances, dispute history. Documents are hash-anchored on-chain so post-hoc alteration is detectable.
Opaque issuance with no reputational permanence.
A real-world asset becomes eligible for token representation only once legal authority, operational reality, and technical enforceability are all established.
Asset must have clearly definable ownership, a verifiable custody or control model, and a legal framework that supports token-conveyed ownership recognized under local law.
Every admitted asset is anchored to a jurisdiction through an Enclave SPV. Most issuers onboard into an existing Enclave’s default SPV. Operators needing bespoke structures follow the separate creation track — both meet identical standards.
Canonical record created: identifiers, jurisdiction, custody arrangements, valuation parameters, lifecycle constraints.
Independent attestations from custodians, brokers, registrars, and legal counsel. No self-attestation; failure of any gate blocks issuance.
Smart contract evaluates all conditions atomically. Pass → ERC-3643 token minted with locked supply and anchored metadata. Fail → blocked, no override.
A transfer the SPV does not recognize is not a transfer of ownership at all. The Enclave Operator administers an approval registry encoding the recipients the SPV will legally recognize, and the ERC-3643 compliance hook enforces it — the on-chain ledger and the SPV’s legal register cannot drift.
Pre-approval lets buyers complete KYC/AML and contract execution in advance, joining the approved recipient list so future transfers settle without delay. Approved marketplaces and custodians act as recognized intermediaries inside the Enclave’s compliance perimeter.
This is intentionally stricter than permissionless transfers. Allowing uncontrolled transfers would decouple the token from its legal meaning — recreating the issuer-claim problem ENCLAVES is designed to solve.
The two settle together but never merge. Stablecoin conveys no ownership and is never a substitute for the asset token — it only ever moves the cash that buys, services, and redeems it.
At primary issuance the buyer’s stablecoin payment and the asset-token transfer execute as one atomic transaction through an SPV-controlled escrow — either both legs settle or neither does. No interval where one party has paid and the other has not delivered.
Coupons, dividends, rent, and revenue share are paid to holders of record in stablecoin, pro rata. Redemption and exit proceeds settle in stablecoin too, sequenced so the token layer cannot move ahead of settlement.
Only stablecoins admitted through governance are used, matched to the Enclave’s currency — a US-dollar Enclave settles in a GENIUS-regime payment stablecoin, a euro Enclave in a MiCA-compliant e-money token such as EURC.
ENCLAVES’ initial framework spans seven jurisdictions selected for the strength of their legal systems, clarity of ownership frameworks, and relevance to institutional capital.
Lux / Ireland / NL SPV structures. Mature property and securities registries; cross-border judicial cooperation.
Common-law jurisdiction within the UAE with DFSA Investment Token regime; independent courts; reciprocal enforcement.
Common-law free zone with FSRA virtual asset framework, recognized SPV and trust structures, dedicated digital asset licensing.
MAS Payment Services Act + SFA; recognized Variable Capital Company (VCC) for fund-like SPVs; strong rule of law.
Asset-class-specific structures (Delaware LLC / statutory trust). Reg D / S / A+ for securities-classified tokens.
SFC licensing regime for virtual asset trading platforms; strong property and trust law; gateway to Asian capital markets.
English law trust structures or limited companies as SPVs; deep case law on beneficial ownership; FCA oversight maturing.
ERC-20 has no concept of identity-checked transfers. ERC-721 and ERC-1155 give you per-token semantics but no native compliance layer. ERC-3643 (T-REX) is the industry standard for permissioned security tokens: mandatory Identity Registry checks and a configurable Compliance module evaluated on every transfer.
Each asset is its own ERC-3643 contract instance — cloned via EIP-1167 minimal proxy by the platform’s token factory. That gives per-asset supply, per-asset state machine, per- asset compliance rules, and per-asset maturity. Fractional ownership is the ERC-20 base; the Enclave-approval enforcement rides on the ERC-3643 transfer-check hook.
ENCLAVES’ guarantees are designed to survive contact with real markets, real custodians, and real legal systems. ERC-3643 is the standard those systems already speak.
The terminology used throughout the whitepaper and the platform.
The unit of trust. A virtual environment drawn over one jurisdiction, binding an SPV that governs transfers, an operator that runs the process, the assets, and platform access into one accountable whole. Run by an Enclave Operator who bonds ENCL against their conduct.
The party that owns the real-world asset and holds legal title until a token is bought. It proposes the asset and sets intended parameters, but cannot mint, override verification, or control transfers.
The accountable party that runs an Enclave: onboards assets, bonds ENCL, approves minting once gates are green, and executes lifecycle events. Operationally and economically accountable; its bonded stake is the slashable stake. Distinct from the SPV.
The jurisdiction-specific legal entity that governs transfers within an Enclave — it approves who may hold or receive a token so every holder is a legally recognized owner. It is not the title holder and does not own the underlying asset; it acts as transfer-control and, where applicable, security-trustee entity.
Once a token is bought, ownership of the asset (or a defined fraction) passes to the holder and rides with the token. The token ledger is contractually designated as the authoritative record of ownership.
Structural category (I–VI) describing how strongly an asset can be independently verified and enforced. Drives bonding and verification requirements.
Numeric (0–100) summary of an asset’s legality, verification, bonding, process compliance, and reputation. Decomposable and time-decaying. Measures integrity and enforceability, not investment risk.
A second, independent measure of investment risk on the EU PRIIPs Summary Risk Indicator scale (1–7). Orthogonal to the Trust Score and deliberately kept out of the bonding formula.
The on-chain checks — verifications complete, Enclave Operator approval, SPV transfer-control active, no unresolved encumbrances, issuer’s unilateral control removed and holders’ interest perfected, ENCL stake bonded, cooling period elapsed — that gate ERC-3643 minting.
Standardized machine- and human-readable certificate exposing all trust metadata for a given asset, including which control (registry-locked, custody-locked, or security-backed) stands behind the token.
ENCL stake required of an Enclave Operator, proportional to asset value and Trust Class. On-chain defaults run 1.5% (Class I) to 20% (Class VI). Slashable on proven fraud.
Forfeiture of staked ENCL on proven fraud, gross negligence, or intentional misrepresentation. Proceeds split between harmed owners (pro-rata) and the protocol treasury.
Monthly engineering, legal, and roadmap updates. No marketing filler.