ESPERANTO (ESP) — System Design Document v1

Status: Foundation Phase | Date: March 2026 | Version: 1.0

1. EXECUTIVE SUMMARY

1.1 What is ESP?

ESPERANTO (ESP) is a globally-referenced asset-referenced token (ART) under MiCAR that maintains purchasing power parity across five economic dimensions: consumer price inflation (CPI), foreign exchange volatility, commodity prices, productivity, and crypto market dynamics. Unlike single-currency stablecoins (USDC, USDT) or regional alternatives (EUROC), ESP tracks a decentralized index of real economic value rather than any single nation’s currency.

Purpose: Enable frictionless cross-border settlement, long-term savings vehicles, and collateral for DeFi protocols in a truly neutral, inflation-resistant denomination.

Target Markets: - Crypto-native treasuries seeking non-USD reserves - Emerging market users hedging local currency devaluation - Cross-border remittance corridors - B2B global trade invoicing - DeFi protocols requiring diversified collateral

1.2 Key Differentiators

1.3 Executive Metrics

• Launch Target: €5M–€50M guarded phase (Month 7–12)
• Projected Year 1 Revenue: €80K–€150K (mint/burn fees, reserve yield)
• Regulatory Path: FMA authorization (Austria) by Month 6
• Team: Founder + 2 FTE (operations, tech) in Phase 1
• Target: Become the primary settlement token for emerging market crypto users

2. INDEX ENGINE

2.1 Final Production Formula

The ESP index value is computed daily via weighted multi-pillar aggregation:

INDEX_t = β·CPI_t + γ·FX_t + δ·COMM_t + ε·PROD_t + ζ·CRYPTO_t

Where:

• β = 0.58 (CPI pillar weight)
• γ = 0.10 (FX volatility hedge weight)
• δ = 0.15 (Commodity inflation weight)
• ε = 0.15 (Productivity deflation offset)
• ζ = 0.02 (Crypto damping — anti-volatility)

2.1.1 CPI Pillar

CPI_t = (1 - λ) · RAW_CPI_t + λ · CPI_{t-1}

where λ = 0.97 (daily EWMA smoothing)

Aggregate global CPI from 20-country basket: - OECD developed (70%): USA, Japan, Germany, France, UK, Canada, Australia - Emerging (30%): India, Brazil, Mexico, South Africa, Turkey, Philippines, Indonesia, Vietnam, Thailand, Pakistan

Normalized to year-over-year percentage change, then dampened via 97% daily retention to smooth volatility spikes.

2.1.2 FX Pillar

FX_t = Σ(w_i · log(FX_i,t / FX_i,base))

where:
  USD: w_1 = 0.43
  EUR: w_2 = 0.29
  CNY: w_3 = 0.12
  JPY: w_4 = 0.08
  GBP: w_5 = 0.08
  Base = Q4 2025 ECB midrates

Captures real exchange rate movements. Log-returns dampened by same λ = 0.97 EWMA. Goal: hedge against single-currency depreciation.

2.1.3 Commodity Pillar

COMM_t = (1 - λ) · RAW_COMM_t + λ · COMM_{t-1}

RAW_COMM_t = a·ENERGY_t + b·METALS_t + c·AGRI_t

where:
  a = 0.40 (energy: WTI, Brent, natural gas)
  b = 0.40 (metals: gold, copper, lithium, nickel)
  c = 0.20 (agriculture: wheat, corn, soybeans)
  λ = 0.97

Protects against supply shocks and real asset inflation.

2.1.4 Productivity Pillar

PROD_t = Σ w_i · TFP_i,t

where w_i = 1/20 (equal weight across 20 OECD countries)
TFP_i,t = log(GDP_i,t / (Labor_i,t + Capital_i,t))

Update frequency: Quarterly (lagged 1 quarter)

Captures technological deflation and long-term growth. Dampens structural inflation via productivity gains.

2.1.5 Crypto Pillar (Anti-Volatility)

CRYPTO_t = (1 - λ_K) · RAW_CRYPTO_t + λ_K · CRYPTO_{t-1}

RAW_CRYPTO_t = max( log(BTC_t / BTC_base), -0.05) + max( log(ETH_t / ETH_base), -0.05)
               ────────────────────────────────────────────────────────────────────
               2
where:
  λ_K = 0.995 (ultra-conservative daily smoothing — almost frozen)
  BTC_base, ETH_base = Jan 1, 2026 prices
  Clamp: ±5% daily moves capped to prevent extreme spikes

Provides minimal diversification from crypto volatility while remaining resilient to extreme moves. Ultra-high smoothing (λ_K = 0.995) means 99.5% of yesterday’s value persists to today.

2.2 Parameter Reference Table

2.3 Data Sources & Pipeline

2.3.1 CPI Pillar Data Sources

Handling Missing Data: - Lag >3 days: Use LOCF (Last Observation Carried Forward) + flag as provisional - Outliers (>±3σ): Clamp to historical ±3σ band; flag for manual review - Interpolation: Linear for monthly → daily CPI (use 21-day rolling average)

Quality Rules: - Require ≥18/20 country sources updated within 48 hours - If <18 sources, pause index update and use previous close value - Weekly reconciliation against OECD forecast releases

2.3.2 FX Pillar Data Sources

Specification: - Use ECB noon rates (12:00 CET) as reference point - Real-time rates update every 15 minutes - Apply ±3% band clamp per currency (extreme move guard) - Rebase quarterly to prevent drift

2.3.3 Commodity Data Sources

Weighting Scheme (within commodity pillar): - Energy (40%): WTI 50%, Brent 30%, Nat Gas 20% - Metals (40%): Gold 25%, Copper 25%, Lithium 20%, Nickel 30% - Agri (20%): Wheat 33%, Corn 33%, Soybeans 34%

2.3.4 Productivity Data Sources

Note: Productivity data has 1–2 quarter lag. Use official OECD releases only; interpolate linearly for daily display.

2.3.5 Crypto Data Sources

Specification: - Use volume-weighted price average (VWAP) across top 5 exchanges - Fallback: CoinGecko’s VWAP if individual exchange data unavailable - Extreme move guard: Clamp ±5% per day before applying λ_K smoothing

2.4 Rebalancing Rules

Quarterly Rebalance Dates: March 31, June 30, September 30, December 31

Trigger Conditions: 1. Any component weight drifts >2% from target 2. New OECD productivity data released (one-time adjustment per quarter) 3. Commodity concentration (any single commodity) exceeds 35% of COMM pillar 4. FX concentration (any single currency) exceeds 50% of FX pillar

Rebalance Process:

1. Freeze Window: Trading suspended 12:00–14:00 CET on rebalance date
2. Historical Review: Analyze prior 24 months of daily index values
3. Weight Adjustment: Recalculate β, γ, δ, ε, ζ to maintain 1.00 sum and target allocations
4. Announcement: Publish new weights 24 hours before effectiveness
5. Execution: Rebalance reserves (buy/sell T-Bills, FX) to match new weights
6. Documentation: Post rebalance report to governance dashboard within 48 hours

