Reading Robinhood Chain mainnet live. Every finding comes with its evidence.Open the workspace

Seehow
thechainconnects.

Read contracts. Trace transactions. Connect the evidence behind every on-chain move.

see a live example

EVM address (0x + 40 hex) or transaction hash (0x + 64 hex).

Robinhood Chain · chain 4663 · public reads, no wallet needed · independent tool, not affiliated with Robinhood

Reads fromreading head…
  • RPCrpc.mainnet.chain.robinhood.com
  • RPCrobinhood-rpc.publicnode.com
  • TRACErobinhood.drpc.org
  • SOURCEsourcify.dev
  • EXPLORERrobinhoodchain.blockscout.com
  • REGISTRYdevelopers.uniswap.org
  • DOCSdocs.robinhood.com/chain
Evidence-backed

no safety scores, ever

“A finding without its evidence is a guess. GeoAI shows the block, the method and the provider behind every claim, and says plainly what it could not read.”

observed ≠ interpreted ≠ unknownnot detected ≠ does not exista zero owner ≠ control removed
Three passes

Read the contract, trace the transaction, connect the evidence

  1. 01Read the contract.
  2. 02Trace the transaction.
  3. 03Connect the evidence.

Three deterministic passes build one evidence bundle. Every section of the workspace, and every Ask Geo answer, points back into it.

GeoScan

How GeoAI reads an address

A deterministic pipeline turns an address into evidence records and findings. The panels below are a live read of the USDG proxy contract on Robinhood Chain, refreshed every minute; nothing is scored, nothing is guessed, and anything that did not answer is reported as unknown.

How it works
01

Pins a block

The latest header becomes the observation point. Balances, code and storage slots are read at that block, so the findings describe one moment.

observation block
read from /api/showcase when reachable
  • eth_getBlockByNumber(latest)
  • hash + timestamp recorded as E1
  • every state read below uses this block tag
02

Reads code, slots and calls

Bytecode, EIP-1967 slots, token metadata, owner and pause state: one batched read, every answer kept as an evidence record with its block.

one batched read · 0x5fc5…d168
reading USDG…
a revert or empty answer is evidence too
03

Verifies source and patterns

Sourcify (and Blockscout in the workspace) provide verified ABI and source. Capability patterns are matched on the implementation of a proxy.

verified sourcesourcify
asking Sourcify…
Three live findings

Upgradeable proxy

block unknownrpc · sourcify
⌁eth_getStorageAt · EIP-1967 implementation slot
reading…
geoai · finding
Waiting for the live read…
Open on the workspace →

Unlimited allowance

block unknownrpc · eth_getLogs
⌁Approval(owner, spender, 2^256−1) · receipt log
reading…
geoai · finding
Waiting for the live read…
Open on the workspace →

Admin controls present

block unknownrpc · sourcify
⌁eth_call · owner() · paused() + implementation ABI
reading…
geoai · finding
Waiting for the live read…
Open on the workspace →
Live reads from Robinhood Chain and Sourcify · cached 60 s on the server · values can change in any later block
GeoTrace

What happened in this transaction?

Transaction, receipt and block; calldata and logs decoded with verified ABIs or known standards; ERC-20 / 721 / 1155 movements and approvals; internal ETH from a call trace when an endpoint answers. Pending and reverted transactions are reported as exactly that.

Explore a transaction
GeoTrace · newest transaction with logslive · loading
finding the newest transaction with logs…
Ask Geo

Questions answered with references.

Ask Geo sees only the investigation’s evidence bundle. Every factual claim cites evidence ids, the server validates each citation, facts are kept apart from interpretation and unknowns, and the observation block is always stated.

Ask about an address
Ask Geo · deterministic summary of a live readlive · loading
“What can this contract do, and who controls it?”
answer · built by code from the findings · every line cites evidence ids of this read
reading USDG…
Facts
what the evidence shows
Interpretation
what it likely means
Unknowns
guards, history and traces are not part of this quick read
observation: block unknown · a configured model answers from the same bundle with validated citationsask on the workspace →
Connections

Every connection tells a story.

GeoAI draws bounded graphs from retrieved data: who called whom, what moved, in which transaction and block. This one is the newest transaction with logs on Robinhood Chain, read live. A transfer demonstrates an interaction, not necessarily common ownership, and GeoAI never labels an address a whale, insider or exchange without evidence.

Reading the newest transaction with logs…
  • ● sender
  • ○ counterparty
  • □ contract
  • ■ token
  • — call + first transfer

Live · loading

reading the newest transaction with logs…
Evidence

An answer is only as useful as its evidence.

