SYLVAULT
/

AUTONOMOUS TREASURY · ROBINHOOD CHAIN TESTNET · 46630

syncing···

SYLVAULT

THE VAULT THAT GROWS ON FEES

Every swap on the $SYLV pool pays a toll. A vault contract collects the toll and routes it through five fixed pipes — burn, stock reserves, dev ops, liquidity, chaos. The split is carved into bytecode. Nobody decides. Nobody refunds.

$SYLV trades on a constant-product pool with a 4.2% toll; 2.5 points of every toll belong to the protocol. When the harvest runs, the vault claims what the pool owes and cracks the pot in one transaction: 40% buys and burns $SYLV off the market, 40% fills stock reserve positions, 10% funds dev ops, 5% adds liquidity, and 5% is spent on chaos — deliberately inefficient value that keeps the treasury from becoming a payoff matrix anyone can farm.

The harvest itself is a public utility. Anyone can run harvest() from any wallet — the caller pockets 0.25% of the claim plus rounding dust as a keeper fee. Each pipe executes isolated under try/catch: a route that fails leaves its funds pending and retries next run; the rest of the vault proceeds regardless.

This edition runs on the Robinhood Chain testnet (chain 46630) where gas is paid in native ETH. Feeds are simulated on testnet; the mainnet edition plugs into real equities prices and ships after the external audit.

THE SPLIT40 / 40 / 10 / 5 / 5 — SET IN BYTECODE
  • buy & burn 40%
  • stock reserves 40%
  • dev ops 10%
  • liquidity 5%
  • chaos 5%

TRADE $SYLV RUN THE HARVEST

harvested · usdc···
$sylv burned···
live supply · sylv···
pool price · usdc···
pending claim · usdc···
harvest window···
SYLVAULT TERMINAL
02

Live

POOL RESERVES · ROLLING PRICE · KEEPERS
SYLV / USDC · MAIN POOL—

$ —

rolling window of live pool prints · one tick every refresh · flat line until the second print lands

POOL LIQUIDITY · USDC···
$sylv IN POOL···
KEEPER PAID · USDC···
SUPPLY BURNED···
03

Trade

MAIN POOL · USDC ⟷ $SYLV

ORDER TICKET/ desk

SIDE

EST. OUT—

no wallet

Constant product, honest toll

The desk quotes against live pool reserves with the 4.2% toll already deducted — 2.5 points feed the vault, the rest pays liquidity. Orders carry a 3% slippage guard baked into the call. What the ticket shows is what the pool math does.

The swap itself is a direct pool call — no router, no intermediary contract between you and the reserves. Approvals go to the pool and only the pool.

tip: file swap 100 buy at the console — section 11.

04

Positions

40% OF EVERY HARVEST LANDS HERE

Nine perpetual stock positions — half swap, half LP, guarded by feed-staleness and drift checks. The testnet edition runs simulated feeds; mainnet plugs into real equities prices.

9 ASSETS EQUAL WEIGHT 50 / 50 SWAP-LP ±3% TWAP GATE
tickerfeed pricestatusposition pool
05

Routes

40 / 40 / 10 / 5 / 5 — SET IN BYTECODE
HOW A FEE IS DIVIDEDLIVE ROUTE LEDGER
  1. 40% buy & burn —
  2. 40% stock reserves —
  3. 10% dev ops —
  4. 5% liquidity —
  5. 5% chaos —

THE RECEIPT

  1. 01 · a swap pays its tollevery $SYLV swap on the pool pays 4.2%; 2.5 points belong to the protocol
  2. 02 · anyone runs the harvestharvest() is permissionless — the caller pockets 0.25% + dust for the trouble
  3. 03 · the pot cracks40 / 40 / 10 / 5 / 5 — constants in bytecode, not entries in a config table
  4. 04 · pipes run aloneeach route executes isolated under try/catch; a failed pipe waits, the rest proceed

INV-1 ···claimed = keeper + pending + paid

06

Harvest

PERMISSIONLESS KEEPER CONSOLE

fn harvest()— claims pool fees, fires all five routes in one tx

NEXT WINDOW···

MINIMUM CLAIM···

connect a wallet to run it

The harvest is a public utility