Concentration Caps (soft, rebalance-triggered):

2.5 Stress Tests

Scenario 1: USD Crash (30% depreciation vs FX basket in 6 months)

Trigger: Political instability, fiscal dominance, or monetary policy shock.

Index Behavior: - FX pillar: +7.8% contribution (0.43 USD weight × 18% loss = −7.74% shock absorbed by other currencies) - Net index impact: ~+1.2% (FX 10% weight × ~12% multi-currency improvement) - CPI pillar: Potential +3–4% (imported inflation in USD-dependent countries) - Net Result: INDEX rises ~4–5%, ESP appreciates in real terms

Mitigation: Diversified FX basket ensures no single currency collapse crushes peg; CPI capture protects against imported inflation pass-through.

Scenario 2: Commodity Spike (Oil +80% in 3 months)

Trigger: Middle East conflict, supply shock, or geopolitical event.

Index Behavior: - Energy (16% of COMM): WTI +80% → Energy contribution +12.8% - COMM pillar (15% of INDEX): ~+2.2% impact - CPI effect (lagged 4–6 weeks): +1–2% additional - Net Result: INDEX rises 3–4% over 2–3 months

Mitigation: λ = 0.97 EWMA smoothing spreads impact over ~14 days; quarterly rebalance caps energy to <60% of pillar.

Scenario 3: Crypto Winter (BTC −70%, ETH −75% in 2 months)

Trigger: Regulatory crackdown, leverage collapse, or sentiment reversal.

Index Behavior: - Crypto pillar (only 2% of INDEX): Clamp to −5% per day - With λ_K = 0.995, −5% clamp spreads over 28 days - Net Result: INDEX drops 0.10–0.15% maximum - Why Resilient: Crypto is only 2% weight; ultra-high smoothing prevents cliff drops

Mitigation: Intentionally low weight and extreme smoothing isolate ESP from crypto volatility.

Scenario 4: Global Recession (CPI −2%, commodity prices −30%, productivity +1% due to automation)

Trigger: Financial crisis, demand collapse, or supply-side shock.

Index Behavior: - CPI pillar (58% weight): −2% → −1.16% contribution - COMM pillar (15% weight): −30% → −4.5% contribution - PROD pillar (15% weight): +1% → +0.15% contribution - Net Result: INDEX drops 5–6%

Mitigation: Productivity gain partially offsets; deflation is acceptable (ESP preserves real purchasing power in nominal terms).

Scenario 5: Stagflation (CPI +8%, commodity +40%, productivity −1%)

Trigger: Oil shock + policy error (1970s-style scenario).

Index Behavior: - CPI pillar: +8% → +4.64% contribution - COMM pillar: +40% → +6% contribution - PROD pillar: −1% → −0.15% contribution - Net Result: INDEX rises 10–11%

Mitigation: Commodity weight (15%) captures real asset inflation; CPI weight (58%) ensures purchasing power preservation.

3. TOKEN & RESERVE DESIGN

3.1 Token Specification

Contract Details:

Token Authorization Control:

Only ESPMinter contract authorized to call mint()
Only ESPBurner contract authorized to call burn()
Owner (DAO/Foundation) can pause transfers
Emergency: Kill switch pauses all transfers

Multi-chain Deployment:

Cross-chain bridge: Stargate Finance or LayerZero for liquidity movement.

3.2 Mint/Burn Mechanics

Primary Market (KYC Counterparties)

Participants: - Licensed market makers (BingX, OKX, Kraken if available) - Institutional investors (family offices, treasuries) - Crypto hedge funds with institutional counterparty relationships

Mint Process:

Pricing (NAV ± 10 bps):

Mint Price = (INDEX_t × 0.9990) to (INDEX_t × 1.0010)
Burn Price = (INDEX_t × 0.9990) to (INDEX_t × 1.0010)
Fee: 5 bps (0.05%) split: 2 bps to reserve, 3 bps to protocol

Minimum Mint/Burn: €10,000 per transaction (≈10,000 ESP at parity)

Maximum Daily Mint Cap (guarded launch):

• Phase 1 (€5M cap): €500K per day (0.1% of total supply)
• Phase 2 (€50M cap): €2M per day
• Phase 3 (uncapped): 2% of daily trading volume on primary exchange

Secondary Market (Open Trading)

• CEX pairs: ESP/EUR, ESP/USD, ESP/ETH
• DEX pools: Uniswap v3 (0.01% fee tier, tight range)
• Spreads driven by arbitrage; no protocol fee on secondary trades

3.3 Reserve Structure

Reserve Composition (Backing €50M Circulating Supply)

Reserve Management Rules:

• WAM (Weighted Average Maturity): Must stay <90 days after 2027; currently <120 days acceptable
• Concentration Limits:
  • No single country >30% of reserve
  • No single issuer >20%
  • Cash buffer always >5% of AUM
• Quality Standards:
  • Minimum Moody’s A2 or equivalent
  • ECB-eligible collateral only for repo operations
  • No equities, no corporate debt, no emerging market bonds
• Rebalancing: Monthly; if any asset >2% off target, execute within 5 business days
• Custody: Segregated accounts with Euroclear (primary) and Federal Reserve (for USD leg)

Reserve Yield Calculation

Reserve Yield = Σ(w_i × Yield_i)

For Phase 1 (€5M AUM):
  = 0.25 × 3.2% + 0.16 × 3.0% + 0.05 × 3.25% + 0.20 × 5.0%
    + 0.08 × 3.75% + 0.08 × 0.75% + 0.08 × 2.25% + 0.08 × 0.75%
  = 0.80 + 0.48 + 0.16 + 1.0 + 0.30 + 0.06 + 0.18 + 0.06
  = 3.04% blended annual yield

3.4 Peg Mechanism

Arbitrage Incentive Structure

Goal: Maintain ESP/INDEX price within 0.5% band (tight peg).

Arbitrage Loop (if ESP > INDEX):

1. Market maker buys EUR, USD, or commodities (real assets)
2. MM submits to ESPERANTO Issuer with mint request
3. Issuer assembles into reserve basket, mints ESP
4. MM sells ESP in secondary market at premium
5. Profit = Premium − Mint fee (5 bps) − Collateral acquisition cost

Example:
  INDEX = €1.0000
  ESP secondary price = €1.0080 (80 bps premium)
  Mint fee = 5 bps
  Arbitrage profit = 80 − 5 − (acquisition friction) ≈ 50–70 bps
  Action: MM mints 1M ESP, realizes €500K–€700K on small capital deployment

Arbitrage Loop (if ESP < INDEX):

