The house-venue proof token, launched 2026-10-20 to prove — on mainnet, to the lamport — that a launcher token can graduate to the platform's own venue and keep its rules, including the Escrow Split's settlement behavior. A proof, not an investment.
Preflight report · last verified 2026-10-21 · all preflight reports
Per-token configurations are Locked — no one can change a launched token's rules. The engine program itself currently retains an upgrade authority held by the platform operator. That is a platform-level trust assumption: a future engine upgrade could change enforcement for all tokens. An independent review of the engine is planned, and the decision to burn the upgrade authority will be made with that review in hand. Until then, AgentOnly does not claim the engine is fully immutable.
| Mint | 5hXj8x3UCx4VqxpoyrNQTbfQxp4MAqjzTj3xqbJDSZEn |
| Pool (Meteora DBC) | 2fcnzG2Cb2HwXgFSuwvJGLbmA1AHMufGEsF5RpCSjYHZ |
| Token program | Token-2022 — standard Token-2022 for the token's whole life; no proprietary token program |
| Hook / engine program | EPdYVfsX7Lk9gtLp8CVouiFrNwtxP5g11NR6DDgs6akT |
| HouseSwap pool (venue) | EvD3GLFGqZ6jCMUDFgcyaapac5fGRGVED8ooqv4nqrvA |
| HouseSwap program | 8aeCfKabRfbXrLY68CXbsgp3x7mgikjwgMF3d7oY1Y8h |
| Engine config (this token) | 6T4Q1H3VnH9a8yGZLSyeYJ44zCEpS8YgJ8u6dyJpSDoa |
| Launched | 2026-10-20 (pool creation transaction below) |
| Creator fee | 100 bps (1%), to the deployer / fee-claimer wallet FMYVMuJgoM9J41PaXBmJe6ijSHUtSr2VPRbAJvH4MhCP. The house venue mirrors this rate; accrued house fees are visible in the proof record. |
| Holder fees | Off — no Distributor; this proof isolates the venue layer. |
| Config authority mode | Locked — the rule stack below cannot be changed by anyone |
| Rule | What it does here — parameters in plain numbers |
|---|---|
| Basis Latch (rule 1) — graduated mode | Sellable fraction starts at 5,000 bps (50%) at entry; vesting 432,000 seconds (5 days; engine default) and a 20,000 bps (2×) dip multiplier (engine default) govern the rest; the first crossing below basis latches the holder. Price feed maximum staleness: 300 seconds. (The proof's dip was microscopic — the venue's dip test is binary, and the record says so.) |
| Escrow Split (rule 2) | 5,000 bps (50%) of every buy's value is escrowed per buyer instead of traded. On a sell, the resolved escrow splits: a sell after a dip refunds 96% to the seller, 2% to pool depth, 2% to treasury; a sell above entry forfeits the resolved escrow to pool depth in full. Both branches were executed on mainnet — see Routes. |
| Max Wallet (rule 9) | No wallet may hold more than 500 bps = 5% of supply = 50,000,000 HPROOF. |
HPROOF committed at launch to graduate to the house venue at an engine-side threshold of 0.2 SOL of curve progress (the curve itself is built non-completing). Activation is permissionless once the threshold is crossed, and it landed on 2026-10-20 (signature below). After activation the house venue is the default door and the curve is the legacy door — and all three rules survive: the same engine keeps judging every transfer, and the Escrow Split keeps settling on house trades, as the tested rows show.
The rules are enforced by a mint-level Token-2022 transfer hook: the engine program runs inside every transfer of this token — curve trades, venue trades, and plain wallet-to-wallet sends alike, whoever builds the transaction. There is no off-chain component to bypass. Rules that carry per-holder state read it from holder records keyed to the receiving token account, in the templated form the standard Token-2022 extra-accounts resolver builds — which is why generic routers can construct a first buy for a wallet that has never held the token, with no custom integration.
Three separate questions, never collapsed into one badge: can the route be built (supported), has it actually run (tested), and does a named provider surface the token (indexed). Simulation results are labeled as simulation.
| Check | Status | Evidence & scope |
|---|---|---|
| Route supported — generic resolvers & DBC doors | Route supported | Standard Token-2022 mint; curve phase on Meteora DBC with templated extra accounts; after activation, the house venue is a standard program interface documented in the repository. |
| Route tested — house activation | Tested on mainnet | Permissionless activation bundle landed 2026-10-20 after the curve crossed the 0.2 SOL threshold: 4CEPuR7r4P…p2dNa5. Post-activation reads verified on-chain: venue live, fee rate mirrored at 100 bps, reserve seeded. |
| Route tested — house buy with escrow split | Tested on mainnet | First house buy (0.10 SOL total): 5tbFTW6PGv…bjJuVJ. Exactly 50,000,000 lamports (50%) were escrowed for the buyer; the traded half and the 1% house fee reconcile to the lamport in the proof record. |
| Route tested — dip sell: escrow refunded 96/2/2 | Tested on mainnet | The buyer sold half the position after a dip: 3fiTsVeEnV…w8fAae. Of 24,997,064 resolved escrow lamports, 23,997,181 (96%) refunded to the seller, 499,941 (2%) to depth, and the 2% treasury share folded into depth because no client passes the treasury wallet as a venue extra — documented venue behavior, observed exactly. |
| Route tested — above-entry sell: escrow forfeited | Tested on mainnet | A second buyer sold 40% of a position above entry: 2co1wyRfWL…xFHsUi. The full resolved escrow (11,994,704 lamports) forfeited to pool depth; refund exactly 0. |
| Provider indexed — Jupiter | Indexed as generic DBC | Jupiter's token index carries this mint in the generic Meteora DBC class (launchpad: "met-dbc") — no AgentOnly partner label. Indexing as a generic DBC token is not the same as a tested swap route. |
| Provider indexed — BasedBot | Not indexed | BasedBot's app answers “No route to SOL” for this mint (observed 2026-10-20, as for the launcher's mints generally). Our assessment is that the refusal happens in the app's backend before any transaction is built — the same mint structure routes through generic resolvers, as the tested rows above show. BasedBot has not confirmed the reason; we state the observation and label the explanation as our assessment. |
| Venue behavior in simulation | Tested in simulation | House trials: trial-house 37/37 · trial-houseswap 87/87 · engine trial suite 64/64 · DBC×Engine integration suite 40/40 (real Meteora DBC binaries, local validator). Simulation is not mainnet execution — the mainnet rows above are the proof for this token. |
The Basis Latch reads a cranked price feed (an EMA of the pool price). The feed goes stale after 300 seconds and the hook vetoes transfers while it is stale — that is deliberate: a latch decision is never made on old prices. A dedicated crank service (Railway, polling every 30 seconds, crank wallet Hmuum57dKYa2XEm198fa5jCeKMJobxWHR3iq4mwV5rmN) keeps every launcher feed inside the gate; observed feed ages in steady state sawtooth between 0 and ~270 seconds. This token's feed is in the crank set.
The proof run surfaced four defects in the launcher and trading clients (a missing account in the house launch step, read-only flags on house swaps, an under-budgeted house sell, a read-only vault flag in the activation builder). The on-chain programs behaved per spec in every case; the first house launch attempt failed at the config step for the client reason and was resumed in place — the failed transaction is preserved in the launch record, not hidden. The client fixes shipped the same week with the trial suites green (trial-house 37/37, trial-houseswap 87/87).
Last verified: 2026-10-21. Statuses on this page describe what was true at that date; simulation results are labeled as simulation wherever they appear and are never presented as mainnet execution.