Chain adapters
Normalize BLCH events from Bloch Genesis-4 while preserving its eUTXO asset and finality rules.
GRAPHUS
A MATTER OF DATA 2.0
Graphus is graph analytics for BLCH on Bloch Genesis-4. Explore real script-hash and transaction references, query balances and inspect graphs with their sources, block anchors and coverage.
Real chain analytics · Source and coverage disclosed · No live wallet scoring
01 / PRINCIPLE
A transaction, a source record, and a graph path are different kinds of evidence. Graphus keeps them distinct, dated, and inspectable so analysts can see a reason for review without treating proximity as guilt.
02 / THE SYSTEM
Six linked layers make intelligence reproducible and reviewable. Each is designed to operate outside chain consensus and behind private access controls.
Normalize BLCH events from Bloch Genesis-4 while preserving its eUTXO asset and finality rules.
Carry source, license, timestamp, confidence, and expiry with every external claim. A stale signal stops at the gate.
Trace bounded value-flow paths and changing relationships. Shared infrastructure remains a confounder.
Evaluate only reviewed outcomes with time-separated tests, error costs, calibration, and rollback before any promotion.
Test proofs for small deterministic feature transforms or inference. Proof validity cannot establish source truth or model accuracy.
Show evidence paths and alternatives, record analyst decisions, and allow correction before consequential customer action.
03 / ASSET MAP
Explore the event model for BLCH on Bloch Genesis-4. The map describes architecture; Bloch has a bounded, source-reported indexer sample.
Script hashes, outputs, exact asset units, slot, and block lineage are tracked separately. A script hash does not identify a person.
Boundary: five-transaction indexer samples exist; full input resolution and reorg replay are future gates.
Illustrative system map. A graph edge is not an identity claim, a sanctions decision, or proof of illicit activity.
04 / GRAPH INTELLIGENCE
Select an example to see how Graphus would distinguish observations from claims. These examples are synthetic design illustrations.
FINALIZED EVENT · SOURCE ID · EXPIRY
A bounded, directed path can help prioritize review. The path is an association with source references and time limits; it is never a verdict about a person or wallet.
05 / ANALYTICS WORKBENCH
The research roadmap combines deterministic graph methods with measured ML. Every output needs its inputs, source time, uncertainty, and an alternative explanation.
Time-ordered paths, pass-through, fan-in and fan-out, peel-chain candidates, cycles, and shared-service hub warnings.
Prototype: bounded paths with finality, expiry, and bridge-proof gates.BLCH baselines, burstiness, concentration, dwell time, peer comparison, and missing-data-aware anomaly signals.
Roadmap: review leads, never illicit labels.Compare time-aware embeddings and graph models with transparent rule baselines. Use reviewed labels, entity-disjoint holdouts, calibration, and drift checks.
Current: validation gates only; no trained AML model.Reconstruct the exact path, source snapshot, block version, feature transform, and reason code behind an analyst view or model output.
Roadmap: reorg replay, correction, and dispute propagation.Separate identity and IP context from chain observations; use tenant-scoped pseudonyms, short retention, field rights, and private audit logs.
Current: prototype privacy helpers; legal review required.Benchmark verifiable feature computation or small inference against committed inputs and pinned code, with proof cost and leakage measured.
Research: no prover or proof deployed.06 / APPLICATIONS
Graphus is a shared technical layer. Each customer use has its own lawful purpose, rights, access boundary, and retention rule.
Bloch Inc Proof of Red and Blue Score can use Graphus BLCH transaction signals and reviewer workflows. Results are advisory, tenant scoped, and external to Bloch Protocol.
Open BLCH Analytics LabDocumented flows and asset activity for authorized market infrastructure research, with aggregation and source rights matched to the use.
Track chain adapters, source freshness, reorgs, and data quality without exposing wallet-level findings on public pages.
05 / TRUST BOUNDARY
No on-chain labels. Graphus does not change validation, transaction acceptance, blocks, or balances.
Minimized personal data. Identity and IP context remain separate, restricted, and purpose limited.
Reviewable signals. Disputes, expiry, and source updates can downgrade or remove a finding.
Bounded live script facts. Bloch script-hash lookups report source data and limits; no production AML model or ZK proof is deployed.
06 / ROADMAP
Dedicated data and ML hosts, Bloch indexer sample probe, and source-height checks for Bloch Genesis-4.
Rights-reviewed ingestion, bounded storage, replay, reorg handling, and finality verification.
Reviewed labels, temporal holdouts, false-positive costs, calibration, bias tests, and analyst appeal flow.
Benchmark a small ZK proof for feature transforms or inference before deciding whether it belongs in a service.
GRAPHUS OF BLOCH INC
Better intelligence begins with a better account of what the data can actually support.