THE MICROSCOPIC MAINNET SEED
Connect your wallet, review the costs, and approve in your wallet. We confirm the result before showing your next action. Every trade needs its own approval.
This owner controller verifies the signed mainnet release, wallet accounts, HedgAI qualification, and a free Lane 1 planning check before composing anything. The verified activated controller prepares authenticated owner Cranks, reviews Jupiter Swap V2 /build routes against the dual-authority registry, proves finality, reconciles accounting, and exposes reviewed cycle transitions. The kernel never moves JUP/USDC by itself; every successful Crank contributes exactly 100 disclosed lamports to the Agent Zero Keeper buildout wallet.
Wallet controls unlock only after the frozen Program ID and release hashes pass every launch gate.
Runtime Program ID, ProgramData, ELF hash, and retained upgrade authority remain unavailable until the founder-signed runtime release verifies. A retained authority can replace code between readback and execution; controls stay locked until this risk and the exact identities can be shown for owner review.
CAPTAIN CONSOLE
Exact mainnet owner, available SOL, canonical JUP/USDC accounts, and finalized HedgAI qualification. Exact operation funding is checked only at review.
Controls are release-locked.
First create your Mission, then review your JUP purchase.
During setup, Solflare shows “No change” for HedgAI, JUP and USDC. Only SOL setup costs apply. After confirmation, check the next action for free; each trade has its own review and wallet approval.
The free check decides whether the next owner-reviewed step is initial entry, average-down add, average-up add, full exit, fund, or wait.
Personal-wallet Mission initialization, Human/mobile Cranking, and reviewed lifecycle operations are available only when this page verifies the embedded dual-authority activation binding against the active release. A successful Crank contributes exactly 100 lamports; failure contributes zero.
No finalized Mission has been read.
Connect your wallet to check your next step.
Return to wallet verificationThe deployed kernel can issue these cards. Public human card creation is available only through fresh authenticated evidence and the verified dual-authority activation boundary.
The direct-Metis review, owner handoff, finalized-delta proof, and separate reconciliation controller are available only after the exact embedded dual-authority Agent Zero attestation verifies. Every trade remains owner-reviewed, owner-signed, finalized, and separately reconciled.
NINE-WALLET ONION
Trinity remembers only public wallet addresses in this browser. It never stores recovery phrases or private keys, and it never switches wallets or trades a layer without you.
Start Layer 1 first. After its Mission exists, Trinity will show the planning reference for a wallet roughly 15% lower.
Important: the deployed kernel currently exits at a minimum 2% profit plus bounded costs and a 1% contingency—not the proposed 10% layer target. A 10% rule needs a separate reviewed on-chain policy upgrade before the site can enforce or advertise it as live.
FREE PRE-CHECK QUEUE
Finalized wallet state and quote-only market checks are read first. Merely viewing this list sends no transaction and pays no Keeper contribution.
OWNER-SIGNED OPERATION
The verified successor controller can create canonical token accounts, initialize a Mission, check the current strategy threshold, request authenticated owner actions for initial entry / average-down add / average-up add / full exit, reconcile finality, finalize a cycle, and start the next cycle. Every signature still follows exact release, registry, adapter, account, fee, and unsigned-transaction review; there is no background crank, delegated key, or automatic trade.
The signed runtime release, live ProgramData, wallet accounts, and fresh market evidence must all verify first.
MANDATORY PRE-SIGN SUMMARY
Snapshot estimate only. Mission X is derived from the current JUP price; Jupiter minimums, price movement, slippage, network fees, and future fills can change actual USDC requirements.
The release manifest must validate before planning estimates appear.
Before the owner signs, the site must show the exact Mission X, JUP quantity, estimated USDC, remaining capacity, wallet shortfall, and 100-lamport Crank fee from a fresh quote-only route probe. The launch probe tests the exact $0.12 planning input; a successful quote proves that input was available at that moment but does not claim it is Jupiter’s global minimum. If the probe has no qualified route, initialization remains unavailable. For an open position, a paid Crank is prepared only when the private authenticated Worker ledger and fixed-point proof derive its exact sell-cost reserve; the browser cannot supply that reserve.
CONTROL LOOP
The verified activated controller follows one owner-driven loop: review the exact operation, sign one exact transaction, prove finality and wallet deltas, append authenticated accounting, then expose only the next reviewed lifecycle action.
REPEATABLE CYCLES
Cycle receipts are canonical. Optional NFTs remain a later interface layer.
HONEST EVIDENCE BOUNDARY
Launch evidence is assembled by the Trinity Captain service and committed by the owner’s Crank. Missing, stale, future, incomplete, or inconsistent evidence produces no actionable card. The launch publisher is centralized; raw market history and a Jupiter route are not authenticated on-chain. The program authenticates the Captain submission, canonical wallet accounts, timing, sequence, and balances. A future evidence companion can strengthen source attestation without changing this launch promise. The seed remains upgradeable under the separately approved retained authority. Every owner operation rereads and binds the live code identity; pre-sign code hashing detects drift but cannot eliminate the centralized trust of a retained upgrade key.
LAUNCH GATES