1. Market maker buys ESP from secondary market
2. MM submits burn request to ESPERANTO Issuer
3. Issuer validates holdings, burns ESP, returns collateral
4. MM sells collateral (T-Bills, FX) at spot price
5. Profit = (INDEX − ESP secondary) − Burn fee (5 bps)

Example:
  INDEX = €1.0000
  ESP secondary price = €0.9920 (80 bps discount)
  Burn fee = 5 bps
  Arbitrage profit = 80 − 5 ≈ 75 bps
  Action: MM buys 1M ESP at €0.9920, burns, recovers €1M face value

Circuit Breaker Triggers:

• If ESP/INDEX deviation >1% for >2 hours → halt new mints
• If ESP/INDEX deviation >2% for >1 hour → emergency board review + potential mint/burn suspension
• If INDEX movement >5% in 1 day → circuit breaker cooldown (30 min trading pause)
• Recovery: Manual board approval required to re-enable, or automatic after 24 hours

3.5 Liquidity Architecture

CEX Listing Strategy

Phase 1 Targets (Months 7–12):

1. BingX (founder’s network)
   • Pair: ESP/EUR, ESP/USD
   • Liquidity: €500K market maker reserve
   • Fee tier: 0.1% trading fee (standard)
   • Volume target: €1M–€5M daily
2. Kraken (if compliant path achievable)
   • Pair: ESP/EUR, ESP/USD
   • Liquidity: €300K reserve
   • Fee tier: 0.16% trading fee
   • Volume target: €500K–€2M daily
3. OKX
   • Pair: ESP/USDT
   • Liquidity: €400K reserve
   • Fee tier: 0.1% (promotional)
   • Volume target: €500K–€1M daily

Phase 2 Targets (Months 13–18):

• Bybit (emerging market focus)
• Gate.io (Asia volume)
• Upbit (Korea)

Volume Targets:

DEX Liquidity Pools

Uniswap v3 Strategy:

Curve (for stablecoin-to-stablecoin routing):

• ESP/3CRV (Tri-pool: USDC, USDT, DAI)
• Depth: €300K liquidity
• Fee: 0.04%
• Aim: Become routing hop for emerging market users

Initial DEX Launch (Phase 1):

• Allocate €300K from reserve to bootstrap Uniswap pools
• Concentrated liquidity (tight range) to maximize capital efficiency
• Liquidity mining incentives: None (foundation bootstrap only)

OTC Desk & Institutional Relationships

OTC Desk Structure:

• Operator: ESPERANTO Issuer (Frankfurt office) or partner broker
• Counterparties: Family offices, hedge funds, DAOs, emerging market central banks
• Tickets: €500K–€50M per transaction
• Pricing: INDEX ± 3 bps (tighter than secondary market)
• Settlement: T+1 (EUR FX) or T+2 (USD FX)

Example OTC Trade:

Counterparty: Emerging market central bank
Request: Buy ESP 100M (€100M notional)
Pricing: INDEX=€1.0015, offer at €1.0012 (−3 bps)
Collateral: Mix of EUR, USD, T-Bills per reserve composition
Settlement: 2 business days, via Euroclear
Commission: 0% (market-maker loss acceptable for AUM growth)

4. MiCAR COMPLIANCE & LEGAL STRUCTURE

4.1 Classification Justification: ART not EMT

Key Distinction (MiCAR Articles 3(5) vs 3(6)):

ESP’s Classification as ART:

1. Reference Asset: Multi-pillar index (CPI + FX + Commodities + Productivity + Crypto)
   ≠ Single fiat currency ✓ (ART marker)

2. Redemption Mechanism: Holders redeem at NET ASSET VALUE (daily index),
   not fixed par ✓ (ART marker)

3. No Guarantee: ESPERANTO Issuer guarantees "best-efforts" index tracking,
   not 1:1 peg. Tracking error is acceptable within 2% band. ✓ (ART marker)

4. Conclusion: Unambiguously ART under MiCAR Article 3(6) ✓

Why NOT an EMT:

• ESP is not redeemable at fixed par (not a currency proxy)
• Index fluctuates daily; holders accept purchasing power, not nominal stability
• Collateral backing is not fiat 1:1; it’s a diversified basket

4.2 Significant ART Thresholds & Growth Management

Significant ART Triggers (MiCAR Art. 19(4)):

Strategy to Manage Below Thresholds:

1. Cap circulating supply at €50M until Significant ART designation approved
2. Limit holder count via institutional-only distribution (KYC counterparties)
3. Voluntary compliance with Significant ART rules early (Art. 36–39 now; beyond requirements later)
4. Transparency: Publish monthly metrics on holder count, trading volume, to demonstrate controlled growth

4.3 Austrian Legal Entity Structure

3.1 ESPERANTO Vermögensverwaltung GmbH (Issuer / OpCo)

Jurisdiction: Austria (Vienna) Business: Asset management, token issuance, reserve custody

Incorporation Details:

Operating Functions:

• Token minting/burning (via smart contracts)
• Reserve management (asset custody arrangement)
• Primary market interactions (KYC’d counterparties)
• Compliance & regulatory reporting to FMA
• Whitepaper updates & investor communications

3.2 ESPERANTO Foundation (Index Governance & Long-term Steward)

Jurisdiction: Austria (Privatstiftung) OR Liechtenstein (Stiftung) — recommend Austria for simplicity

Business: Non-profit governance, index oversight, protocol stewardship

Structure (Austria Privatstiftung):

Governance Decisions:

• Quarterly Index Rebalancing: Foundation approves weight changes
• Smart Contract Upgrades: Foundation votes on UUPS proxy implementations
• Emergency Actions: Circuit breaker thresholds, killswitch deployment
• No Token Distributions: Foundation has no governance token; Kuratorium members serve ad honorem (no fees)

Foundation-GmbH Relationship:

        ESPERANTO Foundation
         (Non-Profit)
              │
              │ Strategic Direction
              ├─────────────────────────────┐
              │                             │
              ▼                             ▼
      Foundation Board           ESPERANTO Vermögensverwaltung
      (Governance)              GmbH (Operational)
                                 │
                                 ├── Token Minting/Burning
                                 ├── Reserve Management
                                 ├── FMA Compliance Reporting
                                 └── Market Maker Relationships

4.4 Custody & Custodian Arrangement

Primary Custodian (EUR leg): - Institution: Euroclear (Luxembourg-based ICSD) - Assets Held: Austria OeBs, German Bunds, EUR cash deposits - Segregation: Dedicated custody account (ESP Funds Only) - Insurance: Euroclear protection up to €100M (or full amount if lower)

Secondary Custodian (USD leg): - Institution: Federal Reserve (via BNY Mellon if private entity) - Assets Held: US T-Bills, USD cash deposits - Segregation: Segregated custody account at BNY Mellon - Insurance: FDIC equivalent (BNY Mellon insurance program)

