01 / TIME SERIES
Red and Blue over time
Red / transaction risk Blue / wallet context
View chart data
| Period | Red | Blue | Signals |
|---|
Source: Bloch Inc synthetic fixture · Scores 0–1000 · No measured performance
BLOCH INC / INTELLIGENCE INFRASTRUCTURE
Proof of Red
and Blue Score.
External AML evidence infrastructure for Bloch transactions and wallet context, powered by the proposed Graphus of Bloch Inc data layer. Source-aware, explainable, and designed for human review.
01 / OVERVIEW
Evidence with context.
Decisions with review.
Red represents transaction-level risk signals. Blue summarizes wallet behavior and data quality. Neither is a verdict, and neither changes Bloch consensus.
Loading synthetic fixture…
02 / SIGNAL INTELLIGENCE
See the signal.
See its limits.
Every visualization has an adjacent data table and a source note. Production sources would carry license, observed time, confidence, and expiry.
SYNTHETIC
02 / DISTRIBUTION
Transaction risk bands
View chart data
| Score band | Transactions |
|---|
Source: synthetic fixture · Counts are hand-authored and internally consistent
03 / TYPOLOGIES
Signals by reason code
View chart data
| Code | Typology | Count |
|---|
Source: synthetic fixture · Multiple signals may relate to one transaction
04 / FLOW CONTEXT
Evidence, not association guilt
Wallet context Transaction observation Source record
Concept diagram only · No real wallets, identities, sanctions, or transaction graph
03 / SERVICE ARCHITECTURE
Connected to Bloch.
Independent of consensus.
BI-PoRB reads finalized chain data and permitted third-party APIs. It returns expiring evidence to private customer workflows; Bloch validation never depends on the service.
01
Observe
BLOCH RPC / INDEXER
LICENSED DATA APIs
02
Normalize
FINALITY + REORG CONTROL
SOURCE RIGHTS + FRESHNESS
03
Explain
RED TRANSACTION SIGNALS
BLUE WALLET CONTEXT
04
Review
HUMAN CASE WORKFLOW
PRIVATE TENANT API
Protocol boundaryNo block-header field, validator requirement, on-chain reputation, or automatic transaction denial.
04 / GOVERNANCE
Rich data requires
strong boundaries.
Live operation starts only after purpose, legal basis, controller roles, source rights, retention, regional transfers, and an impact assessment are reviewed.
Trace every finding
Source, observation date, confidence, attribution level, license, expiry, and dispute state travel with each signal.
Private by default
AML scores need explicit delegated, verified, tenant-scoped access with purpose and audit; lawful public chain facts and ML detail are planned for everyone.
Keep people in the loop
Potential matches prompt verification. Customers retain a challenge and correction path before significant action.
Collect for purpose
No identity documents, raw memos, card data, or sensitive personal details enter the public dashboard.
SOURCE REGISTRY
Data lineage preview
| Source | Purpose | Observed | Validity |
|---|
No real provider API is connected.
HUMAN REVIEW
Case queue preview
| Case | Signal | State | Age |
|---|
Case identifiers are fictional. No person or wallet is identified.
05 / OFFICIAL SOURCE SNAPSHOT
Public source.
Precise attribution.
The local connector reads OFAC's official SDN files and publishes aggregate source metadata. Exact identifier screening remains private and requires verification.
Loading official source metadata…
No customer wallet or person is screened by this public page.
View the official OFAC source ↗06 / MULTI-CHAIN DATA PLANE
Three networks. Five assets.
One evidence contract.
Each network has different transaction semantics. The status below separates a live source probe from planned ingestion and scoring.
Bloch
eUTXO inputs, outputs, slots, and reported finality from the historical indexer.
Ethereum
Native transfers, token logs, contracts, traces, and finalized block lineage.
USDT + USDC
Issuer-pinned ERC-20 Transfer logs on Ethereum, with exact event identity and finality.
Bitcoin
UTXO provenance, prior output resolution, reorgs, and cautious address attribution.
Bloch source probeLoading public indexer status…
No live AML score is calculated from this source probe.
07 / DELIVERY ROADMAP
Build the evidence layer.
Validate before launch.
The preview demonstrates interface and boundaries. Live screening requires engineering, operational, legal, and model validation gates.
- NOWSource-backed preview
Synthetic risk dashboard, official OFAC metadata, and bounded Bloch source probe.
- NEXTData governance
Source rights, lawful basis, retention, transfer assessment, impact review.
- BUILDThree network adapters
Bloch, Ethereum native plus USDT/USDC ERC-20, and Bitcoin finality, reorg rollback, and provenance.
- VALIDATEPrivate intelligence
Tenant authentication, human review, appeals, and real-world model evaluation.
BLOCH INC / BI-PoRB
Intelligence that stays
accountable.
Explore the architecture and synthetic data. Live AML screening is a future gated capability.