← PRODUCT
PRODUCT · SCREEN

GateDNAwallet fingerprint

A deterministic wallet fingerprint from public history: age, activity, stablecoin share, counterparties.

GateDNA · wallet profileevm · blockscout
Age
unknown (≥ 0 d, bounded)
Transactions
200 read · 30,422,181 total
Stablecoin share
79%
Counterparties
111
Coverage
BOUNDED
  • First activity date unknown — pages read newest-first
  • 79% of token transfers are stablecoins
Caveat: 200 of 30,422,181 transactions were read, so age and counterparty counts are lower bounds. Observed facts only — no score.
On this page

What it does

GateDNA is a deterministic fingerprint of one address from its public history — Blockscout REST on EVM chains, TronGrid on Tron. It reports age, first and last seen, in/out counts, token-transfer count and stablecoin share, distinct and top counterparties (your registered wallets labelled), contract interactions, dust share, active days, burstiness, and two flags: newlyCreated and singleUse.

Two blocks matter. observed holds the facts. confidence says how much of the history was actually read — coverage FULL, BOUNDED (the page cap was hit), PARTIAL (a source failed) or NONE — plus plain-language caveats. facts are observation sentences only.

Why a broker needs it

"Is this wallet brand new, single-use, and has it only ever touched USDT?" is the question a reviewer asks first about a deposit wallet, and it is answerable from public data without any vendor. A fingerprint the same inputs always reproduce can be attached to the case and re-derived later; an opinion cannot.

How it works

GET /api/v1/wallets/profile?chain=…&address=…. The service pages through the address's transfers up to a fixed cap (five pages), computes every figure from the rows it read, labels counterparties that are registered wallets in your tenant, and records which sources answered. The same profile is shown on the wallet in the console.

What it does not do

A profile is never a risk score and never labels an address good or bad. It does not attribute counterparties to exchanges or services, it stops at the page cap on busy addresses (and says BOUNDED), and it covers EVM chains and Tron only.

API

GET /api/v1/wallets/profile?chain=tron&address=T…
{
  "observed":   { "ageDays": 3, "incomingCount": 1, "outgoingCount": 0, "stablecoinShare": 1,
                  "distinctCounterparties": 1, "newlyCreated": true, "singleUse": true, … },
  "confidence": { "coverage": "FULL" | "BOUNDED" | "PARTIAL" | "NONE", "pagesFetched": 1, "pagesCapped": false, "caveats": [ "…" ] },
  "facts":      [ "…" ]     // observation sentences only
}

Full reference: /docs#profile · OpenAPI 3.1

Try the sandboxRead the API docsRequest early access