Documentation — BYTEJURY

Overview

BYTEJURY is a scam checker for Robinhood Chain, Ethereum, Base, Arbitrum One and Solana that treats the smart contract as the primary witness. It reads the code, simulates a real buy and sell on a fork of the chain, and checks what the project’s website and X account claim against what the contract actually allows.

Holder and liquidity analysis (snipers, bundles, insiders, LP) is the second layer. Narrative and hype are the last thing we look at, not the first.

Any report that already exists is free for everyone. A new scan is paid once, on-chain, in the utility token.

How scanning works

1. 1

   You submit an address

   The site checks whether a fresh report exists. If it does, it opens immediately. If not, you pay one scan: the token approval is for the exact price, never unlimited, or a single EIP-2612 permit signature if the token supports it.

2. 2

   The payment contract emits ScanRequested

   The contract takes the price, burns half and sends half to the treasury in the same transaction. The scanner’s indexer reads that event and queues the job.

3. 3

   Facts are collected

   Contract source or decompiled bytecode, proxy layout, owner and roles, static analysis, a fork trade simulation, holder and LP data, the website text and screenshots, the X account and its history.

4. 4

   The AI team builds the case

   The site analyst extracts claims, the auditor reads the code, OSINT searches X, the prosecutor argues mismatches. A second round has them critique each other, then the judge writes the verdict.

5. 5

   The report is published

   JSON is pinned to IPFS, saved to the database and its hash anchored on-chain with publishReport. The report page updates live while this happens.

What each check means

Ownership and roles

Who can still call restricted functions. “Renounced” only counts if no other role (operator, minter, admin, proxy admin) keeps power.

Mint, fees, blacklist, pause

Whether supply can grow, fees can be raised (and how far), wallets can be blocked or trading frozen.

Proxy and upgrades

Whether the code you read can be swapped. We show the implementation and who controls upgrades.

Hidden functions

Logic that changes behaviour for some wallets or under some flag: whitelisted sells, time bombs, unusual transfer hooks.

Fork simulation

A real buy and sell on a copy of the chain at the latest block. Measures buy, sell and transfer tax and detects honeypots directly.

Claims vs code

Each claim from the site or X (tax, supply, LP lock, renounce, audits, partnerships) is marked confirmed, contradicted or unverifiable, with evidence.

Snipers, bundles, insiders

Who bought in the first blocks, which wallets share a funder, how much of the supply they still hold.

Holders and liquidity

Top-10 concentration (excluding pools and burn), LP burned / locked / held by the deployer, lock expiry.

Deployer history

Other contracts from the same deployer and what happened to them.

Verdicts and safety score

Every report has an overall SAFETY score from 0 to 100 — higher is safer. It is the weighted average of four parts: contract (45%), token (30%), social (15%) and website (10%). Parts that could not be assessed are left out of the average. Deterministic facts cap it: a contract that cannot be sold is capped low, a proven honeypot scores near zero, whatever the models say. The verdict follows from the score.

Plain words

Honeypot

You can buy but cannot sell (or selling costs almost everything). We prove it by buying and selling on a private copy of the chain.

Renounced owner

The owner gave up control: the owner-only switches can no longer be used. It only counts if no other role (operator, minter, proxy admin) keeps power.

Proxy / upgradeable

The address you hold is a shell; its code lives elsewhere and can be swapped by whoever controls the upgrade. Safe today says nothing about tomorrow.

Mint authority

Someone can create new tokens at will, diluting every holder. Revoked mint authority means the supply is fixed.

LP burned / locked

Liquidity-pool tokens are the keys to the trading pool. Burned = gone forever; locked = held by a time lock until a date. If the deployer holds them, they can pull the liquidity.

Snipers

Wallets that buy in the first blocks after launch, often bots or the team itself. A large early share means the price can be dumped on later buyers — even if they already sold.

Bundle

Many wallets buying in the same block, funded by one address. Used to fake organic demand and hide how much the team holds.

Timelock

A delay between announcing an admin change and executing it, so holders can react. Without one, changes hit instantly.

Permanent delegate

A Solana Token-2022 setting that lets one address move or burn tokens from ANY wallet, forever. Rarely legitimate for a meme coin.

Tax

A fee taken on buys, sells or transfers. We measure it by trading on a fork, not by trusting the site.

AI team and marketplace inference

Five roles, each a separate model chosen for the job. Models per role are configurable by the admin.

All inference is bought on a secondary marketplace (Surplus Intelligence) with a minimum discount; responses not served by the marketplace are rejected. This keeps scans cheap enough to price low.

Every report lists the models that ran, who served them and what each call cost.

Every finding must carry evidence: a code location, a transaction, a post or a page. Findings without evidence are dropped before the verdict.

• Site analyst · Gemini 3.8 Flash
  Turns the site, docs and screenshots into a list of claims.

• Auditor · Claude Opus 5.5
  Reads source, static analysis and the fork run. Finds privileges and hidden switches.

• OSINT · Grok 4.7
  Searches X: what was promised, what was deleted, who the accounts really are.

• Prosecutor · GPT-5.6 Sol
  Argues every mismatch between claims and code.

• Judge · Claude Opus 5.5
  Weighs the case and writes the verdict and the safety scores.

Payment and burn

Scans are paid in the project’s utility token. The token address is read from the payment contract (utilityToken()) and can be changed by the admin; this site never hardcodes it.

The contract splits each payment on-chain: 50% is burned (via burn() or sent to the dead address) and the rest goes to the treasury. The split is configurable but public, and every payment emits a ScanRequested event with the exact amounts.

Once a scan is paid, the report is free for everyone. Re-scans are paid again.

Current terms (on-chain)

# you always pay on Robinhood Chain (4663); "chain" is where the SCANNED token lives
$ approve(ScanPayments, quote(you, "eip155:8453", "0x…"))      # exact amount, Base token
$ requestScan("eip155:8453", "0x…")
$ requestScan("solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp", "<mint>")   # Solana mint, case kept
> ScanRequested(scanId, payer, …, amountReceived, burned, toTreasury)

Contract addresses

Live values read from Robinhood Chain.

API

Coming soon

A public read API (report by chain and address, recent reports, webhooks on new verdicts) is coming soon. Reports are already public on IPFS by CID.

$ curl /api/v1/reports/base/0x…          # coming soon
$ curl /api/v1/reports/sol/<mint>        # coming soon
$ curl /api/v1/reports?limit=20         # coming soon

FAQ

Questions or a report to dispute? DM@bytejury on X.