Bloch IncGRAPHUS

GRAPHUS OF BLOCH INC / DATA AS A SERVICE

Evidence-grade
data delivery.

Graphus DaaS is the proposed programmable data layer for chain events, wallet flows, source provenance, and transparent ML features. Initial scope: BTC, ETH, Ethereum USDT/USDC, and BLCH. The current API exposes a product manifest only; no live transaction feed or score is available.

Explore the data atlas View live API manifest

Checking API manifest…

01 / PRODUCT LINES

More than a feed.
Traceable context.

Each product keeps network and asset semantics, event identity, finality, source version, and uncertainty attached to the result.

PUBLIC / PROPOSED

Chain facts API

Blocks, transactions, outputs or logs, precise asset units, confirmation state, reorg revision, and canonical source pointers.

Current: a bounded private Bloch sample, source probes, and offline ETH/BTC parsers; no public live transaction feed.
PUBLIC / PROPOSED

Flow graph API

Bounded wallet-to-wallet paths, time ordering, fan-in and fan-out, counterparties, bridge-proof gates, and attribution caveats.

Current: synthetic constellation and bounded graph prototype.
PUBLIC / PROPOSED

ML transparency feed

Feature definitions and values, model card, version, validation cohorts, calibration, drift, uncertainty, and known failure modes after review.

Current: no trained or validated AML model.
DELEGATED / FUTURE

AML score service

A separate authenticated score response for explicitly delegated, identity-verified people with tenant, purpose, scope, expiry, and audit.

Current: no live score endpoint.
PRIVATE / FUTURE

Research workspace

Personal notes, saved queries, watchlists, case collaboration, alerts, exports, and source-aware annotations.

Current: account and annotation code prepared; activation pending login choice.
ENTERPRISE / FUTURE

Delivery contracts

Versioned REST and eventual event delivery, quotas, usage accounting, schema contracts, uptime targets, and licensed source rights.

Current: product design; no SLA claim.

02 / DATA CONTRACT

One event.
Every necessary field.

A normalized movement must keep the raw event reference and its chain-specific interpretation. Bitcoin inputs do not by themselves identify a person or a wallet owner.

Canonical keys

  • network · asset · transaction ID · event index
  • block or slot · observed time · ingested time
  • value in exact native units · direction semantics
  • finality state · source ID · source revision
  • reorg/deletion version · quality flags

Analytical keys

  • bounded path and edge type
  • feature schema and calculation window
  • source confidence and expiry
  • model version and validation metadata
  • uncertainty, alternatives, and non-score explanations

03 / ACCESS

Public insight.
Explicit delegation.

Public ML details can be deep without publishing a protected AML score. Identity context, raw IP, private case notes, and confidential source claims stay outside the public feed.

OPEN

Explore

Factual search, wallet constellations, source quality, graph flows, and lawful non-score ML details after production gates.

REGISTERED

Research

Private annotations, saved searches, alerts, exports, and usage history when account activation is complete.

EXPLICIT GRANT

Decide

Only a specifically named and verified person can request a future score within the approved purpose and scope.

GRAPHUS OF BLOCH INC

A Matter of Data 2.0

Every data product should explain what it knows, where it came from, and what it cannot prove.

Explore wallet flows Workspace preview