What happened.
A specific mechanism at a stated point in blockchain history. An observation your team can examine.
BITPOORT REGISTRY / DATA FOR PEOPLE & AI
Blockchain intelligence for the on-chain economy.
Grounded in evidence. Built for AI.
Documented on-chain findings for analysts, applications and AI agents.
One origin. Three swap venues.
Follow 25.5 million USDC to the DEX/swap venues it was swapped through.
RECORDED PATH CONTEXT / RELATIONSHIPSELECT A NODE ↗
25,500,000 USDCRECORDED ORIGIN
OBSERVATION BLOCK14,442,840
01 / 05
HISTORICAL REPLAY / Examples from Bitpoort’s published RegistrySource & coverage ↗
A mechanism. A block. The supporting record. Explore the evidence before it enters your workflow.
01 Documented findings+02 Sources & methods+03 Stated coverage+04 Signed snapshots
01 / THE REGISTRY
Evidence your systems
can work with.
The Registry is our core product. Each record connects an observation to the transactions and method behind it, with its certainty and limitations in view.
{"mechanism": "LP_REMOVED","chain": "ethereum","evidence": ["transaction","event_log"],"reproduction": {"method": "event inspection","scope": "stated block"},"status": "illustrative"}
Where it comes from.
The supporting transactions and event references stay attached to the finding.
How it was found.
The method and reproduction steps make the reasoning behind the record inspectable.
What it can support.
Certainty, coverage and limitations help your team make its own assessment.
02 / FROM ACTIVITY TO EVIDENCE
From on-chain activity
to usable intelligence.
A useful finding needs a trail back to its source. The Registry keeps that trail with the record.
01 OBSERVE
Start with the chain.
Identify a recorded event or a contract behaviour at a specific block.
02 DOCUMENT
Keep the evidence.
Attach the relevant transactions, the method, and what the available data can support.
03 PUT TO WORK
Use it in your workflow.
Inspect a record, check address exposure or bring Registry data into your own systems.
The distinction matters. Direct observations and inference stay separate. Signatures protect record integrity; sources and methods support the findings.
03 / MONITORING & TRACING
Exploit intelligence.
Monitor reported exploits. Trace associated fund movements, with sources and coverage limits attached.
THE EXPLOIT REGISTERINTERNAL SNAPSHOT /
1,631
Exploit records catalogued
Reported incidents, with references.
20112026
$32.1B
Reported exploit losses catalogued
1,291 entries with reported loss figures.
1,291 with figures340 without
100%
Exploit records with sources
Public-source citations: 1,631 / 1,631.
Sources stay with the record
Register totals before deduplication. Reported losses are catalogued amounts, not funds traced or recovered by Bitpoort.
About the data
Snapshot of the internal Exploit Register, dated 15 September 2026. Counts refer to entries; duplicate incident records remain, so these are not unique-incident totals.
The $32.1B is the sum of reported loss figures across 1,291 entries, rounded to one decimal billion. Another 340 entries have no reported loss figure. Duplicate entries may affect that sum.
100% describes the presence of a public-source citation. It does not establish that every report has been independently verified or every incident reconstructed.
ILLUSTRATIVE FUND MOVEMENT
One origin. Two destinations.
Follow 100 demo units through a transit wallet into two modelled endpoints.
DEMO TRANSFER UNRESOLVEDSELECT A STEP ↗
SELECTED STEPIncident funds
The invented starting balance is 100 demo units. This is a modelled origin, not an observed exploit.
MODELLED TOTAL · 100 = 65 + 35 DEMO UNITSEXPLANATORY DEMO · NOT LIVE DATA
INTERNAL TODAY
Discuss exploit tracing The real Exploit Register is access-controlled. Traces can be partial; unresolved movements stay explicitly unresolved.
04 / BUILT FOR YOUR DESK
Built for compliance.
Engineered for investigation.
SCREENING WITH CONTEXTBring the evidence
Bring the evidence
into the assessment.
Use address exposure checks to identify connections to recorded activity. Give analysts the underlying findings to review as part of their screening process.
Exposure checksBulk dataRecord review
REGISTRY STANDARD
The Registry,
in your team’s workflow.
Documented findings, supporting sources and exposure checks for compliance teams, financial-crime units and the firms advising them.
Registry Standard
INTERNAL USE$200/ month
or $2,000 per year
Request accessinfo [at] bitpoort.com
Ethereum focusBitcoin advisory
View coverage and product details
Records with their sources.
Inspect documented findings with supporting transactions, methods and stated limitations.
Checks in your existing systems.
Use bulk API access and address exposure checks to support your team’s assessments.
Advisory, clearly labelled.
Keep advisory signals separate from directly observed activity when reviewing a finding.
Records your team can retain.
Use point-in-time snapshots for casework and internal reference, independently of Console.
05 / A FEW PRACTICAL DETAILS
System details.
Do we need to use Console?
No. Registry subscriptions can be used independently through your existing systems. Console is our investigation workspace for exploring activity and organising case findings. It is currently a live prototype.
Where does AI fit?
AI helps users retrieve and explain information. Integrations bring Registry data into software and AI workflows. Factual findings remain tied to the underlying records and methods.
What does the Registry cover?
Current coverage focuses on Ethereum transactions and tokens. Bitcoin information is advisory. Trace coverage has limits, which are stated with the product and its records. See current coverage ↗
What does a signed record establish?
A signature protects a record’s integrity. The sources and methods support its factual findings. Independent signature verification depends on published signing keys and the supported verification process; the current product page states what is available.