Nave: autonomous treasury OS (docs, agents, multi-chain)

Nave is an autonomous treasury operating system for on-chain organizations. A treasury ratifies a constitution. An AI agent layer proposes and reviews. On-chain programs enforce and execute. Docs live at /docs as in-app pages (start /docs/introduction). There is no docs.nave.finance and no public OpenAPI. X @navedotfinance.

Three rules from the intro: the constitution sets approved protocols, caps, floors, confidence thresholds, and cadences. Four agent roles (Executive, Financial, Oversight, Operational) propose and review. They hold no unilateral authority. The chain is the authority.

What the docs actually are

Technical reference for operators, developers, and partners. Tracks: Getting Started, Treasury Operations, Architecture, Investment Overview. Getting Started says Nave is a devnet beta and never touches mainnet funds. Use Solana Devnet, Ethereum Sepolia, or Base Sepolia. Reading a treasury needs no deposit.

Intro also says a treasury can be created on Solana, Ethereum, or Base. $NAVE (Nave Shares) moves between Solana and supported EVM testnets on a dedicated bridge. Tokenomics: ticker $NAVE, max supply 500,000, 6 decimals, no team allocation. Devnet faucet: 0.1 NAVE / 24h if the Solana address holds at least 0.01 devnet SOL.

Architecture a developer can use

Four layers: Vite React client, application backend (Supabase Postgres + edge functions), a Node signer/relayer, on-chain programs. Solana programs are Anchor. EVM treasuries are Solidity on Ethereum and Base. Solana events via a Helius raw webhook. EVM via an event indexer.

The architecture page names signer routes POST /sign, /relay-evm, /bridge-relay, /faucet-claim. Integration says read state from published Anchor IDLs and PDAs. There is no public REST catalog. Agents are advisory. Signer actions on nave_execution: executive_approve, financial_approve, oversight_approve, operational_halt, operational_clear.

Constitution (on-chain rules)
  -> AI agents (propose + review)
  -> Deterministic guardrails
  -> On-chain programs (enforce + execute)
  -> Treasury

Live client program ids (from the deployed app config): core 8GSh9ghC2EL88X9FwftiH2QDrm8drvgSLAUoo45gN5nB, governance CwFouCjZyBrpLGuKvd9VXQqYh4ZYyT9yUQbqmo6k7n9M, execution 2sGy7WwF6uGCyBmPqohRtobmutGhKjr2AG2FKvfcpYzb. Adapters exist for Kamino and Jito. Jupiter Lend is marked beta. MarginFi is behind a flag. Architecture says canonical IDs are the deployed devnet set and can be overridden per instance.

Resources

• Docs index
• Architecture
• Integration