Crypto Custody (Ethereum, Arbitrum, Polygon, Base): - Method: Multi-sig smart contract (2-of-3 threshold) - Key Holders: Founder, External Auditor/Security Firm, Lido Node Operator (or similar) - Cold Storage: No; reserve smart contracts deployed on Ethereum L1 (audited, immutable)

Custody Agreement Terms:

• Frequency of Reporting: Daily statements (settlement + market value)
• Reconciliation: Weekly (independent auditor spot-check)
• Replacement Custodian: 6-month notice to switch; redundancy plan for BNY Mellon

4.5 FMA Authorization Path

Phase 1: Pre-Authorization (Months 1–4)

Month 1: Preparation

• Incorporate GmbH + Foundation (Austrian notary)
• Hire FMA-experienced compliance officer (external, part-time)
• Draft detailed ART Whitepaper per MiCAR Art. 19
• Commission smart contract audit (OpenZeppelin or Trail of Bits)

Month 2: Initial Consultation

• Submit pre-application request to FMA
• Present ART classification & reserve design
• Receive preliminary guidance on missing documentation
• Submit Compliance Plan (governance, reserve management, consumer protection)

Month 3: Full Application

• Submit to FMA:
  • Completed ART Whitepaper (Art. 19)
  • Reserve Management Policy (Art. 36–38)
  • Governance Charter (index rebalancing, emergency rules)
  • Organizational Structure (GmbH + Foundation)
  • Smart Contract Audit Report
  • Board Member CVs & Suitability Assessment (FMA form)
  • Capital Adequacy: Demonstrate €25K+ paid-up capital
  • Risk Management Framework
  • Custody Agreements (Euroclear + BNY Mellon)
• FMA Review Period: 3–6 months (no hard deadline; parallel with testnet)

Month 4: Remediation & Dialogue

• Address FMA clarification requests
• Iterate on governance structure if needed
• Prepare for on-site inspection

Phase 2: Authorization & Go-Live (Months 5–7)

Month 5: FMA Decision

• Best Case: Conditional authorization (requires live deployment plan)
• Likely Case: Authorization with conditions (e.g., cap at €5M, monthly reporting)
• Fallback: Request for more information (delay 1–2 months)

Month 6: Testnet & Ready-to-Launch Checklist

• Deploy contracts to Ethereum Sepolia + Arbitrum Goerli
• Run 4-week testnet with synthetic index updates
• Validate reserve custody setup
• Conduct tabletop exercises for emergency scenarios

Month 7: Mainnet Launch

• Deploy to Ethereum mainnet (L1 anchor)
• Open primary market (first mint request from institutional counterparty)
• List on BingX (founder’s exchange)
• Publish daily NAV on governance dashboard

Total Timeline: Month 0 → Month 7 (realistic, accounting for FMA bureaucracy)

4.6 Ongoing Compliance Obligations

Monthly Obligations

Quarterly Obligations

Annual Obligations

Article-by-Article Compliance Matrix

5. TECH ARCHITECTURE

5.1 Smart Contract Architecture

Core Contracts

ESPToken (ERC-20 + Burnable + Pausable)

// Key Functions
function mint(address to, uint256 amount) onlyMinter returns (bool)
function burn(uint256 amount) public returns (bool)
function pause() onlyOwner
function unpause() onlyOwner
function transfer(address to, uint256 amount) public returns (bool)

Roles: - DEFAULT_ADMIN_ROLE: Owner (Foundation multisig) - MINTER_ROLE: ESPMinter contract only - PAUSER_ROLE: Circuit breaker contract

ESPMinter (Primary Market)

function requestMint(
  uint256 espAmount,
  address collateralToken,
  uint256 collateralAmount,
  bytes32 dataHash
) external returns (uint256 requestId)

function fulfillMint(uint256 requestId) external onlyFulfiller
function rejectMint(uint256 requestId, string reason) external onlyOwner

Specifications: - Minimum mint: €10,000 (10,000 ESP at parity) - Fee: 5 bps (50 basis points) in ESP - Request → Fulfill timeline: T+1 (24 hours) - Fee split: 2 bps to protocol reserve, 3 bps burned

ESPReserveOracle (Daily Index Publisher)

function submitIndexValue(
  uint256 newIndexValue,
  uint256[] memory componentValues,
  bytes[] memory oracleSignatures
) external onlyOracleCommittee

function getLatestIndex() public view returns (uint256)
function getComponentBreakdown() public view returns (IndexComponents memory)

Specifications: - Multi-signature (2-of-3 threshold) - Update cadence: 1× daily (noon CET ± 30 min) - Emergency update path: Any 2 signers can trigger outside normal window - History: 90-day rolling window stored on-chain

ESPCircuitBreaker (Emergency Controls)

function checkMintEligibility(uint256 indexValue) external view returns (bool)
function checkBurnEligibility(uint256 indexValue) external view returns (bool)
function triggerEmergencyPause() external onlyGovernance
function releaseEmergencyPause() external onlyGovernance

Triggers: - INDEX moves >5% in 1 hour → 30 min cooldown, no new mints - ESP/INDEX deviation >1% for >2 hours → pause new mints - INDEX moves >10% in 24 hours → manual governance review required - Extreme outlier data (>±5σ on any component) → reject oracle update, use LOCF

Access Control & Upgradeability

Pattern: UUPS (ERC-1967)

contract ESPToken is ERC20, Ownable, ERC1967Upgrade {
  function _authorizeUpgrade(address newImplementation)
    internal
    onlyOwner
    override {}
}

Upgrade Process: 1. Deploy new implementation to testnet 2. Run security review (24 hours) 3. Governance vote (Foundation board) — minimum 2/3 approval 4. 48-hour delay before execution (allow community withdrawal if disliked) 5. Execute proxy upgrade

Governance Multisig: - Signers: Founder, External Compliance Officer, Independent Board Member - Threshold: 2-of-3 - Timelocks: 48 hours (except emergency pause, which is 0-hour)

5.2 Oracle System

Multi-Source Design

Goal: Minimize single-source oracle manipulation risk.

Architecture:

Data Sources (5 pillars)
  │
  ├─ CPI: [OECD, IMF, Eurostat] → aggregated via median
  ├─ FX: [ECB, BIS, Reuters] → volume-weighted median
  ├─ Commodities: [CME, ICE, LME] → volume-weighted median
  ├─ Productivity: [OECD.Stat official release] → single source (quarterly)
  └─ Crypto: [CoinGecko, CMC, Kraken] → median VWAP
       │
       ▼
  Normalizer (Python/Rust)
  - Outlier clamp (±3σ per component)
  - Unit standardization
  - LOCF for missing data
       │
       ▼
  Index Calculator
  - Apply formula: INDEX = 0.58·CPI + 0.10·FX + 0.15·COMM + 0.15·PROD + 0.02·CRYPTO
  - EWMA smoothing per component
       │
       ▼
  Oracle Committee (2-of-3)
  - Sign index value with private key
  - Append signatures to transaction
       │
       ▼
  Smart Contract ESPReserveOracle
  - Verify 2-of-3 signatures
  - Check bounds (INDEX within ±10% of previous close)
  - Reject if bounds violated; use LOCF
       │
       ▼
  Blockchain (Ethereum L1)
  - Publish INDEX value, emit event

