Follow the model, change the economics, inspect testnet receipts, and see where each ecosystem dependency enters the plan.
NetworkRobinhood testnet · 46630Road Show-owned test-only model
Deterministic deployment model
One proposal becomes one ordered plan.
Every step has an input, a code owner, a prerequisite, and a recovery boundary. The browser view below explains real package seams without pretending that it executed a launch.
01
Show
Join the whitepaper, source revision, and public claims.
evidence-worker · evidence graph
02
Check
Match each claim to code, tests, contracts, or an open gap.
SDK · evidence validation
03
Compose
Select authenticated releases and bind every asset role.
SDK · plan compiler
04
Freeze
Commit the exact action order, inputs, and recovery rules.
canonical JSON · plan hash
05
Assure
Rehearse the frozen path and stop on any mismatch.
fork and test-only runners
06
Launch
Present one reviewable transaction at a time.
wallet queue · explicit authority
07
Prove & settle
Index receipts, reconcile state, and preserve recovery.
indexer · read model
Deterministic simulation
Explanation receiptIncomplete0x2cbe0f03a2561c8d2d8a21e8ed43e6a3064f6a0864f6ce4e222767d3d7059f32Reproducibility digest — the same reviewed input always reproduces this hash.
AuthorityNon-authoritativeNo transaction was signed or broadcast.
ExecutionNot runExecutable bindings remain gated.
Interactive calculations
Know the capital plan before publishing.
Change the collection geometry and working assumptions. This is an educational estimate, not a live quote.
Battle-test your idea against the Special Projects.
A proposed compatibility model derived from your declared parameters. It is not a review, approval, or endorsement by any Special Project.
Project brief
Describe the project in your own words — this is the primary way to express the idea. The declared parameters below stay as a secondary, structured summary.
Whitepaper
Your brief and whitepaper are captured as the project's description context and shown here for the record. The compatibility model below still scores only the declared parameters you set by hand. Automatically reading those parameters from your summary or whitepaper (Handler grounding) is the next phase — this page never fabricates numbers from your text.
Declared parameters
The structured summary of your idea. The fields in this first group feed the deterministic model exactly as before.
Quote asset
Launch allocation — turn each bucket up or down
The reward bucket is fixed at 0 by the model.
AMM bucket
95%9,500 bps
Loan bucket
5%500 bps
AMM 95%
Loan 5%
Reward 0%
NFT collection size5,000NFTs
Above zero reads as NFT-backed.
Tokens per NFT1,000tokens / NFT
Additional declared context
Captured with your brief — grounding these into the score is the next phase.
Chain
Pair asset
Lock stance
Special Projects
up.$UP
★★★★★5.0
Technical
★★★★★
Ecosystem journey
★★★★★
How this was scored
✓Tradable on the ve(3,3) DEX. Any Anvil-launched token can be swapped and LP'd on up., the ecosystem's core venue.
✓Deep AMM liquidity allocation. ammBps 9500 routes the majority of supply into the swappable AMM bucket.
✓Core-pair quote asset. A STONKBROKER quote pairs directly against up.'s deepest routes.
✓Emissions-eligible liquidity lock. Permanently locked liquidity is eligible to be gauged for $UP emissions.
✓Reachable by every up. swapper. up. is where ecosystem users already swap, so a listed token is reachable by all of them.
✓Low-slippage swap UX. Deep AMM liquidity gives up. users low-slippage swaps into this token.
✓Stake-for-emissions loop. Locked liquidity lets up. users stake into the $UP emissions loop.
TickerYard$YARD
★★★★★5.0
Technical
★★★★★
Ecosystem journey
★★★★★
How this was scored
✓Routable market. Any live market can be routed and surfaced through TickerYard.
✓AMM depth aids routing. A deep AMM pool gives TickerYard's router better fills to surface.
✓Core quote simplifies routing. A STONKBROKER quote is directly routable without an extra hop.
✓Discoverable category. A collection/game gets a dedicated discovery surface.
✓Discovery funnel. TickerYard users discovering markets can route straight into this one.
✓Category surface. A collection/game earns a browsable category on TickerYard.
✓Liquid enough to route. Deep liquidity makes routed clicks convert into fills.
Oakmont Vault$STRIKE
★★★★★1.0
Technical
★★★★★
Ecosystem journey
★★★★★
How this was scored
·Leverage or vault design. No leverage/vault design is declared, so the collateral model isn't matched.
·USDG-quoted market. Quote is STONKBROKER, not USDG, so Oakmont's pairing isn't matched.
·Launch-loan allocation. loanBps 500 is below the collateral-usage threshold.
A modeled projection — spokes are your proposed fit to each Special Project, arcs are components two projects already share. Not observed on-chain links.
Drag to pan · scroll to zoom · click a link
Connection detail
Click any connection to inspect it — the modeled compatibility from your project, or the components two Special Projects already share.
Edge record — one line
Chain 46630 · recorded state
The model ran. Here are the receipts.
Road Show-owned and non-official. The testnet deployment demonstrates our compatibility model, not Anvil approval.
Contracts21
Transactions53
Completed paths02
StateVerified
Chain 46630 deployment record — from the frozen registryVerifiedIntegration passed
Atlas records describe evidence and composition. They are not endorsements, executable allowlists, or official Anvil integration claims. Unauthenticated ecosystem claims remain NOT_ESTABLISHED.
Handler Labs · Road Show
Built in public, after the publication boundary is approved.
The source repository has not been republished under Handler Labs yet. Its final URL will appear here after the package and licensing scope is approved.
Planned repositoryHandler Labs / Road Show
Publishing review
01protocol-types
Canonical records, parsers, and safety vocabulary
02provider-interface
Subject-bound data providers and fail-closed read envelopes
03evidence-worker
Whitepaper and repository claim-to-evidence analysis
04sdk
Evidence graph, plan compiler, preflight, and monitoring
05indexer
Reorg-safe receipt ingestion and public read models
06api
Read-only, subject-bound service endpoints
07contracts
Production assurance contracts and a separate test-only compatibility model
08testnet-config
Pinned environments, code identities, and deployment evidence
09docs
Generated reference, runbooks, boundaries, and threat model