Stock Agents
Implementation roadmap

Mainnet progress measured by evidence.

This roadmap separates implemented custody, execution, and automation from release verification and unsupported product ideas. A feature name never overrides a failed runtime check.

Create wallet accountRead product documentation

Statuses describe implementation and release gates, not returns, legal approval, or a guaranteed date.

Current product state
Three labels with deliberately different meanings.

Exportable account custody

Implemented

Wallet creation, address sign-in, encrypted signing, password-gated export, and legacy activation are wired.

USDG Stock Token execution

Fail closed

Every operation remains unavailable unless live configuration, chain, route, price, gas, balance, and eligibility checks pass.

Additional asset families

Unavailable

No arbitrary-contract execution path or automatic asset-admission process is enabled or promised.

The explicit live-trading switch is necessary but never sufficient; all runtime checks still apply.
Product boundary

Implemented does not mean unrestricted.

The mainnet path is deliberately narrow. Unsupported funding assets, contracts, recovery promises, and compliance claims stay outside the product.

Implemented product paths
Available when their live checks pass
Implemented
  • Create a real exportable Robinhood Chain EOA during signup
  • Sign in with a wallet address while preserving legacy email accounts
  • Sync confirmed USDG deposits and live native ETH gas balances
  • Preview supported Stock Token routes, expected output, and buffered gas
  • Run initial allocation and scheduled rebalancing as durable workflows
  • Pause, proportionally unwind to USDG, export the key, or withdraw USDG

Onchain actions remain irreversible and can lose value.

Not available
No hidden or simulated fallback
Unavailable
  • Use WETH as agent principal or external withdrawal currency
  • Trade a contract outside the 18-symbol Stock Token allowlist
  • Treat a Stock Token as direct ownership of the referenced share
  • Recover or reset a lost Pons password through email
  • Treat the technical country gate as legal or KYC approval
  • Automatically admit or trade a newly discovered contract

These boundaries are intentional, not incomplete marketing states.

Release path

Build the narrow path, then prove it.

Custody, execution, and workflow implementation are tracked separately from operational verification and any future expansion in asset scope.

  1. PHASE 01Implemented

    Exportable account wallet

    New accounts receive a real Robinhood Chain EOA. Pons stores its key with authenticated encryption for unattended agents and permits password-gated export.

    • Wallet-address sign-in
    • One-time signup backup
    • Password-gated key export
    • Legacy wallet activation
  2. PHASE 02Implemented

    USDG Stock Token execution

    The trading path quotes allowlisted contracts through verified Uniswap V3 infrastructure and settles purchases and sales in USDG.

    • 18 supported Stock Tokens
    • Chainlink freshness checks
    • Direct and WETH-intermediate routes
    • Receipt-derived accounting
  3. PHASE 03Implemented

    Durable agent schedules

    Initial allocation and Daily, Weekly, or Monthly rebalancing run as durable workflows with stable operation keys and server-side ownership checks.

    • Resumable initial allocation
    • Sell-before-buy rebalancing
    • Pause and resume controls
    • Proportional USDG unwind
  4. PHASE 04Hardening

    Operational release gates

    Mainnet writes remain fail-closed while chain preflight, signer configuration, gas, balances, price freshness, route sanity, and eligibility are verified.

    • Read-only mainnet verification
    • Secret-safe failure reporting
    • Browser and auth regression checks
    • Workflow retry validation
  5. PHASE 05Release-gated

    Production operations

    The production write switch remains a deliberate operational decision after automated checks pass, with monitoring and incident controls kept outside agent permissions.

    • Explicit production enablement
    • Receipt and route monitoring
    • Incident pause procedures
    • No automatic asset admission
Live-write readiness

Eight gates stand before every release.

No single green check compensates for a missing secret, stale feed, invalid route, unsafe wallet state, failed eligibility decision, or unverified build.

Configuration gate
Required

The dedicated RPC, 32-byte wallet encryption key, and explicit live-trading switch must all be present and valid.

GATE 01: Missing or invalid configuration leaves writes disabled.

Chain gate
Required

The RPC must report chain ID 4663 and expose bytecode at the verified settlement, factory, quoter, router, and routing-intermediate contracts.

GATE 02: Every expected contract relationship matches live metadata.

Asset and feed gate
Required

Each supported token must match its allowlisted address, symbol, decimals, and positive completed Chainlink round within the freshness window.

GATE 03: Unavailable or stale assets remain visible but cannot be allocated.

Routing gate
Required

A direct or WETH-intermediate V3 path must return positive output and stay within the allowed deviation from reference prices.

GATE 04: No route is guessed when quotation or sanity checks fail.

Wallet safety gate
Required

Ownership, custody state, onchain balances, attributed holdings, exact allowance, pending nonce, and buffered native gas are checked before signing.

GATE 05: Concurrent or underfunded wallet writes cannot proceed.

Eligibility gate
Required

Buy-side operations require a current eligible audit result based on residence attestation and the request-country signal.

GATE 06: Restricted, missing, invalid, or expired decisions block acquisitions only.

Accounting gate
Required

Execution records retain stable operation keys, expected hashes, confirmation data, and sanitized failures. Holdings update from successful receipts and deltas.

GATE 07: A pending, reverted, or uncertain transaction never becomes a position.

Release verification gate
Required

Type, build, unit, workflow, auth, browser, and read-only mainnet checks must pass without broadcasting automated test funds.

GATE 08: Production writes stay behind the explicit switch until verification is complete.

Safety invariants

Rules that roadmap progress cannot weaken.

These boundaries apply to interactive actions, automatic retries, scheduled runs, and future product changes alike.

  • Private keys never enter database plaintext, workflow inputs, logs, analytics, or user-facing errors.
  • Every query and mutation touching account data is scoped by the authenticated user or revalidated workflow ownership.
  • The asset allowlist, maximum position, slippage minimum, route, gas, eligibility, and reconciliation checks cannot be bypassed by UI state.
  • Sells, key export, and USDG withdrawals remain reachable when acquisitions are restricted.
Review before funding

Understand custody and execution first.

Read the full documentation, back up the wallet key, then use the live preview before approving a Stock Token mandate.

Read the docsCreate wallet account