Committee Signers

Signing Thresholds: - Normal operation: Signers 1 + 2 - Emergency (heartbeat failed): Signers 1 + 3 or 2 + 3 (any 2) - All 3 available: Use lowest-risk pair (1 + 2 preferred)

Commit-Reveal Scheme

Weekly Aggregation & Verification:

Monday 00:00 UTC:
  Signers 1 & 2 each compute INDEX independently
  Commit phase (12 hours): Submit hash(INDEX || salt) publicly
  Reveal phase (12 hours): Publish actual INDEX + salt
  Discrepancy >0.1%? Halt and investigate; use previous close

Wednesday 12:00 CET:
  Official ESPReserveOracle.submitIndexValue() called
  2-of-3 signatures verified on-chain
  Index value locked; emits event

Heartbeat Check:
  If no new index for >26 hours → circuit breaker triggered
  Pause all mint/burn until manual override

Data Quality Rules

Outlier Detection & Clamps:

Missing Data Protocol (LOCF = Last Observation Carried Forward):

Daily Validation Checklist:

☐ Receive data from all 5 pillars by 11:00 CET
☐ Check each source against expected range (±3σ)
☐ If outlier: cross-reference 2+ backup sources
☐ If still anomalous: use LOCF + flag manual review
☐ Compute index value at 11:30 CET
☐ Compare to previous close: if >±10%, investigate before signing
☐ Signers 1 & 2 independently verify calculation
☐ Commit hash by 12:00 CET; reveal by 12:30 CET
☐ Publish on-chain by 13:00 CET (latest)
☐ Emit event; dashboard updates within 60 seconds

5.3 Data Ingestion Pipeline

Architecture Overview

┌─────────────────────────────────────────────────────────┐
│               DATA COLLECTION LAYER                     │
├─────────────────────────────────────────────────────────┤
│  Batch Collectors (Python/Rust):                        │
│  - CPI Batch: Daily 10:00 CET → fetch OECD, Eurostat   │
│  - FX Stream: Real-time push → ECB feeds                │
│  - Commodity Stream: Real-time push → CME/ICE APIs      │
│  - Productivity Batch: Quarterly → OECD.Stat           │
│  - Crypto Stream: Real-time → CoinGecko/CMC v3         │
└────────────────┬────────────────────────────────────────┘
                 │
┌────────────────▼────────────────────────────────────────┐
│              NORMALIZER (Python/Rust)                   │
├─────────────────────────────────────────────────────────┤
│  Tasks:                                                 │
│  - Unit standardization (e.g., CPI % → basis points)   │
│  - Outlier detection & clamping (±3σ per component)    │
│  - Missing data handling (LOCF)                         │
│  - FX volume-weighting (20-country basket)             │
│  - Commodity VWAP (multi-exchange aggregation)         │
│  Output: JSON { CPI, FX, COMM, PROD, CRYPTO }          │
└────────────────┬────────────────────────────────────────┘
                 │
┌────────────────▼────────────────────────────────────────┐
│            INDEX CALCULATOR (Python)                    │
├─────────────────────────────────────────────────────────┤
│  Compute:                                               │
│  INDEX_t = 0.58·CPI_t + 0.10·FX_t + 0.15·COMM_t        │
│          + 0.15·PROD_t + 0.02·CRYPTO_t                 │
│  Apply EWMA smoothing (λ=0.97 for all but crypto)     │
│  Output: INDEX value + component breakdown              │
└────────────────┬────────────────────────────────────────┘
                 │
┌────────────────▼────────────────────────────────────────┐
│            ORACLE PUBLISHER (Rust)                      │
├─────────────────────────────────────────────────────────┤
│  Tasks:                                                 │
│  - Receive INDEX from calculator                        │
│  - Request signatures from 2-of-3 oracle committee      │
│  - Verify signatures received                           │
│  - Call ESPReserveOracle.submitIndexValue()            │
│  - Log transaction hash; store in PostgreSQL            │
│  Output: On-chain index event                           │
└────────────────┬────────────────────────────────────────┘
                 │
┌────────────────▼────────────────────────────────────────┐
│            BLOCKCHAIN (Ethereum L1)                     │
├─────────────────────────────────────────────────────────┤
│  - Verify 2-of-3 signatures                             │
│  - Check bounds (±10% vs previous)                      │
│  - Store INDEX on-chain                                 │
│  - Emit IndexUpdated(value, timestamp) event            │
└─────────────────────────────────────────────────────────┘

Tech Stack Recommendation

Database Schema (PostgreSQL)

CREATE TABLE index_history (
  id SERIAL PRIMARY KEY,
  index_date DATE NOT NULL UNIQUE,
  index_value DECIMAL(18,8) NOT NULL,
  cpi_component DECIMAL(18,8),
  fx_component DECIMAL(18,8),
  commodity_component DECIMAL(18,8),
  productivity_component DECIMAL(18,8),
  crypto_component DECIMAL(18,8),
  published_at TIMESTAMP NOT NULL,
  transaction_hash VARCHAR(66),
  CONSTRAINT check_index_range CHECK (
    index_value > 0.8 AND index_value < 1.2
  )
);

CREATE TABLE data_sources (
  id SERIAL PRIMARY KEY,
  source_name VARCHAR(100) NOT NULL,
  component VARCHAR(50) NOT NULL,
  last_fetched TIMESTAMP,
  status VARCHAR(20),
  health_check_url TEXT,
  backup_source_id INT REFERENCES data_sources(id)
);

CREATE TABLE oracle_signatures (
  id SERIAL PRIMARY KEY,
  index_id INT NOT NULL REFERENCES index_history(id),
  signer_address VARCHAR(42) NOT NULL,
  signature VARCHAR(132) NOT NULL,
  signed_at TIMESTAMP NOT NULL
);

CREATE TABLE circuit_breaker_events (
  id SERIAL PRIMARY KEY,
  triggered_at TIMESTAMP NOT NULL,
  trigger_type VARCHAR(50),
  index_value_before DECIMAL(18,8),
  index_value_after DECIMAL(18,8),
  action_taken VARCHAR(200),
  resolved_at TIMESTAMP
);

5.4 Dashboard & Transparency

Public Dashboard (Web)

URL: https://dashboard.esperanto.money

Core Sections:

1. Live Index Display
   • Large, real-time INDEX value (updated every 60 seconds)
   • 24h change, YTD change
   • Peg status: GREEN (within ±0.5%), YELLOW (±0.5–1%), RED (>1%)
