QUIVER turns four-chain launch activity into clear narrative signals, then carries a reviewed brief into a wallet-ready Pons launch on Robinhood Chain.
DETECT THE META · LOAD THE IDEA · LAUNCH ON PONS · SPLIT FEES ON-CHAIN · DETECT THE META · LOAD THE IDEA · LAUNCH ON PONS · SPLIT FEES ON-CHAIN ·
01 The premise
Most people spot a trend when it’s already crowded.
QUIVER makes the early signal clear enough to act on — before the timeline agrees.
The radar watches launch activity across Robinhood Chain, Solana, BNB Chain and Base for accelerating narratives and fresh clusters of attention. It does not promise a winner. It makes the signal legible and turns it into a practical launch direction. QUIVER frames the opening; Pons handles the release.
02 The method
Three moves. One clean shot.
01Detect
Read the current.
QUIVER measures momentum, recurring language and narrative overlap while a meta is still taking shape.
02Load
Shape the idea.
The signal becomes a focused brief: name, ticker, positioning and art direction.
03Loose
Launch through Pons.
Creators review the concept, connect a wallet and launch through the live QUIVER contract on the Pons rail.
03 Launch
Turn a signal into a launch brief.
The launch workspace now connects to an EVM wallet, reads the current Pons fee and economics pin, then presents one final review before the on-chain launch.
Wallet not connectedConnect an EVM wallet to Robinhood Chain · Chain ID 4663
Live launcher:0xf9533a6ad25f8ee7ebd101e44eddf71171c71f95 on Robinhood Chain. Review reads the current Pons launch fee and economics pin before the wallet can sign.
04 Live
Live — launched via QUIVER
Every coin shown here was launched through the QUIVER launcher on Pons.
Waiting for the launch feed…
The feed loads when this section comes into view.
05 Radar
Four chains. One field of signal.
A continuously refreshed read across Robinhood/Pons, Solana/pump.fun, BNB/four.meme and Base/Clanker — with detected narrative metas ready to carry into the Launch workspace.
SCANNING FOUR CHAINS…
Waiting for radar feed…
Detection window · 1h vs 24hSTREAMING
Four rails. One clean read.
QUIVER normalizes launch events from Pons V2, pump.fun, four.meme and Clanker, then scores themes by one-hour momentum against a 24-hour baseline with a saturation penalty.
—Events captured
—Watchers live
—Service uptime
Loading same-origin radar.json…
Global theme leaderboard
Per-chain top themes
Signal selected. Brief next.
Choose any detected meta above to preload its narrative into the Launch workspace, then refine the token name, ticker, artwork and creator identity before wallet review.
Live feed:radar.json is refreshed by the four-chain watcher pipeline and polled here every 10 seconds while Radar is visible.
06 Explore
Interrogate the signal before you ship it.
From detection to direction
Keep the thesis attached to the evidence.
Explore is the reading layer between raw activity and a launch decision. Compare the narrative, its chain leader and its momentum window before turning it into a brief.
Read all four rails together instead of treating a single chain spike as the whole market.
02
Check the window
Use the one-hour momentum score against its 24-hour baseline and account for saturation before choosing a direction.
03
Carry the context
The “Use this signal” handoff preloads the selected narrative into Launch without skipping the creator’s review.
07 The split
Three percent. Shared three ways.
The deployed model divides normal-trading fees into three equal shares after Pons’s initial 15-second snipe-tax window. Each launch gets its own splitter, keeping balances separate.
1%
Creator
The person who launched the coin.
1%
QUIVER
The protocol share during normal trading.
1%
Pons
The underlying launch and market rail.
08 The standard
Clear rules. Clean accounting.
The model calls for one splitter per coin, separate balances and visible allocation. The exceptions stay in print.
Launch chainRobinhood Chain · 4663
Launch railPons V2
Normal trading fee3% total
Opening window15-second Pons snipe tax
Launcher0xf9533a6a…71c71f95
Fee accountingIsolated per coin
09 Docs
The protocol, without the fog.
The exact launch path, fee arithmetic, radar API and safety properties behind the deployed V1 launcher.
01 · Architecture
One atomic launch.
QUIVER facilitates the release; Pons remains the underlying launch and market rail. A failed step reverts the whole transaction.
01
Review
The creator confirms token metadata, route and immutable social identity.
02
Pin
The interface reads Pons's current launch fee and economics hash immediately before signing.
03
Deploy
QuiverLauncher creates a dedicated splitter for this token inside the same transaction.
04
Launch
Pons creates the token and curve, then the splitter binds to the returned token.
Per-launch deployment: every token receives a fresh QuiverSplitter with immutable treasury and Pons recipients. Its social identity is written once; only the payout address can later be re-pointed by the original launcher.
03 · Radar API
The interface contract.
The zero-dependency Node service watches Pons V2, pump.fun, four.meme and Clanker. Each chain runs in an isolated loop with its own cursor and backoff.
GET /metasGlobal and per-chain themes scored over a 1-hour momentum window against a 24-hour baseline.
GET /suggestions?theme=aiLaunch ideas grounded in the selected theme and recent detected names.
GET /healthPer-chain watcher state, cursor, lag, launch count and last error.
Published feed: the watcher pipeline exports radar.json at the site root about every 15 seconds. Radar requests it every 10 seconds while visible and reports the export age directly.
04 · Safety
Failure closes the path.
Economics pin
A changed Pons fee schedule reverts instead of silently launching under different terms.
Pair validation
Non-native pair tokens must be approved by Pons before the launch continues.
Solvent accounting
Only fresh, uncredited balances are released. Repeated release and harvest calls remain no-ops.
Reentrancy guards
Harvest, release, claims, curve sweeps and pool sweeps are guarded.
Pull claims
Creator, QUIVER and Pons withdraw only their own recorded credits.
Battle tested
46 contract tests pass, including repeated release, partial claims, multi-asset accounting and solvency fuzzing.
V1 launcher deployedWallet flow, contract addresses, radar endpoints and safety properties are all in this single build.
