pre-sign wallet firewall · jev-latest

read the call
before you sign

jev doesn't pick coins. it refuses the drain. paste an unsigned transaction. jevguard decodes it, simulates asset changes, asks jev structured questions, then code emits allow, warn, or block.

$jevg is the dashboard access pass — hold the published amount on robinhood chain. the dashboard is public to look at; tools stay locked until a connected wallet holds that amount.

$jevg · contract unpublished

jevguard

$ jevguard scan unsigned-tx

the problem

a swap button can hide an unlimited approve

  • signing a transaction is authorization — not a receipt you can undo.
  • permit and permit2 look like swaps until you decode the spender and amount.
  • setApprovalForAll on an nft collection hands the operator every token.
  • jevguard reads the call, pretends to execute it, then tells you allow, wait, or stop.

JEVGUARD

ALLOW

swap 0.05 eth → usdc on uniswap

hold $jevg to scan

how it works

decode, simulate, ask jev, decide

every step is deterministic enough to audit. jev never sees raw hex. hard rules cannot be talked out of a block. you still hold the keys — a block never auto-sends.

01

decode

read the call before it leaves your wallet

02

simulate

preview asset changes without a private key

03

ask jev

structured facts only — never raw calldata

04

decide

code emits allow, warn, or block

what jev never sees

0x095ea7b30000000000000000000000004444444444444444ffffffffffffffff

stripped → facts.json
0xdead0xdead0xdead0xdead0xdead0xdead0xdead0xdead

raw hex stays in the decoder. jev only gets names, amounts, and yes/no facts.

jev questions

tiny answers. hard math stays in code.

  • unlimited_approval
    0.96
  • spender_is_unknown
    0.94
  • looks_like_drain
    0.91
  • permit_phishing
    0.12

the classic drain

approve( 0x4444…4444 , uint256.max )

blocked before you sign

phishing sites wrap this in a “swap” button. jevguard unwraps it.

forensic report

decode · sim · jev · policy

BLOCK

unlimited_unknown_spenderrisk 2.84judge jev
unlimited approval
unknown spender
intent match

what gets blocked

code owns the hard rules

unlimited unknown spender

approve or increaseAllowance to max-uint for an address that is not on the allowlist.

nft blanket operator

setApprovalForAll(true) to an unknown operator. that is a collection-wide drain.

permit traps

eip-2612 / permit2 with max amount and an unknown spender. chain id mismatch is a block.

multi-asset drain

simulation shows many tokens leaving plus native out to a target that is not a known router.

jev cannot override

if jev says allow and a hard rule says block, the report is block. math stays in code.

you still sign

allow can send through your wallet. warn asks you to hold. block disables send.

price bots

guess the next candle

a token call is not a trade idea. unlimited approval to a stranger is a key to the wallet.

jevguard

refuses approve(uint256.max)

unknown spender + unlimited allowance is a hard block. jev cannot override it.

supported networks

one scanner. seven chains.

ethereumbasearbitrumoptimismpolygonbnbrobinhood

robinhood chain (4663) is first-class. gas is eth. $jevg lives there.

robinhood chain · 4663

$jevg is the access token

hold $jevg on robinhood chain. the scanner checks the connected wallet, then reads the unsigned call before you sign.

token intel

summary, lore, and launch clusters

look up any project from a contract, website, or x profile. jevguard returns a public summary, published lore if it exists, and launch-wallet clusters — same-tx, same-block, shared senders — plus a simple graph. $jevg is only the hold-to-use pass for the dashboard. it is not the lookup sample.

open token intel

token intel

summary

usd coin (usdc)

erc-20 on ethereum. pool liquidity reported.

faq

plain answers

does jevguard hold my keys?

no. it never asks for a seed phrase. connect is wallet-only. a block cannot send a transaction.

what does jev actually see?

a facts sheet: classification, addresses, allowlist flags, amounts, simulation deltas, optional intent. not calldata. not your key.

what is $jevg for?

it is the access pass for the dashboard. you can look at the page; using the tools needs a connected wallet. when the token gate is on, that wallet must also hold the published amount. the publisher wallet is exempt.

can i look up any token?

yes — dashboard → token intel. paste a contract, a website, or an x profile. clustering needs a contract; a site or profile can still return published lore. scans also attach the same snapshot for tokens in the transaction.

do you show bundled wallets?

yes: same-transaction distributions, same-block clusters, shared senders, and a simple hub-and-spoke graph. it is not a bubble-maps clone. funding-source graphs need a paid indexer for high confidence.

can simulation be wrong?

yes. contracts can behave differently on-chain. treat allow as “nothing obvious looked like a drain,” not a guarantee.

look before you sign

connect a wallet, hold $jevg on robinhood chain, paste a transaction. if it is a drain, jevguard blocks it.

$jevg · contract unpublished

open dashboard