2. Component Breakdown
   • Pie chart: β=58% CPI, γ=10% FX, δ=15% Commodity, ε=15% Prod, ζ=2% Crypto
   • Each component shows: current value, 7-day change, 30-day volatility
   • Clickable: Drill into sub-components (e.g., FX → USD 43%, EUR 29%, etc.)
3. Reserve Composition
   • Table: Asset class, amount, %, yield, custodian
   • Pie chart: EUR bonds 46%, USD bonds 20%, GBP bonds 8%, JPY bonds 8%, CNY bonds 8%, Cash 10%
   • Live update: Mark-to-market value vs. par
4. Secondary Market Data
   • Price feeds: ESP/EUR, ESP/USD, ESP/ETH across BingX, Kraken, Uniswap v3
   • 24h volume, average spread (bps), depth (±0.5% slippage volume)
   • OHLCV chart (1h, 4h, 1d candles)
5. Tracking Error & Performance
   • Daily INDEX vs. ESP price: deviation %, trend over 90 days
   • Rolling 30-day correlation (ESP price vs. INDEX)
   • Historical NAV table (last 30 days)
6. Risk Metrics
   • Current concentration limits: CPI <60% ✓, FX USD <50% ✓, Commodity energy <35% ✓
   • Liquidity reserve: €2.5M available for emergency buyback
   • Circuit breaker status: GREEN (normal), flashed YELLOW/RED if triggered
7. Governance & Compliance
   • Last rebalance date, next rebalance date
   • FMA authorization status
   • Whitepaper version, publish date
   • Link to auditor report (latest, PDF)
   • Regulatory filings (if applicable)

API Endpoints (RESTful)

GET /api/v1/index/current
  → { index: 1.0052, components: {...}, timestamp: "2026-03-30T12:00:00Z" }

GET /api/v1/index/history?from=2026-03-01&to=2026-03-30
  → [ { date: "2026-03-01", index: 1.0010 }, ... ]

GET /api/v1/components/breakdown
  → { cpi: 0.9950, fx: 1.0015, commodity: 1.0080, prod: 1.0002, crypto: 0.9999 }

GET /api/v1/reserve/composition
  → { assets: [ { name: "Austria OeBs", amount: 12.5, currency: "EUR", yield: 3.2 }, ... ] }

GET /api/v1/secondary-market/prices
  → { pairs: [ { symbol: "ESP/EUR", price: 1.0050, volume_24h: 2.3e6 }, ... ] }

GET /api/v1/risk/status
  → { peg_status: "GREEN", deviations: {...}, circuit_breaker: false, liquidity_buffer: 2.5 }

GET /api/v1/governance/rebalance-schedule
  → { next_rebalance: "2026-06-30", last_rebalance: "2026-03-31", ... }

Authentication: Public endpoints (no API key); rate limit 100 req/min per IP

5.5 Security Framework

Smart Contract Audits

Auditor Selection:

Recommended Approach: - OpenZeppelin (full audit) for ESPToken, ESPMinter, ESPCircuitBreaker - Certora (formal spec) for INDEX calculation formula - Deploy after both audits complete + findings remediated

Bug Bounty Program

Platform: Immunefi (or HackerOne)

Structure:

Policy: - 30-day disclosure window post-report - Safe harbor for good-faith security researchers - Payout within 14 days of approval

Incident Response Plan

Tier 1: Information Security Incident (Data Breach, Key Compromise)

0–1 hour:   Detect → Alert Foundation board + Compliance Officer
1–4 hours:  Assess impact → Notify FMA (within 4 hours if crypto asset risk)
4–24 hours: Contain → Revoke compromised keys; activate backup
24–72 hrs:  Investigate → Determine root cause; implement fix
72 hrs+:    Remediate → Deploy patch; restore affected systems
Days 7–30:  Post-mortem → Publish incident report (redacted)

Tier 2: Oracle Failure (Data Feed Outage >1 hour)

Immediate:  Detect stale data → Circuit breaker auto-triggered
5 mins:     Alert oracle committee → Manual verification of data sources
30 mins:    Decision → Use LOCF (continue with previous INDEX) or pause index updates
1–2 hours:  Recovery → Restore data feed; test before publishing new INDEX
4 hours:    Resume → Publish updated index; post incident summary

Tier 3: Smart Contract Exploit (Unexpected Behavior)

0–15 mins:   Detect via monitoring → Alert all key holders
15–30 mins:  Verify → Reproduce issue; estimate financial impact
30 mins:     Emergency response → Activate circuit breaker (pause minting)
30–60 mins:  Board decision → Escalate to FMA; decide on recovery action
1–4 hours:   Containment → Deploy emergency patch or rollback
4–24 hours:  Investigation → Post-mortem; identify root cause
24–72 hrs:   Recovery → Restore state if needed; compensate affected parties
Week 2:      Remediation → Redeploy fixed contract; resume normal operations
Week 4:      Post-mortem → Publish incident report with lessons learned

Key Contacts (On-call Rotation):

6. GO-TO-MARKET STRATEGY

6.1 Positioning

Tagline: “The World’s Currency, Not Any Single Nation’s”

Elevator Pitch (30 seconds):

ESPERANTO is a crypto-native stablecoin backed by a real-economy index spanning CPI, currencies, commodities, and productivity. Unlike USDC or USDT, ESP maintains purchasing power globally—not just US dollars. Issued in Austria under MiCAR, regulated by the FMA, with fully transparent reserves.

Differentiation Matrix:

Value Proposition by Segment:

6.2 Phase 1: Foundation (Months 1–6)

Objectives: - Establish legal & regulatory foundation - Validate index formula & oracle pipeline - Acquire first 3–5 institutional partners - Prepare mainnet launch

Milestone Map:

Market Activities (Months 3–6):

1. Stealth Launch (Community)
   • Discord: 500–1K early adopters (index validators, test participants)
   • Medium blog: Weekly technical deep-dives on index methodology
   • Twitter: Daily component updates (education angle)
2. Institutional Outreach
   • Target: 3–5 crypto treasuries, hedge funds with >€50M AUM
   • Contact: Partner VCs, family offices in crypto space
   • Pitch: “Be our first primary market participant; get 0% mint fee for first €500K”
3. Exchange Negotiation
   • BingX: Leverage founder’s relationship; negotiate Q3 listing
   • Kraken: Parallel conversations; target conditional approval by Month 7

6.3 Phase 2: Guarded Launch (Months 7–12)

Objectives: - Mainnet go-live with €5M supply cap - Achieve €1M–€2M daily CEX volume - Launch DEX pools (Uniswap + Curve) - Pilot remittance corridor (pilot geography)

Mainnet Launch Checklist (Month 7):

• FMA Authorization Letter signed
• Smart contracts deployed to Ethereum mainnet + Arbitrum
• Custody accounts fully funded (€5M in reserves)
• Oracle committee live & signing daily
• Dashboard live & public
• CEX listing live on BingX (trading pair: ESP/EUR, ESP/USD)
• Community comms: Announcement, AMA, testnet users celebrated

