Method

A scan reads one address from Robinhood Chain through the public RPC, in this order:

1. The head block, the ETH balance, the sent-transaction count (nonce) and any code at the address. A wallet with an EIP-7702 delegate is still shown as a wallet.
2. Balances of 39 tracked tokens: WETH, USDG, USDe and the official stock tokens.
3. The whole history, one token contract per query: transfers in, transfers out and approvals of WETH, USDG and up to two stock tokens the address holds now; and withdrawals to Ethereum through the ArbSys system contract.
4. A recent window of 240,000 blocks (about seven hours) for any contract at all: token transfers both ways, approvals, WETH wraps and ERC-1155 transfers.
5. Token names and decimals, which counterparties have code, and up to 160 block timestamps.

Findings are then computed by plain rules from those rows, with no scoring and no guess at owners. The same rows always give the same findings.

The map draws up to 24 counterparties from the same scan around the address. A shorter line and a larger dot mean more transfers. Named contracts (only from the sourced list below) sit on the right half, plain addresses on the left. Once the consent book is deployed, an address that set "no named node on maps" is drawn without its address.

The watch list lives in your browser's local storage, up to 25 addresses. On each visit, and every minute while the page is visible, Vynra asks the server what changed in the last 90,000 blocks (about two and a half hours) or since the last check, whichever is shorter. The first check learns the baseline. Later checks flag a new counterparty, a new token, a new approval, more sent transactions or a changed ETH balance. A gap longer than the window is not read: open Scan for the full report.

Preview decodes call data in your browser against 6 known contract families: ERC-20 token, NFT (ERC-721 / ERC-1155), Wrapped Ether, Uniswap v2 router, Withdrawal to Ethereum (ArbSys), VynraConsentBook. A selector outside that list is reported as "cannot decode". "Run once" sends the call to the server, which runs it with eth_call at the latest block with a gas cap of 3,000,000 and reports whether it would revert. Nothing is signed or broadcast.

VynraConsentBook is written and tested but not deployed yet. It has two parts. Statements: a wallet (or the one manager it appointed, after the manager accepts) publishes a label of up to 64 bytes, an optional link and hash, and four signals: no third-party labels, no named node on maps, please do not watch, and watching is fine (the last two cannot both be set). Every version is kept as a hash and an event. Report anchors: anyone anchors a report hash with its block range and method version; the author revises or withdraws; the wallet acknowledges or disputes, and a revision resets the response. The contract has no owner, no fee, no upgrade path and no payable function, and it holds nothing.

Every token transfer has a sender and a receiver. Vynra groups transfers by the other address and counts them in and out. The zero address is shown as mint or burn. A counterparty is an address, not a person; two addresses may belong to one person, and one exchange address may serve thousands.

The earliest inbound transfers Vynra read are listed as the first funding. ETH sent directly (not as a token) leaves no log on the chain, so it is invisible to a log reader. Deposits from Ethereum through the bridge leave no log here either. With an explorer key configured, the explorer's transaction list adds direct ETH transfers.

Vynra reads the timestamps of up to 160 blocks with this address's transfers and counts them by UTC hour. With at least eight, it names the busiest hour and the quietest six-hour stretch. A steady quiet stretch can hint at a time zone. Bots and schedulers break this pattern, and Vynra says so.

Approval and ApprovalForAll events show which spender a wallet trusted and for how much. Vynra keeps the latest event per token and spender. Spending through transferFrom lowers an allowance without an event, so the value shown is the last one set by an event, not always the current allowance.

Vynra names a contract only when it is in this list. Each line was checked on chain on 10 Nov 2026 (code present, and symbol for tokens). There are no exchange wallets in it: we found no sourced list of exchange addresses on Robinhood Chain.

Plus 39 tracked tokens, named by the symbol each returns on chain.

A downloaded report is JSON with the fields method, methodVersion, address, chainId, balances, tokens, transfers (newest 400), approvals, wraps, withdrawals, counterparties, timing, findings, statement and coverage. Coverage lists the head block, the tokens read over the whole history, the recent window, the explorer state, the number of chain reads, and every gap with its block range and reason.

The report hash is keccak256 over the canonical JSON of the report: object keys sorted at every level, no spaces. You can recompute it from the file and compare it with an anchor in the consent book.

• Vynra reads and explains public data. It does not make transactions private. Hiding transaction details needs other technology and its own testing.
• It does not know who owns a wallet and never says so.
• The public RPC accepts 10,000,000 blocks per query with one contract address and 30,000 without. Untracked tokens are read only in the recent window. A window that cannot be read is listed as a numbered gap, never skipped silently.
• Direct ETH transfers and bridge deposits are not visible without an explorer key.
• A scan is shared for ten minutes. Watch reads at most the last 90,000 blocks per check.
• Preview decodes only known contract families, and a successful run once is not a promise about later blocks.