# Technical Implementation

Zodor's technical foundation rests on established Ethereum standards while introducing proprietary enhancements:

#### Standards in Use <a href="#standards-in-use" id="standards-in-use"></a>

| Standard             | Role                                                                                                      |
| -------------------- | --------------------------------------------------------------------------------------------------------- |
| **ERC-734 / 735**    | Modular identity profile + claim holder (Masque ID)                                                       |
| **ERC-780**          | Decentralized claim registry                                                                              |
| **ERC-3643 (T-REX)** | Compliant security tokens (`ZCET`, `ZIPT`, `ZEROC`, `ZIST`, per-asset Capital tokens)                     |
| **ERC-7943**         | Universal RWA adapter for DeFi composability                                                              |
| **ERC-4337**         | Account abstraction (smart wallets, paymaster, bundler)                                                   |
| **EIP-7702**         | Hybrid wallet `ZodorDelegateAccount` runs smart-wallet code in EOA context, preserving the user's address |
| **ERC-4626**         | Yield-bearing vault (`ZodorSecurityVault`) with NAV adjustment + non-transferable shares                  |
| **ERC-1167**         | Minimal-proxy clones for gas-efficient identity issuance                                                  |
| **ERC-1271**         | Smart-contract signature verification                                                                     |
| **ERC-7201**         | Namespaced storage layout for upgrade safety                                                              |

#### System Layers <a href="#system-layers" id="system-layers"></a>

The platform operates through five integrated layers:

1. **Identity Layer** `MasqueIdFactory`, `ZodorClaimIssuer`, `ZodorIdentityRegistry` manage decentralized identities with jurisdiction, tax domicile, and risk-score attributes.
2. **Claims Layer** Handles KYC, AML, accreditation, and ESG verification through cryptographic claims bound to the user's Masque ID. ZK proofs (Groth16) issued via `ZKKYCGate` allow privacy-preserving issuance.
3. **Compliance Layer**  `ZodorComplianceModule` enforces dynamic regulatory requirements (country caps, holding periods, OFAC) at the contract level, on every transfer.
4. **Token & Adapter Layer**  ERC-3643 tokens for the four verticals, plus per-asset Capital tokens deployed by `CapitalAssetFactory`. `ERC7943Adapter` exposes them to external DeFi without leaking compliance state.
5. **DeFi & Cross-Chain Layer**  `ZodorSecurityVault`, `ZodorPermissionedPool`, `ZodorCCIPBridge`, and `ZodorOFTAdapter` provide yield, liquidity, and cross-chain mobility under continuing compliance enforcement.

#### Account Abstraction Stack <a href="#account-abstraction-stack" id="account-abstraction-stack"></a>

| Component                                                    | Address (Maskade L1)                         |
| ------------------------------------------------------------ | -------------------------------------------- |
| `EntryPoint` (v0.7)                                          | `0xF7240284f8ed844C18D711A87E3888954e915f9E` |
| `ZodorAccountFactory`                                        | `0x234A800E585d45a22Abfe85483e4ae1395BD0a6b` |
| `ZodorPaymaster` (treasury sponsorship legacy / promotional) | `0xF3c742681Ba394F71ac051ABCF9102dBD8A8e0c3` |
| `SimplePriceOracle`                                          | `0xc343F722F5679B73D7AbC8cc7Ce0805107a86380` |
| `ZodorDelegateAccount` (EIP-7702)                            | `0xD6F01aaC273887f7886B550237D90B4eD36eB913` |
| `ZodorTokenPaymaster` (USDT/USDC/MASK gas)                   | `0xba0E6eA7663096D37B13eb006AFDCF01B9403da6` |

`ZodorTokenPaymaster` accepts USDT, USDC uses `SimplePriceOracle` (24 h staleness, 20% circuit breaker) to price gas, applies a 500 bps buffer, enforces a 5,000,000 gwei daily user cap; and supports a sponsored-address allowlist for promotional flows.

#### Toolchain <a href="#toolchain" id="toolchain"></a>

| Layer               | Tool                                                               |
| ------------------- | ------------------------------------------------------------------ |
| Smart contracts     | Solidity ^0.8.24, Foundry (test/fuzz), `forge script` (deploy)     |
| Identity            | ONCHAINID (ERC-734/735), ERC-3643 T-REX (composition, no lib dep)  |
| ZK circuits         | Circom 2.x + snarkjs, Groth16                                      |
| Account abstraction | ERC-4337 + EIP-7702, alto bundler, thirdweb SDK                    |
| Cross-chain         | Chainlink CCIP + LayerZero v2 OFT                                  |
| FHE                 | Zama fhEVM                                                         |
| Frontend            | Next.js 14 (PWA), TypeScript strict, `viem`                        |
| Mobile              | Flutter + thirdweb RN SDK                                          |
| Backend             | Node.js 20, Express + Apollo Server 4, MongoDB 8, AWS Lambda + ECS |
| Package manager     | pnpm workspaces                                                    |

Compiler / library pin: `solc = 0.8.24`, `via-ir` enabled, 200 optimizer runs. Uses **OpenZeppelin v4** (required by ONCHAINID).

#### Distinctive Approach <a href="#distinctive-approach" id="distinctive-approach"></a>

While aligned with public Ethereum standards, Zodor differentiates through:

* Hybrid EIP-7702 + ERC-4337 wallet UX
* Per-asset (rather than per-platform) ERC-3643 tokens through `CapitalAssetFactory`
* Three-mode privacy stack (ZK-KYC, Paillier, FHE) chosen per asset class
* Dual cross-chain (CCIP + OFT) for institutional optionality
* Stablecoin-paid gas through `ZodorTokenPaymaster` with on-chain price oracle and circuit breaker
* Reserve-proof oracle architecture (Path C) for institutional-grade verification without full on-chain transparency


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://whitepaper.zodor.io/system-architecture/technical-implementation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.