Liquidity Activation (Months 8–9):

1. Uniswap v3 Concentrated Pools
   • Allocate €200K liquidity: ESP/EUR (0.01% fee, ±0.5% range)
   • Deploy on Ethereum L1 + Arbitrum
   • Target spreads: <5 bps at €100K liquidity depth
2. Curve 3CRV Pool
   • Add ESP/3CRV pool (Ethereum mainnet)
   • Liquidity: €150K
   • Fee: 0.04%
   • Incentive: None (bootstrap allocation only)
3. Market Maker Relationships
   • Recruit 2–3 independent MMs (crypto funds with trading desks)
   • Offer: €10K–€50K liquidity mining on Uniswap/Curve for 3 months
   • Volume targets: €500K daily (CEX + DEX combined)

Regulatory Milestones (Months 7–12):

• Month 7: Post Whitepaper update (MiCAR Art. 19)
• Month 9: First quarterly reserve report to FMA
• Month 11: Annual risk assessment submitted
• Month 12: Year-end audit completion + financial statement filing

Marketing (Months 9–12):

1. Emerging Market Outreach
   • Partner with 1–2 cross-border remittance platforms (e.g., Wise, Flutterwave)
   • Pilot: Send ESP payments to Philippines, Mexico, Nigeria
   • Campaign: “Send global value, not just USD”
2. DeFi Integration
   • Approach Aave for listing as collateral (Ethereum + Arbitrum)
   • Curve: Encourage liquidity farming via LP incentives
   • Compound: Similar collateral discussion
3. Thought Leadership
   • Founder speaks at FundSummit (fintech conference)
   • Publish technical paper: “Multi-Pillar Index Design for Stablecoin Stability” (academic journals)
   • Medium series: “Why We Built a Non-National Currency” (founder’s blog)

6.4 Phase 3: Scale (Months 13–24)

Objectives: - Raise supply cap to €50M - Multi-chain presence (Ethereum, Arbitrum, Base, Polygon) - Establish B2B payroll & invoicing partnerships - EU-wide marketing campaign (MiCAR compliant)

Supply Expansion (Month 13):

• Request FMA cap increase from €5M → €50M (based on performance data)
• Demonstrate: 99.9% uptime, <0.5% tracking error, zero incidents
• Secure approval; announce on day of FMA letter

Multi-Chain Rollout (Months 14–16):

B2B Payment Integrations (Months 16–18):

1. Payroll Provider Partnership
   • Partner: Deel, Remote, or Guidepoint
   • Use case: Pay remote workers across borders in ESP (neutral currency)
   • Volume target: 100 payroll runs/month by Month 18
2. Invoice Factoring
   • Partner: Marco Polo Network (Hyperledger) or TradeLens equivalent
   • Use case: Trade finance denominated in ESP (remove FX basis risk)
   • Pilot with 3–5 EU SMEs (electronics, textiles, machinery exports)
3. Treasury Management
   • Partner with Crypto custodian (Coinbase, Galaxy)
   • Service: “Global Treasury in ESP” for crypto funds
   • Volume target: €20M+ in treasuries by Month 24

EU Marketing Campaign (Months 18–24):

1. Regulatory Messaging
   • “The First MiCAR-Compliant Global Currency”
   • Broadcast: Austrian business media, Financial Times (EU section), Cointelegraph
   • Budget: €50K
2. Institutional Sponsorships
   • Sponsor FH Joanneum (founder’s university) crypto research lab
   • Sponsor European Blockchain Association event
   • Budget: €20K
3. Emerging Market Influencers
   • Partner with 5–10 crypto educators in India, Mexico, Nigeria
   • Campaign: “Why ESP > local stablecoin” (educational, not promotional)
   • Budget: €30K (micro-influencer tier)

6.5 Target Segments & Positioning

7. BUSINESS MODEL

7.1 Revenue Streams

Stream 1: Mint/Burn Fees

Fee Structure: - Mint: 5 bps (0.05%) per transaction - Example: EUR 10,000 → 5 bps → EUR 5 fee → net ESP received ≈ 9,995 ESP - Burn: 5 bps per transaction - Example: 10,000 ESP → 5 bps → EUR 5 fee → net EUR received ≈ EUR 9,995 - Fee distribution: 2 bps to reserve buffer, 3 bps protocol revenue

Revenue Projection:

Phase 1 (€5M AUM, €100M annual mint volume):
  Annual mint volume: €100M
  Mint fees: €100M × 5 bps = €50K
  Annual burn volume: €50M (assume 50% annual turnover)
  Burn fees: €50M × 5 bps = €25K
  Total mint/burn revenue: €75K

Phase 2 (€25M AUM, €250M annual volume):
  Mint fees: €250M × 5 bps = €125K
  Burn fees: €125M × 5 bps = €62.5K
  Total: €187.5K

Phase 3 (€50M AUM, €500M annual volume):
  Mint fees: €500M × 5 bps = €250K
  Burn fees: €250M × 5 bps = €125K
  Total: €375K

Stream 2: Reserve Yield

Sources: - T-Bill interest (USD: 4.8–5.2% on €10M allocation) - Government bond yields (EUR: 2.8–3.5% on €22.5M allocation) - ECB deposit facility (3.25% on €2.5M) - JPY/CNY bond yields (0.5–2.5% on €8M)

Revenue Projection:

Phase 1 (€5M AUM):
  Blended yield: 3.04% (per calculation in 3.3)
  Annual revenue: €5M × 3.04% = €152K

Phase 2 (€25M AUM):
  Blended yield: 3.04% (unchanged)
  Annual revenue: €25M × 3.04% = €760K

Phase 3 (€50M AUM):
  Blended yield: 3.04%
  Annual revenue: €50M × 3.04% = €1,520K

Cost Offset: Reserve yield partially covers operational costs (custodian, oracle, compliance).

Stream 3: Spread Revenue (Market Making)

Method: - Market makers execute mint/burn for secondary market arbitrage - Spread between secondary price and primary NAV captured by MMs, not protocol - Protocol benefit: Reduced need for direct MM subsidies

Example:

Secondary market price: ESP/EUR = 1.0080 (premium)
Primary market NAV: 1.0000
MM buys mint: 1M EUR → receives ~1M ESP (1 bps fee) → sells at 1.0080
Spread profit: 80 bps (before costs)
Protocol benefit: No subsidy needed; organic liquidity from arbitrage

Revenue Projection: N/A (protocol net-zero; MMs retain spread)

Stream 4: Licensing Fees for Index Data

Target Customers: Other stablecoin projects, crypto funds needing global index

Pricing Tier: - Tier 1 (Community): Free (read-only API, 100 req/min) - Tier 2 (Professional): €1,000/month (1,000 req/min, guaranteed uptime SLA) - Tier 3 (Enterprise): €5,000/month (unlimited, white-label option, priority support)