Every finding in GeoAI is built from typed evidence records. A record says which provider answered, which method was called, which block it describes, when it was observed, and what it cannot tell you. Ask Geo cites these ids; the server rejects any citation that does not exist.

  1. 01
    Finding

    What was observed, why it matters, and the confidence: observed, interpretation, or unknown.

  2. 02
    Source

    The provider that answered (rpc:official, sourcify, blockscout, trace) and the exact method or endpoint category.

  3. 03
    Block number

    The block the observation describes. State reads of one investigation are pinned to one block.

  4. 04
    Observation time

    When GeoAI made the read. Implementations, owners, balances and allowances can change afterwards.

  5. 05
    Coverage limitations

    What the record cannot tell you: pagination limits, missing ABI, event-derived amounts, trace unavailability.

Evidence record · livereading…
reading the chain…

Live record from /api/showcase, cached 60 s. No sample values on this page.

The evidence layer

Every claim, connected to its record.

Findings, the connection graph, Ask Geo answers and exports all point back into one bundle of typed evidence records. Open a citation, copy a value, visit the explorer, or take the whole investigation with you as JSON.

Ways to use the evidence
01 · Evidence card · live
reading the chain…

Provider, method, block, time, result, limitations, explorer link.

02 · Citations · live
reading the chain…

Ids from this live read. In the workspace each chip opens the record; ids that do not exist are removed from answers and reported.

03 · Export & copy
geoai-address-0x5fc5360D-<time>.jsonJSON
this live read · reading…summary

Export JSON and Copy summary on every investigation. Exports carry every record and no credentials; key-shaped strings are redacted.

04 · Watchlist · this device
No saved investigations on this device yet. Open an analysis and press Watch.

Device-local labels and manual refresh. No background monitoring, no alerts.

READTRACECONNECTREADTRACECONNECTREADTRACECONNECTREADTRACECONNECT
READ · TRACE · CONNECT

Built to be honest about limits.

Designed for investigators, analysts and curious holders who need to know not only what was found, but how, and what could not be found.

01

Observed, interpreted, unknown

Every finding carries one of three confidence levels, and a limitation line when the read could not settle the question.

02

One observation block

State reads of a run are pinned to one block and the time is recorded. Implementations, owners and allowances can change afterwards, and the page says so.

03

Nothing invented

No safety scores, no sample data in place of a failed request, no holder counts or prices the providers did not return, no model claim without a citation.

Token

$GEOAI

The GeoAI token lives on Robinhood Chain (chain 4663). Its contract address is published on this page first. Until it appears here, no address claiming to be $GEOAI is ours.

Once published, this block reads the contract live with the same records as every GeoScan: name, symbol, decimals, total supply, verified source. It never states a price, a market value or a promise.

  1. 01

    The address is verified on chain: bytecode present, ERC-20 reads answer, symbol() is GEOAI.

  2. 02

    It is written into the site record and deployed; this block and /api/token switch to live reads.

  3. 03

    Every value shown afterwards is a read at a stated block with its evidence record, never a price.

Contract addressnot published
CA: Soon
GeoAI · $GEOAI · Robinhood Chain · chain 4663
name()
—
read from the contract
symbol()
—
must answer GEOAI
decimals()
—
read from the contract
totalSupply()
—
display units per decimals()
verified source
—
Sourcify match
holders
—
explorer-indexed count

No address to copy yet. When it is published, the copy button, the GeoScan link and the explorer link appear here.

Record from config/token.json. No placeholder values: the facts above fill in only from live reads of the published contract.

FAQ

Honest answers about what GeoAI can and cannot do.

No. It shows what the chain and explorers answer, with the block and method behind each finding. “Not detected” never means “does not exist”, and nothing here replaces an audit.

Public Robinhood Chain JSON-RPC endpoints (official, publicnode, drpc, with chain-id checks and failover), Sourcify and the Blockscout explorer API for verified source and address history, and an optional trace endpoint for internal calls. Every evidence record names its provider.

Only the evidence bundle of the current investigation. Every factual claim must cite evidence ids, and the server rejects citations that do not exist. Without a configured model key, Ask Geo shows a deterministic findings summary instead and never pretends to be AI output.

Only when a trace-capable endpoint answers debug_traceTransaction. Otherwise the transaction page says “Internal call trace unavailable” rather than reconstructing them from incomplete data.

It is bounded: the newest page of indexed transactions and token transfers for an address, or the decoded events of one transaction. The graph states its block range, page limit and whether older history exists.

No. It is stored in your browser and refreshes only when you ask. GeoAI runs no background workers, so it makes no monitoring claims.

The contract address is not published yet: the token block on this page and /token say “CA: Soon” until the address is written into the site record and deployed, and that happens here first. Until then, no address claiming to be $GEOAI is ours. Once published, the block reads the contract live (name, symbol, decimals, total supply, Sourcify verification) with evidence records, and never states a price, a market value or a utility.

Start

Start with an address.
Follow the evidence.

Paste an EVM address or a transaction hash. GeoAI reads Robinhood Chain live and shows every record behind what it says.

EVM address (0x + 40 hex) or transaction hash (0x + 64 hex).