From equity thesis
to explicit operation.

Quick start

The shortest path from an idea to a reviewed operation has four steps.

1. 01
   Stress the model

   Use Economics to change price, annual distributions and the discount rate, then inspect the resulting principal and yield values.

2. 02
   Connect a wallet

   Open Operations and connect MetaMask or another injected EVM wallet. The app requests Robinhood Chain Mainnet automatically.

3. 03
   Initialize the prototype

   Deploy a personal prototype registry once. It cannot receive ETH or debit ERC-20 assets, but normal network gas applies.

4. 04
   Record an operation

   Review the displayed parameters and submit one nonpayable call. The resulting receipt confirms that the prototype event was recorded; it does not represent a financial transfer.

System architecture

The product is split into four bounded layers. Each layer can fail closed without forcing the others to invent state.

Financial state never flows directly from a visual control to a signer. The operation engine produces an immutable manifest first; execution adapters accept only a validated manifest after separate user approval.

Operation lifecycle

Every financial action advances through explicit states. The interface uses the same language as the underlying lifecycle so a button never implies more progress than has actually occurred.

Supported operation intents

{
  "version": "qnt-manifest/0.1",
  "environment": "robinhood-chain-mainnet",
  "chainId": 4663,
  "action": "split",
  "asset": "AAPL",
  "amount": "1.000000",
  "expected": ["1.000000 P-AAPL", "1.000000 Y-AAPL"],
  "oracleState": "SYNCED",
  "broadcast": "deployment-gated"
}

Separation model

A position starts as one Stock Token exposure and becomes two analytical legs with the same combined reference value. The yield leg is the discounted value of expected quarterly distributions through maturity; principal is the conserved residual.

// Present value of expected quarterly distributions
yieldLeg = Σ dividend[t] / (1 + discountRate) ** t

// Principal is the conserved residual
principal = max(spot - yieldLeg, 0)
principal + yieldLeg === spot

Scenario stress testing

The Economics Lab applies bounded shocks without mutating the base series. A scenario may change the reference spot, annual distribution and discount rate; maturity and long-run growth remain tied to the selected series.

The sensitivity matrix adds ±25% distribution moves and ±150 bps rate moves around the active scenario. Every cell is recomputed with the same quarterly cash-flow schedule.

Oracle and accountant states

The oracle layer watches a normalized multiplier and separates economically different events before a risk model consumes them.

Consumer rule

const response = await fetch('/api/oracle?token=AAPL');
const { tokens, asOf } = await response.json();
const accountant = tokens[0];

if (accountant.status !== 'SYNCED') {
  pauseRiskIncreasingActions();
}

useIndex(accountant.dividendIndex, { asOf });

Consumers must check both classification state and freshness. A syntactically valid number is not automatically an executable price.

Lending risk model

The lending interface treats a principal leg as collateral, applies the oracle value, and expresses risk through loan-to-value and health factor.

Application API

The release candidate exposes chain metadata alongside model and oracle fixtures. Every state-changing intent remains explicit and deployment-gated.

Response invariants

• Amounts are decimal strings or documented numbers; never infer token decimals from display formatting.
• A consumer must reject unknown status values instead of treating them as synced.
• Timestamps describe the fixture or indexed block, not the browser request time.
• Production responses must add chain ID, contract address, block number and finality metadata.

Robinhood Chain profile

Quantaire targets Robinhood Chain Mainnet. The wallet adapter, operation manifests and deployment registry all resolve to the same production network.

Contracts and wallet boundary

The browser adapter connects through EIP-1193, requests chain 4663 and verifies the exact runtime bytecode of QuantairePrototypeExecutor before every operation. Split, Merge, Supply and Borrow are encoded only as event metadata. The adapter contains no approval or token-transfer execution path.

Protocol contracts

Required adapter methods

Security model

The current prototype records operations without moving assets. Calls use zero transaction value, require an exact bytecode match and cannot invoke token approvals or transfers. Missing metadata, an unexpected chain or a contract mismatch stops progress before a wallet prompt appears.

Never do this

• Never request a seed phrase or private key.
• Never hide a token approval inside another action.
• Never treat an RPC submission as transaction success.
• Never retry a state-changing transaction with a new nonce automatically.
• Never enable production execution with placeholder addresses.

Release gates and mainnet procedure

Financial execution remains disabled until every gate has accountable, immutable evidence. A machine-readable readiness check exits non-zero while any item is open, and the read-only preflight rejects stale or near-heartbeat oracle data.

Required sequence

1. 01
   Compile and test

   Build exact artifacts, execute local EVM lifecycles and preserve output with the release commit.

2. 02
   Run read-only preflight

   Verify chain 4663, token bytecode, decimals, feeds, maturities, owner balance, gas and deploy bytecode hash.

3. 03
   Close review gates

   Complete audits, economic review, caps, multisig, timelock, monitoring and incident ownership.

4. 04
   Deploy in stages

   Deploy the Series Manager first. Lending remains a separate opt-in decision after additional controls exist.

5. 05
   Verify runtime

   Compare deployed bytecode, owner and configuration through two independent RPC endpoints and Blockscout.

6. 06
   Initialize series

   Create each series separately from reviewed calldata and reconcile every emitted address and maturity.

7. 07
   Transfer ownership

   Complete two-step ownership acceptance by the approved multisig and retire the deployer.

8. 08
   Canary, pause, review

   Run minimum-value flows, reconcile custody and accounting, pause again, then approve activation separately.

pnpm contracts:build
pnpm contracts:test
pnpm test
pnpm contracts:readiness
OWNER_ADDRESS=0x... pnpm contracts:prepare:mainnet
SERIES_MANAGER_ADDRESS=0x... EXPECTED_OWNER_ADDRESS=0x... pnpm contracts:verify:mainnet

Glossary

Current release limits

Prices, rates, indexes, event schedules and market totals remain deterministic fixtures. Entered operation amounts are illustrative metadata. Wallet state comes directly from the user's EVM provider and is never stored remotely.