ENCLAVES
How it works

Trust does not disappear when assets move on-chain. We design it instead.

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.

Layered trust architecture

Five layers, each addressing a distinct failure mode.

Law provides enforceability, cryptography provides constraint, process provides continuity. No single layer is sufficient on its own.

LAYER 1

Jurisdictional Legality

Each Enclave is anchored in a jurisdiction whose law recognizes SPV ownership, beneficial ownership, and digital signatures. The SPV is bankruptcy-remote from operational entities; the token ledger is contractually designated as the authoritative record of beneficial ownership.

Solves

Legal ambiguity in disputes, insolvency, cross-border claims.

LAYER 2

Verification Integrity

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.

Solves

Unilateral misrepresentation by issuer, custodian, or verifier.

LAYER 3

Economic Bonding

Enclave Operators bond ENCL proportional to asset value and Trust Class (α = 1–20%). Verifiers bond against their attestations. Slashing on proven fraud, gross negligence, or intentional misrepresentation turns dishonesty into capital loss.

Solves

Cost of fraud underpriced relative to fraud gain.

LAYER 4

Process Enforcement

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.

Solves

Discretionary issuance, governance backdoor, manual workaround.

LAYER 5

Transparency & Auditability

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.

Solves

Opaque issuance with no reputational permanence.

Asset issuance lifecycle

Issuance is gated, not granted.

A real-world asset becomes eligible for token representation only once legal authority, operational reality, and technical enforceability are all established.

  1. 01

    Pre-issuance qualification

    Asset must have clearly definable ownership, a verifiable custody or control model, and a legal framework that supports beneficial ownership held on behalf of asset owners.

  2. 02

    Jurisdiction & Enclave selection

    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.

  3. 03

    Asset registration

    Canonical record created: identifiers, jurisdiction, custody arrangements, valuation parameters, lifecycle constraints.

  4. 04

    Custody, control & legal verification

    Independent attestations from custodians, brokers, registrars, and legal counsel. No self-attestation; failure of any gate blocks issuance.

  5. 05

    Mint Authorization Check

    Smart contract evaluates all conditions atomically. Pass → ERC-3643 token minted with locked supply and anchored metadata. Fail → blocked, no override.

Authorization is emergent, not granted.

The platform composes individual attestations into a Mint Authorization Check. If any condition is unmet, issuance is blocked with no manual override, side channel, or negotiation. No single party — issuer, Enclave Operator, SPV, platform, or governance — can force a mint.
Post-issuance guarantees

Every transfer is gated by the Enclave.

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.

Transfer flow

  1. 1. Asset owner initiates transfer → the ERC-3643 compliance check queries the Identity Registry and the Enclave’s approval registry (administered by the Enclave Operator on behalf of the SPV).
  2. 2. Registry verifies recipient: KYC current, SPV–recipient contracts executed, no jurisdictional restriction, asset not suspended or in dispute.
  3. 3a. Approved → balance updates, log emitted, SPV register reflects new beneficial owner.
  4. 3b. Not approved → transaction reverts. No partial state, no pending claim.

Liquidity, without decoupling

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.

Jurisdiction framework

Jurisdictions are not interchangeable. Each Enclave names its own.

ENCLAVES’ initial framework spans seven jurisdictions selected for the strength of their legal systems, clarity of ownership frameworks, and relevance to institutional capital.

EU · MiCA

Lux / Ireland / NL SPV structures. Mature property and securities registries; cross-border judicial cooperation.

Initial focus · Securities, real estate

DIFC

Common-law jurisdiction within the UAE with DFSA Investment Token regime; independent courts; reciprocal enforcement.

Initial focus · Cross-border real estate

ADGM

Common-law free zone with FSRA virtual asset framework, recognized SPV and trust structures, dedicated digital asset licensing.

Initial focus · Cross-border, securities

Singapore

MAS Payment Services Act + SFA; recognized Variable Capital Company (VCC) for fund-like SPVs; strong rule of law.

Initial focus · Funds, commodities

United States

Asset-class-specific structures (Delaware LLC / statutory trust). Reg D / S / A+ for securities-classified tokens.

Initial focus · Treasuries, equities

Hong Kong

SFC licensing regime for virtual asset trading platforms; strong property and trust law; gateway to Asian capital markets.

Initial focus · Tokenized securities

United Kingdom · FCA

English law trust structures or limited companies as SPVs; deep case law on beneficial ownership; FCA oversight maturing.

Initial focus · Securities, structured products
Default SPVs operate inside each active Enclave; bespoke SPVs are supported on a separate onboarding track for institutional operators. Trust guarantees are identical.
Token standard

Why ERC-3643

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.

Glossary

Key concepts

The terminology used throughout the whitepaper and the platform.

Enclave

The unit of trust. An environment binding four things together: a jurisdiction, a legal entity (SPV) to hold title, a standardized operational process, and a defined scope of assets. Run by an Enclave Operator who bonds ENCL against their conduct.

Enclave Operator

The accountable party that runs an Enclave: onboards assets, bonds ENCL, approves transfers, and executes lifecycle events. Operationally and economically accountable; its bonded stake is slashable. Distinct from the SPV.

Enclave SPV

The jurisdiction-specific legal entity that holds title or custody rights within an Enclave. Bankruptcy-remote from operational entities; the legal anchor courts recognize.

SPV (Special Purpose Vehicle)

Legal entity that holds the asset on behalf of asset owners. Bankruptcy-remote. Operates under a defined jurisdiction.

Trust Class

Structural category (I–VI) describing how strongly an asset can be independently verified and enforced. Drives bonding and verification requirements.

Trust Score

Numeric (0–100) summary of an asset’s legality, verification, bonding, process compliance, and reputation. Decomposable and time-decaying.

Mint Authorization Conditions

The set of on-chain checks — verifications complete, Enclave Operator approval, SPV active, no encumbrances, ENCL stake bonded, cooling period elapsed — that gate ERC-3643 minting.

Public Trust Certificate

Standardized machine- and human-readable certificate exposing all trust metadata for a given asset.

Beneficial Ownership

The legal right to the economic benefits of an asset. In ENCLAVES, the token ledger is contractually designated as the authoritative record.

Bonding (α)

ENCL stake required of an Enclave Operator, proportional to asset value and Trust Class. Ranges from ~1% (Class I) to ~20% (Class V). Slashable on proven fraud.

Slashing

Forfeiture of staked ENCL on proven fraud, gross negligence, or intentional misrepresentation. Partial allocation to affected asset owners.

Stay close to the build

Monthly engineering, legal, and roadmap updates. No marketing filler.