Security Model

Contract controls

• two-step ownership transfer
• reentrancy guards on financial state transitions
• explicit owner checks for positions and sessions
• keeper allowlist
• session action, market, size, collateral, leverage, expiry, revocation, and nonce checks
• protocol and market pause or reduce-only controls
• slippage, freshness, confidence, leverage, open-interest, skew, and vault checks
• atomic conditional state transition and action

Oracle controls

Testnet reports are domain-separated and include short validity windows, source timestamps, confidence, market IDs, bid/ask, and rounds. Reports are transaction-scoped and cannot become a lasting cached protocol price.

The residual testnet risk is signer trust. Whoever controls the authorized oracle key can sign a false price.

Infrastructure controls

• private Postgres and worker networking
• server-only provider and keeper credentials
• one writer and one executor replica
• transaction simulation
• receipt confirmation and deduplication
• confirmation-aware indexing and reorg rollback
• public deployment manifests contain no secrets

Testing

The repository includes Solidity unit, fuzz, and invariant coverage plus indexer and keeper tests, web typechecking, deployment verification, funded lifecycle, realtime oracle, and delegated-intent end-to-end scripts.

Tests reduce risk but do not substitute for an external audit, production oracle assurance, economic review, operational redundancy, or legal review.

User responsibilities

• verify the Robinhood Chain testnet network and contract addresses
• review every wallet transaction and typed-data signature
• use short session expiry and narrow limits
• revoke unused sessions
• avoid using real funds with testnet contracts
• treat natural-language parsing as a draft, not authority

Current deployment

Veyronn currently runs on Robinhood Chain testnet. Mainnet activation adds the production oracle, reviewed governance and key management, external audits, infrastructure redundancy, production collateral policy, and launch controls documented in the Mainnet Readiness checklist.