Silent Partner
testnet

Risks & trust

What can go wrong, who controls what, and what anyone can see. Read it before you put money in.

What can go wrong

A bug in the contract

The contract hasn't had a professional audit. It has had two independent security reviews and property tests that throw thousands of random cases at it. That's not the same as an audit, so put in only what you could lose.

We stop running

If no new share price is posted for 24 hours, or a withdrawal goes unpaid for 24 hours, anyone can switch the vault to emergency mode. Every holder then takes their share out at the last price. You don't need us for that. In emergency, payouts come from what's actually in the vault, in rounds: anyone can start a round, the vault reads its own balance and splits it pro rata over everyone owed, so the last one out gets the same fraction as the first. That's live on testnet (the drill2 vault); the mainnet vault still runs the earlier build, where emergency payouts are fixed at the last price.

A swap fails

Trades go through 1Click, NEAR's swap service. A trade that doesn't fill just doesn't happen; the vault keeps what it had. A deposit from another chain that fails is refunded to the address you gave.

NEAR AI is down

AI leaders ask a model running in a secure enclave what to do. If it can't be reached, they hold: no answer, no trade.

Testnet isn't real money

The leaderboard is a paper season: testnet tokens, real market prices. One small mainnet vault holds real USDC to prove the full path works. This site shows it read-only.

Who controls what

The vault's key

Can: Can sign only trades that bring the money back into the vault at a 1Click-signed price, and payouts to a holder's own account.

Can't: Nobody holds it. It's split across NEAR's MPC network and tied to the contract.

The operator (us)

Can: Sees what the vault holds, places the leader's trades and posts share prices. The contract rejects any price that doesn't fit two 1Click-signed market quotes.

Can't: Can't send funds anywhere else. If we stop, the emergency exit opens.

The leader

Can: Sends trade signals. Must keep at least 10% of the vault in their own money, and the contract checks.

Can't: Can't withdraw your money, see who you are, or trade outside the vault's allowed assets and slippage.

One thing we can still change: the code

The mainnet vault's account still has a full-access key, held by the builder, until November 25, 2026. With it the contract code can be redeployed, and new code could change what the vault's key will sign. We kept it so a bug found during the hackathon review can be fixed. After November 25 the demo vault is wound down: holders are paid out and the account is deleted. A real-money vault would launch with that key deleted and its build hash published, so anyone can check the code can't change. The testnet vaults keep their keys too; they hold paper money.

What's public, and what isn't

Public: deposits and withdrawals (they're ordinary NEAR token transfers, so amounts and accounts show on NearBlocks), share balances, the share price, the leader's stake and the vault's size, rounded.

Sealed: what the vault holds, every trade and fill, and when the leader trades. Not even followers see them. See exactly what the chain shows →

We count page views, with no cookies and nothing about you. Totals per page and per day only, skipped under Do Not Track; the counts are published in the season log.

The detail

Every attack we considered and what stops it is in the threat model. Every mainnet transaction is listed in docs/mainnet.md. The code is open source.