Skip to content

USDG Vaults

user

Permissionless USDG creator vaults on Robinhood Chain: shares, fuses, receipts, deposit-readiness gates, and the full product path.

USDG Vaults on Robinhood Chain — with HISS fuses in the loop. Anyone can create a public USDG vault, depositors receive vault shares, and vault strategies rebalance into source-verified Robinhood Chain tokenized assets under binding HISS fuse rules. Every action writes a deterministic, database-backed receipt.

Chain architecture

  • Vault chain: Robinhood Chain — mainnet 4663, testnet 46630, ETH gas.
  • Base asset: USDG on Robinhood Chain (6 decimals, canonical contract source-verified).
  • Rebalance universe: source-verified Robinhood Chain Stock Tokens and tokenized ETFs.
  • Payments: x402 payments may use Base where configured — Base is never the vault chain.
  • Boundary: Robinhood MCP is not used for pooled vault execution. The Bankrbot → Robinhood MCP path stays per-user, per-account, and unpooled.

The vault lifecycle

  1. A creator configures a vault in the creation wizard: source-verified assets, 17 binding fuses, bounded fees, disclosed lockup.
  2. Vault candidates are free to save. Publishing a public vault onchain carries a one-time 50 USDG launch-beta creation fee, and the creator seeds at least 5% of TVL as skin in the game before public deposits can open.
  3. The VaultFactory deploys the vault on Robinhood Chain mainnet (chain id 4663) from the creator's own wallet.
  4. Public deposits open only after the public deposit gate passes — contract audit, disclosures, oracle, and liquidity checks — and each vault is marked ready in the on-chain deposit readiness registry.
  5. Depositors accept the risk acknowledgment, deposit USDG, and receive vault shares — sharing profits and losses.
  6. Rebalances compile through HISS fuse checks and write receipts plus post-rebalance audits.

Checking live state: deployment, gate, and vault status are machine-verified — read GET /api/vaults/readiness (or GET /api/status) rather than trusting copy, and see vault contract status for the truth rules. Unknown/unavailable is not the same as not deployed: a failed status fetch never means contracts are undeployed or deposits are closed, and a degraded live check means the page is using last verified status.

What HISS is here

The compiler, fuse verifier, receipt layer, and marketplace. HISS is not a broker-dealer, investment adviser, custodian, or order router. Vault performance depends on creator strategy and markets: past performance is not a guarantee of future returns, and no vault offers guaranteed yield of any kind.

Read next

Agent skill file

Working with Bankrbot, an MCP agent, or another compatible agent? Hand it the canonical HISS operating manual: /skill.md (the agent skill file).