The launch shows up in a log, not a feed.
SCOUT watches two topics: TokenLaunched on the Pons V2 factory and PoolCreated on the Uniswap V3 factory. The token, the curve or pool and the deployer all come out of the indexed fields.
reading the chain
A sniping desk for Robinhood Chain
Jev decides.
The veil signs.
Five agents read every launch off the chain. Jev answers in one call. The fill can be signed by a one-time key made in your browser and funded from another chain.
reading the public log
The veil.
A one time snipe wallet whose key never leaves your browser, funded from another chain and emptied the same way. Nothing on Robinhood Chain ties the fill to your main wallet.
01
Made in your browser
The key is generated by WebCrypto on your own machine and encrypted with a passphrase you type. Only the encrypted form is kept, and only here. The server never receives it and the desk never holds it.
02
Funded from another chain
Send ZEC, BTC, SOL, NEAR or ETH from wherever you already hold it. A solver on NEAR Intents takes the order and delivers native ETH to the veil address on Robinhood Chain.
pricing 0.1 ZEC on the rail
03
Signed by a key with no past
The veil key signs the fill. The fill is a public transaction sent from an address with no history, and the link from that address to your main wallet is not on the chain.
What stays public
- The fill. It is an ordinary transaction on Robinhood Chain, sent from the veil address, and anyone can read it in the explorer.
- The origin deposit, exactly as its own chain shows it. A Zcash send shows what Zcash shows, a Solana transfer shows what Solana shows.
- Timing. Both ends of the route carry a timestamp, so the two can be lined up by anyone watching both chains.
NEAR's Confidential Intents would also hide an order's size, pair, direction and timing while it settles. Quoting that route needs a partner key this desk does not hold, so the live route is the public one and the page says which one it ran.
Five agents read the chain.
Jev reads the five agents.
Each agent answers one question off the chain itself. Their answers become a state object small enough for a System One model to read literally, and Jev returns four typed answers.
01
SCOUT
Reads TokenLaunched from the Pons V2 factory and PoolCreated from the Uniswap V3 factory. No indexer, no API key.
02
LEDGER
Checks which tracked wallets already bought this launch, and at which block they got in.
03
PULSE
Counts buy and sell flow over the last blocks: unique buyers, ETH in, ETH out, seconds since the last buy.
04
FLUX
Quotes the fill through the Pons curve or Uniswap V3, then builds a ticket your own wallet signs.
05
WARDEN
Bytecode, owner, mint and pause selectors, holder concentration, liquidity, deployer history, snipe tax. A kill here ends the trade.
Jev, TypeSafe System One
One call carries the compact state and four typed questions: what to do, how likely a rug is, whether buy flow is accelerating, whether the crowd is already in. A WARDEN kill overrides every one of them.
action
rug
momentum
crowd
measuring latency
Launches, last hour-Pons V2 and Uniswap V3
WARDEN kills today-Verdicts overridden by the scan
Jev latency-Last typed answer, round trip
Decisions today-Each one published as a receipt
The feed, newest first
| Launch | Age | WARDEN | Jev | Liquidity |
|---|---|---|---|---|
reading the chain | ||||
One launch,
step by step.
This is the newest launch on Robinhood Chain right now, walked through the desk in the order the agents run.
- 01 SCOUT
- 02 WARDEN
- 03 PULSE
- 04 LEDGER
- 05 FLUX
- 06 Jev
The safety scan runs before anything else.
WARDEN pulls the bytecode and looks for mint, pause and blacklist selectors, reads the owner, rebuilds holder concentration from Transfer logs, measures the pool or curve liquidity and reads the current snipe tax.
reading the chain
Flow, counted in blocks.
PULSE counts CurveBuy and CurveSell over the recent window: how many distinct addresses bought, how much ETH went in, how long since the last buy landed.
reading the chain
Who is already in.
LEDGER holds the early buyer list built from the last forty thousand blocks, plus any wallet you add to your own watchlist. It reports which of them are in this launch and at which block.
reading the chain
The fill, quoted before the verdict.
FLUX simulates the buy against the live curve or asks QuoterV2 for the best Uniswap tier, then returns tokens out, price impact and a minimum out. The ticket is unsigned. Your wallet signs it, or the veil key does.
reading the chain
Four questions, one second.
The compact state goes to Jev in a single call. Action, rug risk, momentum, crowd. Code applies the policy on top: a WARDEN kill ends it, a buy needs confidence, a copy needs a tracked wallet already in.
reading the chain
The model answers in types.
Jev is TypeSafe's System One model. You hand it a state object and a set of typed questions. It hands back a choice, a score or a probability, with the full distribution over the options. There is no prose to parse and nothing to regex.
It reads literally and it is not a calculator, so every number in the state is computed in code and sent as a value and a named bucket. Token names from the chain are truncated and marked untrusted. The state stays under sixty fields.
Confidence policy
| Verdict | Condition |
|---|---|
| killed | WARDEN returned a kill flag. Jev's answer is recorded and ignored. |
| buy | Jev chose buy, confidence is at least 0.55 and rug score is below 1.0. |
| copy | Jev chose copy and at least one tracked wallet is already in. |
| skip | Any buy or copy that misses its condition, downgraded with the reason stated. |
| pass | Jev chose pass. The launch is not worth watching. |
The four questions, exactly as the API sends them
{
"action": {
"type": "choice",
"instructions": "What should a sniper do with this launch right now?",
"criteria": {
"buy": "Enter now",
"copy": "Enter only because tracked wallets are in",
"skip": "Not now, keep watching",
"pass": "Never, walk away"
}
},
"rug": {
"type": "score",
"instructions": "How likely is this token to be a rug or a honeypot?",
"criteria": ["Clean", "Some flags", "Likely rug"]
},
"momentum": {
"type": "boolean",
"instructions": "Buy flow over the last blocks is accelerating."
},
"crowd": {
"type": "boolean",
"instructions": "At least one tracked wallet already bought this token."
}
}
No confidence field comes back. Confidence is the highest probability in the returned distribution, computed in code.
loading the public log
The desk's own book.
The desk runs the same loop on every launch and marks each call against the real curve price. No fill has been made. Fills begin when the desk wallet is funded.
reading the desk
The rail is NEAR.
The veil is funded across chains by NEAR Intents, and the network that clearing runs on has a listed wrapper of its own.
NEAR Intents
You state what you hold and what you want. Solvers compete for the order and one of them delivers native ETH to the veil address on Robinhood Chain. Quotes, deposit status and the asset list are open endpoints: no account and no key.
- Route
- 1Click v0, quote then deposit then status
- Destination
- native ETH on Robinhood Chain
- Read on
- 2026-09-26
Bitwise NEAR Staking ETP
A physically backed exchange traded product listed on Deutsche Boerse Xetra. It stakes the NEAR it holds and reinvests the rewards daily, which is how a European brokerage account holds the network the veil settles through.
- Ticker
- NEAR, Xetra
- ISIN
- DE000A4A5GV2
- WKN
- A4A5GV
- Inception
- 2025-07-01
- TER
- 0.85 percent
- Staking
- 3.01 percent net, NAV $26.21
Product figures read from bitwiseinvestments.eu on 2026-09-26 and true as of that date. Jevmaxxing is not affiliated with Bitwise, NEAR or TypeSafe, holds no tokenised share of any of them, and none of this is advice or an offer.
The token
$JEVMAXX pays the bill for the desk.
The tool is free and keyless. Somebody still pays for the Jev calls and the RPC. Pons creator fees do, and the same fees fund the desk wallet that runs this exact loop in public, with its receipts in the same log as yours.
CA: issuance pending
No token has been issued yet. When it is, the address appears here and on the official account, nowhere else.
In
Pons creator fees
Collected on every trade of the coin, on the launchpad itself.
Out
Jev calls and RPC
The decision bill for every visitor, so the desk stays keyless and free.
Out
The desk wallet
Runs the same loop in public. Its fills appear in the receipts log.
Supply
Fair launch on Pons
No presale, no team allocation, no private round.