THE SHORT VERSION / READ THIS FIRST
A public black-box lock with a private search.
VAULT turns a hidden combination into a live competition. Everyone sees the same lock, the same public readings, and the same clicks. Your agent keeps its exact guesses private while it spends a limited attempt reserve to learn the shape of the answer.
MODE LIVE RACE
FEEDBACK ONE SCALAR
WIN CONDITION FIRST CRACK
LOCK6pins in sequence
DIAL RANGE100positions per pin
SEARCH SPACE10^12raw combinations
OUTPUT0—100one reading per run
02
Black-box lock protocol
The lock is difficult because it gives you a useful signal without telling you which dial produced it.
01 / BINDING ORDER
One pin matters at a time.
The lock has a hidden order. Pins before the current one are already set; pins after it are invisible. Touch a solved pin and the reading collapses.
02 / PUBLIC ORACLE
Every run returns one number.
The reading combines pins already set with proximity on the current binding pin. There is no per-pin breakdown and no “warmer on pin 3” message.
03 / COLLAPSE
Protect the work you already did.
A sharp drop means you disturbed a pin that was set. Restore it before searching again. Solved pins are progress, not spare dials.
04 / SHIFT
Find the pin that is speaking.
A small movement means that pin is binding. Work it deliberately until the click. The next hidden pin then becomes active.
reading = (pins set + proximity on binding pin) ÷ total pins × 100
03
Agent system
Your agent is the instrument that turns limited information into a better search. Training changes how it reads; holding changes how long it can stay in the race.
RESERVE
Attempts are the scarce resource.
Each live run spends one attempt. The configured token mint and holder-data source must verify your balance and holding age: balance raises capacity, holding age adds capacity and faster regeneration. Selling below the qualifying position or losing verification locks the bank—no new attempts accrue or spend until it is verified again.
PRECISION / MEMORY
Training makes information usable.
Precision reduces reading noise. Memory preserves more of your search history and unlocks deeper analysis of previous runs.
INTUITION
Sometimes the lock tells on itself.
Intuition gives your agent a chance to receive a tell naming the current binding pin. It is a probability, not a shortcut you can force.
AUTO-RUN
Leave a search policy running.
Auto-run keeps a belief state and selects the next probe from your policy. It is competent enough to keep the vault active, but a focused person can still outperform it.
04
System map
These are the boundaries that matter when you are deciding whether to trust a reading or a payout.
01
WALLET
Sign a one-time challenge. The server uses the verified wallet to authorize your agent.
02
AGENT
Your stats, policy, reserve, logs, and workshop progress live on the server.
03
LOCK ORACLE
A valid run is checked against the secret. Only the scalar reading and public click are broadcast.
04
EVENT STREAM
SSE pushes state, standings, clicks, and runs to every connected viewer in real time.
vault:// wallet signature → agent state → lock attempt → scalar reading → public event
05
Trust & settlement
Read the boundary between what the app observes and what the operator controls.
PUBLIC
What everyone can see.
Round state, vault balance, readings, clicks, standings, agent names, and crack history. Exact dial values are never broadcast.
PRIVATE
What stays with your agent.
Guessed positions, your attempt log, policy, wallet-authorized profile, and workshop decisions are not part of the public feed.
Settlement boundary: the vault balance is read from Solana, while the lock, readings, and ledger are computed by this server. The operator settles payouts from the treasury. This app holds no treasury keys and sends no transactions.
Not investment advice. Technical behavior may change as the game moves toward a claim contract.
VAULT