Live testnet, same bytecode that flies on mainnet. The keeper console is open to any address, any wallet, no allowlist. Rate-limited by a cooldown — 60 seconds in the testnet edition, one hour planned for mainnet.

When you run it, the vault claims everything the pool owes, pays you the keeper fee, and fires all five routes before the block closes. Watch section 07 — the ledger writes itself the moment your transaction lands.

tip: file harvest at the console once connected.

07

Ledger

LAST 12 VAULT ENTRIES · APPEND-ONLY
  1. reading the ledger···
08

Guards

SAFETY GATES ON EVERY ROUTE
G/01 TWAP drift gate
Before any pool trade, spot must sit within ±3% of the 30-minute TWAP. Manipulation inside the window is refused, not punished.
G/02 Feed staleness & pause
Stock routes skip any asset whose oracle is older than 15 minutes, paused, or negative. Skips are events, not errors.
G/03 Pool impact cap
No single route moves more than 0.5% of a pool per execution. Oversized amounts batch across future harvests.
G/04 Rollback isolation
Pipes run as external self-calls under try/catch with a 4M gas cap. A failing pipe leaves its funds pending — never takes the harvest down.
G/05 Timelocked custody
Fee-recipient and dev-treasury changes need a request/confirm delay — 24 hours on mainnet. The world watches the intention first.
G/06 Self-auditing ledger
INV-1 asserts claimed = keeper + pending + paid after every harvest. INV-4 asserts the vault holds zero $SYLV when the dust settles.
09

FAQ

THE FINE PRINT
What exactly is Sylvault?
An autonomous treasury. $SYLV trades on a pool; the pool fees are periodically claimed by a vault contract and split along five fixed routes — buy&burn, stock reserves, dev ops, liquidity, chaos. No human in the loop, no off-chain infrastructure: the whole vault is bytecode.
Who can call harvest?
Anyone, from any wallet. The caller receives 0.25% of the claim plus rounding dust as a keeper reward. Harvests are rate-limited by a cooldown — 60 seconds on testnet, one hour planned for mainnet.
What happens if a route fails mid-harvest?
Nothing catastrophic — by design. Each route executes as an isolated external call wrapped in try/catch under a gas cap. If it reverts (stale feed, drift gate, thin pool), the amount stays pending for that route and every other pipe completes normally. The failed amount retries next harvest.
Are the stock positions real?
On testnet they're simulated — mock feeds push plausible prices for SPY, NVDA, TSLA and six others so you can watch the routing work end to end. On mainnet the same code consumes real equities price feeds and real position tokens.
Why does 5% go to "chaos"?
A treasury that can only do sensible things is a treasury that can be modeled, front-run and farmed. The chaos route buys a volatile side asset and burns it — deliberately inefficient value that keeps the system from becoming a deterministic payoff matrix.
Can the weights or destinations be changed later?
Not by any key we hold. The split lives in the vault's bytecode as constants. The owner role can rotate operational parameters (cooldowns, caps, asset list) — all timelock-protected and visible on-chain — but re-weighting would require deploying an entirely new protocol nobody is obliged to follow.
Why is gas paid in ETH?
This edition runs on Robinhood Chain, an Arbitrum-based L2, where the native gas token is ETH. Your wallet pays fees straight from its ETH balance — the Robinhood Chain testnet faucet at faucet.testnet.chain.robinhood.com funds new addresses with 0.01 ETH every 24 hours.
When mainnet?
After the external audit completes and timelocks are extended to production values. Watch @sylvault_fun — the launch announcement is the only signal worth trusting.
10

Community

WATCH THE VAULT WORK

Every harvest is a public event.

The vault does not do private deals. Each harvest, each route, each skip lands on-chain where anyone can read it — the ledger above is a live mirror, not a summary. Follow the account for launch signals; read the contracts for everything else.

FOLLOW @SYLVAULT_FUN READ THE VAULT
  • announcement channelx.com/sylvault_fun
  • home of the vaultsylvault.fun
  • keeper reward0.25% + dust
  • cooldown · testnet60 seconds
  • routes · fixed40 / 40 / 10 / 5 / 5
  • discretionnone
11

Console

FILE A COMMAND TO THE VAULT