ASTERIQASTERIQ

How it works

How to read ASTERIQ

What the product does, where every number comes from, and the things it deliberately refuses to guess.

The path a case takes

  1. 1

    You give ASTERIQ a starting point

    A wallet address, a transaction hash, or a contract address on a connected network. Nothing is assumed about it: submitting an address is not a claim that it is guilty, and ASTERIQ does not store seed phrases or private keys at any point.

  2. 2

    ASTERIQ reads the chain

    Balances, nonces, and contract code come from the network's own JSON-RPC node, and the chain id is checked before any answer is kept. Transfer lists come from the chain's Blockscout explorer index. If either is unreachable, the screen says so rather than inventing a result.

  3. 3

    Destinations become nodes you can expand

    Every outgoing transfer gives a counterparty. Expanding one reads that address's own index and adds its rows. The graph grows one indexed hop at a time, and each hop keeps its source and the moment it was retrieved.

  4. 4

    A watch keeps the wallet under observation

    A watched wallet is polled against the explorer index on each sync. A rule decides when a row becomes an alert: any activity, outgoing movement, or a transfer over a whole-wei threshold you set.

  5. 5

    The case exports as evidence

    A report is the stored investigation written out as JSON: every node, every edge, every source URL, and a disclaimer. It is an evidence package for someone else to act on, not a promise that anyone will.

Evidence

Every chain result carries a basis, a confidence, a source, a source URL, the time it was retrieved, the chain it came from, and a plain explanation. A JSON-RPC fact is labeled on-chain and verified. A Blockscout list is labeled an external index, because it is a list the explorer built, not a trace the node performed. A result that is missing is shown as missing.

Verified fact

Read from the chain and checkable against the explorer.

External intelligence

Published by a named outside source with an evidence link.

Algorithmic inference

Produced by analysis. A lead, not a finding.

Community report

Filed by a user. An allegation until a moderator reviews it.

Supported networks

Robinhood Chain, chain id 4663, is connected through its public RPC and Blockscout explorer. Ethereum and Base are queried only once ETHEREUM_RPC_URL or BASE_RPC_URL is set; until then they report PROVIDER NOT CONFIGURED and no request leaves the server. Every other network in the catalog is listed so its state is honest: a lookup is refused with HTTP 409 before any call is made.

Reading the network catalog…

What ASTERIQ will not do

Clustering and shared ownership
Not implemented. Two addresses transacting does not mean one person controls both, and ASTERIQ will not say that it does.
Exchange attribution
No attribution source is configured. An address is only named as an exchange when a stored wallet label with category 'exchange' says so.
Risk scores
Not running. Every address lookup returns risk status 'not assessed'. No address is labeled malicious by an algorithm here.
Cross-chain tracing
Not implemented. A trail that crosses to another network is not followed, and POST /api/v1/trace/jobs returns 501 rather than producing a graph.
Recovery and freezing
ASTERIQ cannot freeze an account, reverse a transaction, or recover funds, and it does not predict whether anyone else will.
File evidence
Uploads are not enabled. Evidence is kept as https links and notes.

Accounts and wallets

Email registration and Sign-In with Ethereum both create an httpOnly session cookie. Wallet sign-in signs a one-time nonce and recovers the address from the signature; an address that has not signed a challenge is never treated as proof of ownership. ASTERIQ never asks for a seed phrase, a private key, or a payment, and it cannot sign a transaction or move funds. Solana sign-in returns HTTP 501 and is not implemented.

Community labels

Forum posts and wallet reports are user-submitted claims. A report starts at Unverified. Only a moderator can move it to Under Review, Verified, or Rejected, and verifying a report does not place the address into threat intelligence — promoting it is a separate, deliberate moderator action. Reading the forum needs no account; posting, commenting, reacting, and reporting require a session.