Realistic Adoption (Year 1): - Tier 2: 2–3 customers → €24K–€36K/year - Tier 3: 1 customer (e.g., a major stablecoin competitor) → €60K/year

Total licensing revenue (Year 1): €84K–€96K

7.2 Cost Structure

Operating Costs (Annual, Phase 1)

Revenue vs. Cost (Phase 1, Year 1)

Revenue:
  Mint/Burn Fees:         €75K
  Reserve Yield:          €152K
  Licensing:              €90K
  Total:                  €317K

Costs:
  Operating:              €330K

NET P&L (Year 1):         −€13K (breakeven within operational uncertainty)

Interpretation: Phase 1 is essentially breakeven or slightly negative. Reserve yield (€152K) covers ~50% of costs; team salary (€140K FTE) is primary expense. Profitability achieved in Phase 2 (€25M AUM → €760K yield).

7.3 Financial Projections (3 Scenarios)

Scenario A: Conservative (€10M AUM by Year 3)

Scenario B: Base Case (€30M AUM by Year 3)

Scenario C: Optimistic (€50M AUM by Year 3)

Key Assumptions: - Team grows to 2–3 FTE by Year 3 (operations, compliance, marketing added) - Custodian fees scale linearly with AUM (1–1.5 bps) - Reserve yield remains 3–3.5% (interest rate assumption) - Mint/burn volume = 20% of AUM per year (turnover assumption) - Licensing revenue grows modestly (low adoption initially)

7.4 Funding Strategy

Phase 0: Bootstrap (Self-Funded, Months 1–3)

• Source: Founder personal capital (€50K–€100K)
• Use: Legal incorporation, smart contract development, initial audit
• Milestone: Working testnet, FMA pre-application approved

Phase 1: Seed Round (Optional, Months 4–6)

• Target Size: €200K–€500K
• Investors: Crypto VCs interested in European stablecoins (a16z crypto, Parafi, Dragonfly)
• Valuation: €3M–€5M (implied based on reserve cap)
• Terms: SAFE or Convertible note (no equity dilution yet; converts on Series A or profitability)
• Use: Complete FMA authorization, external audits, team hire (ops manager, engineer)

Phase 2: Growth Investment (Months 13–18, if Base/Optimistic scenario)

• Target Size: €1M–€2M
• Source: Strategic investors (crypto hedge funds, fintech VCs)
• Valuation: €15M–€25M (based on €25M+ AUM and profitability achieved)
• Use: Scale team to 5–8 FTE, expand to multiple blockchains, B2B integrations, marketing

Phase 3: Strategic Round (Optional, Year 3)

• Target Size: €5M–€10M
• Source: Traditional fintech VCs, family offices seeking exposure to MiCAR ecosystem
• Valuation: €50M–€100M (based on €50M AUM achievement, €1M+ annual profit)
• Use: International expansion (license replica systems in other EU jurisdictions), acquisition opportunities

Funding Priority: Bootstrap Phase 1 completely; only raise if reaching >€20M AUM in Year 2 is clearly achievable (positive PMF signal).

8. RISK REGISTER

Full Risk Matrix

9. APPENDICES

A. Complete Parameter Reference Table

[See Section 2.2 above — full parameter table reproduced here for convenience]

Index Weights (Σ = 1.0): - β (CPI) = 0.58 - γ (FX) = 0.10 - δ (Commodity) = 0.15 - ε (Productivity) = 0.15 - ζ (Crypto) = 0.02

FX Sub-weights: - USD: 0.43, EUR: 0.29, CNY: 0.12, JPY: 0.08, GBP: 0.08

Commodity Sub-weights: - Energy: 0.40, Metals: 0.40, Agriculture: 0.20

Smoothing Factors: - Daily EWMA (CPI, FX, Commodity): λ = 0.97 - Daily EWMA (Crypto): λ_K = 0.995

Outlier Clamps: - CPI: ±3σ, FX: ±3%, Commodity: ±5%, Crypto: ±5%

Rebalancing Cadence: - Quarterly: March 31, June 30, Sept 30, Dec 31 - Drift trigger: >2% off target

B. Data Source URLs and API Endpoints

C. Smart Contract Interface Specifications

ESPToken (ERC-20)

interface IERC20Extended {
  // Standard ERC-20
  function transfer(address to, uint256 amount) external returns (bool);
  function approve(address spender, uint256 amount) external returns (bool);
  function transferFrom(address from, address to, uint256 amount) external returns (bool);
  function balanceOf(address account) external view returns (uint256);
  function allowance(address owner, address spender) external view returns (uint256);
  function totalSupply() external view returns (uint256);

  // Extended
  function mint(address to, uint256 amount) external onlyMinter;
  function burn(uint256 amount) external;
  function pause() external onlyPauser;
  function unpause() external onlyPauser;
}

ESPMinter

interface IESPMinter {
  function requestMint(uint256 espAmount, address collateral, uint256 collateralAmount) external;
  function fulfillMint(uint256 requestId) external onlyFulfiller;
  function requestBurn(uint256 espAmount) external;
  function fulfillBurn(uint256 requestId) external onlyFulfiller;
  function getMintRequest(uint256 requestId) external view returns (MintRequest memory);
}

ESPReserveOracle

interface IESPReserveOracle {
  function submitIndexValue(uint256 newIndex, bytes[] calldata signatures) external onlyOracleCommittee;
  function getLatestIndex() external view returns (uint256);
  function getIndexHistory(uint256 lookback) external view returns (uint256[] memory);
  function getComponentBreakdown() external view returns (Components memory);
}

D. MiCAR Article Cross-Reference Table

FINAL IMPLEMENTATION ROADMAP

Immediate Actions (Next 30 Days)

1. Legal: File GmbH + Foundation incorporation documents with Austrian notary
2. Technical: Begin smart contract development (internal); setup testnet (Sepolia)
3. Compliance: Hire external compliance officer (part-time); draft FMA pre-application
4. Finance: Open business bank account (Vienna); secure €50K founder capital

Critical Path to Mainnet (Months 1–7)

• Month 3: FMA pre-application approval → confidence to proceed
• Month 4: Testnet live with 4-week trial → community feedback incorporated
• Month 5: Full FMA application submitted → clock starts on authorization
• Month 7: Authorization received OR escalate to alternative jurisdiction → launch mainnet

Success Metrics (Year 1 Goals)

• Regulatory: FMA ART Issuer authorization granted ✓
• Operational: <0.5% daily tracking error vs. INDEX ✓
• Market: €5M—€10M AUM achieved; €1M+ daily trading volume ✓
• Tech: Zero security incidents; 99.9% uptime ✓
• Business: Break-even on Year 1 ops; clear path to profitability Year 2 ✓

Document Version: 1.0 Last Updated: March 30, 2026 Next Review: June 30, 2026 (quarterly) Approval: Founder + Compliance Officer (Signature fields to be completed post-review)

END OF DOCUMENT