A sniping desk that leaves no line to you
One-time keys made in your browser. Funding that arrives from another chain over NEAR Intents. Fills that carry no line back to your main wallet. Verdicts published as receipts that never name one.
reading the public log
The desk holds no key, receives no wallet and stores no address. Four promises, each with its proof and a way to check it yourself.
Generated by WebCrypto in your own browser and encrypted with a passphrase you type. Only the encrypted form is kept, and only on your machine. It is never sent, so the server has no copy and no way to make one.
Proof The veil page ships a Content Security Policy that allows no third-party script and connects only to the chain nodes and this site.
Read the security modelIt arrives over NEAR Intents from ZEC, BTC, SOL, NEAR or ETH on another chain. A solver takes the order and delivers native ETH on Robinhood Chain to the veil address, so the money that funds the fill did not come from a wallet of yours on this chain.
Proof The road is priced here on every load, in the relay's own numbers, with the route it ran named.
pricing 0.1 ZEC on the rail
The veil key signs it. Nothing on Robinhood Chain joins that address to the wallet you normally trade from, because the two have never touched each other on this chain.
Proof Open a veil fill in the explorer. The sender is a fresh address, and a fresh address is all that is there.
Open the chain explorerA receipt carries the token, the verdict, the raw probabilities and the WARDEN flags that produced it. It never carries a wallet. The API rate limits by a salted hash of the caller's address and keeps no IP.
Proof The log is public. Read a page of it and look for an address: the store holds the token, the symbol, the venue, the verdict, the four answers, the flags and the timings, and nothing else.
Read /api/receiptsA veil is funded across chains by NEAR Intents, so the network it settles through is NEAR. That network has a regulated wrapper listed on a German exchange, and the wrapper is the whole of the connection.
You name the asset you hold and the asset you want on the chain you want it on. Solvers compete for the order and the winner delivers it. Robinhood Chain is a listed destination, chain key hood, and native ETH on it is what a veil deposit arrives as. Quotes, deposit status and the asset list are open endpoints: no account and no key.
A dry quote, read live from NEAR Intents on this load. It has no deposit address, so nothing can be paid into it.
Generally available on NEAR since 2026-07-08. Execution runs on a private NEAR shard with no public RPC, mempool or explorer, operated by a permissioned validator set and bridged to mainnet through trusted execution environments. NEAR states that this hides an order's size, pair, direction and timing while solvers still compete on it. Quoting that route needs a NEAR Intents partner key. This desk does not hold one, so the route is not live here and the public one is what runs.
Figures read 2026-09-26 from bitwiseinvestments.eu.
A veil settles through NEAR, and this product is how a European brokerage account holds that same network: physically backed, staking the NEAR it holds and reinvesting the rewards daily. That shared network is the only reason Bitwise is named on this page.
Jevmaxxing is not affiliated with, endorsed by or in partnership with Bitwise, NEAR or TypeSafe.
Bitwise has a Zcash Strategy ETF filing pending, open on the read date of 2026-09-26. The first spot Zcash ETF, Grayscale's ZCSH, listed on NYSE Arca on 2026-08-25.
ZEC is a listed origin asset for a veil deposit today and a listed exit asset on the way out. It is the asset the dry quote above was priced in, on 0.1 ZEC.
Bitwise figures read from bitwiseinvestments.eu on 2026-09-26, with the listing note from rankiapro.com, and true as of that date. NEAR Intents and Confidential Intents facts read from docs.near-intents.org and near.org/blog on 2026-09-26. Robinhood Chain's stock token registry holds no Bitwise product and no tokenised share of one exists here. None of this is advice or an offer.
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.
Reads TokenLaunched from the Pons V2 factory and Initialize from the Uniswap V4 PoolManager. No indexer, no API key.
Checks which tracked wallets already bought this launch, and at which block they got in.
Counts buy and sell flow over the last blocks: unique buyers, ETH in, ETH out, seconds since the last buy.
Quotes the fill through the Pons curve or Uniswap V4, then builds a ticket your own wallet signs.
Bytecode, owner, mint and pause selectors, holder concentration, liquidity, deployer history, snipe tax. A kill here ends the trade.
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.
| Launch | Age | WARDEN | Jev | Liquidity |
|---|---|---|---|---|
reading the chain | ||||
This is the newest launch on Robinhood Chain right now, walked through the desk in the order the agents run.
SCOUT watches TokenLaunched on the Pons V2 factory and Initialize on the Uniswap V4 PoolManager, in one read with PoolCreated on the Uniswap V3 factory. The token, the curve or pool and the deployer all come out of the indexed fields.
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.
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.
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.
FLUX simulates the buy against the live curve, asks the V4 Quoter for a V4 pool or QuoterV2 for the best V3 tier, then returns tokens out, price impact and a minimum out. A V4 fill goes through the Universal Router, which enforces the floor itself. The ticket is unsigned. Your wallet signs it, or the veil key does.
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.
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.
| 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 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 token
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.
No token has been issued yet. When it is, the address appears here and on the official account, nowhere else.
Collected on every trade of the coin, on the launchpad itself.
The decision bill for every visitor, so the desk stays keyless and free.
Runs the same loop in public. Its fills appear in the receipts log.
No presale, no team allocation, no private round.