DEVELOPERS / VERIFIED PUBLIC API

Read Blackcoin chain data.

Chain telemetry is checked for source agreement and every public response is re-validated against an exact public schema before anything leaves this origin. Responses fail closed unless an endpoint below expressly documents bounded last-verified continuity. Quantum, supply, and release responses label retained data and expire it after one hour; no stale record is presented as current. Mutable Explorer machine endpoints, record lookups, and readiness remain strict. Coverage bounds are disclosed wherever an index is partial.

No authentication or API key is required. Observe the per-client request limits. Amounts are exact integer-sats strings; heights are integers; hashes are lowercase hex.

The visible Explorer home dashboard may temporarily display five explicitly labeled last-verified aggregates. That UI-only continuity route is not part of the machine API: keep clients on /api/explorer/*, which never substitutes retained records.

AI agents & MCP →Connect an MCP Streamable HTTP client. The hosted endpoint requires no API key or local server.Keystone evaluation stack →Evaluate the deposits-disabled reference on regtest. It is not independently audited and must not hold customer funds.Integration guide →Use your own node for deposit detection. Read public data with curl, JavaScript, or Python.Run a node →Per-OS install, blackcoin.conf, staking, pruning, systemd/docker, troubleshooting.Whitepaper →Protocol V4 spec: PQC, Gold Rush, migration, RPC & consensus reference.Chain params →Machine-readable ticker, decimals, HRP, phase heights, endpoints.OpenAPI →Import the API contract into Postman or Insomnia.API changelog →Version history + deprecation policy for the versioned contract (also /api/changelog.json).Verify it yourself →Reproduce every number on your own signed-source node.Brand & press kit →Logo assets, asset facts, palette, official links.Security & known issues →Private vulnerability reporting, release verification, and known issues.

FOR EXCHANGES & CUSTODIANS / READ THIS FIRST

This public API provides read-only telemetry and explorer records. It exposes verified chain and Protocol V4 accounting data for display and analytics. It does not create addresses, hold keys, track deposits, sign, or broadcast. To list or custody Blackcoin, independently qualify the published production daemon (blackcoind) from the downloads rail against your own infrastructure and integrate custody through its JSON-RPC interface. Verify balances and history independently with the reproduction contract; the daemon is the source of truth, this API is a mirror of it.

Evaluate an integration reference. Blackcoin Keystone is a separately versioned, historical evaluation bundle. It packages a pinned v30.1.3 node with a deposits-disabled, targeted regression-tested integration daemon. It boots on regtest via docker compose up (tarball · sha256). It is not independently audited or production custody software; do not use it with customer funds. It is not a 30.1.5.1 distribution or evidence of current-release compatibility. See the current upgrade and version-identity guidance.

Listing applications: [email protected]
Technical & custody integration: [email protected]
General exchange contact: [email protected]

Integrate Blackcoin into your platform

CORS is open on every read endpoint. Fetch directly from any origin without an API key or proxy: fetch("https://projectblackcoin.org/api/v3/quantum").then(r => r.json())
Stream live state. new EventSource("https://projectblackcoin.org/api/v3/quantum/stream") delivers verified snapshots from the feed used by this site. Check each snapshot's timestamp and quality, including after reconnecting.
Validate responses in your client. Check the documented schema, freshness, height, and hash before using a record. This site also validates public responses before serving them.
Run your own. The daemon itself carries the full explorer surface (txindex, shadowindex, getgoldrushblock, getshadowaddress and friends are enabled in the production build). Point the open-source release from the downloads rail at your infrastructure and you can serve this entire contract yourself.
Drop in the live badge. <script src="https://projectblackcoin.org/embed.js" async></script> renders a self-updating height + materialized-credits badge anywhere (add data-target="#css-selector" to control placement).
Machine-readable contract. The full surface is described in openapi.json; live health for every endpoint is at /status, and the reproduction contract lives at /verify.
Attribution welcome, not required. If you display this data, linking the exact record on this explorer (every response includes heights and hashes) lets your users verify it independently.

GET/api/v3/quantum

Current quorum-verified Gold Rush snapshot: anchor, shadow pools, next-block projections, source identity.

Quality ladder live / delayed / last_verified by snapshot age; strong ETag keyed on a content hash of public fields; 503 with {schema_version:3,status:"unavailable"} when no snapshot inside the one-hour retention window passes validation.

SSE/api/v3/quantum/stream

Bounded text/event-stream pushing each accepted snapshot as event: snapshot.

Event id is <height>:<snapshot_id>:<quality>; retry hint 5000 ms.

GET/api/v3/lifecycle

Quorum-attested schema-12 replay marker (with commitment hash), protocol phase, and the published consensus schedule.

GET/api/quantum

Legacy schema-2 snapshot envelope, preserved unchanged for existing consumers.

GET/api/releases

Validated release catalog from the signed GitHub record: platform-classified binaries and the verification rail (checksums, SBOM, provenance, evidence).

A validated catalog may remain available for at most one hour during a GitHub interruption. Retained responses are explicitly last_verified and carry Warning: 110 plus X-Data-Quality/Verified-At/Expires-At/Age-Seconds. Download redirects are live-only and resolve the pinned GitHub asset ID to a fresh GitHub-signed target; retained or unverified asset identities return 503.

GET/api/supply

Base-chain supply sample (JSON: sats and decimal BLK). Plain-text aggregator endpoints: /api/supply/circulating and /api/supply/total.

Inner sample_* fields preserve the Explorer producer's collection and restart provenance. The outer quality/verified_at/expires_at/age_seconds fields describe this site's delivery and retention state. Samples older than 10 minutes, Explorer-retained samples, or a site disk fallback are labeled last_verified, never live, and expire one hour after sampled_at. JSON and plain-text responses carry the same X-Data-* quality headers.

GET/api/ready

Dependency readiness with separate live, operational, ready, restart-recommended, and catch-up state for each component, including an explicit fully reconciled supply read.

HTTP 200 requires observer quorum/agreement, a fresh canonical tip, synchronized required indexes, canonical address anchoring, complete base coverage, gap-free payload-complete shadow coverage, and a non-null fully validated supply sample. Operational catch-up remains an explicit 503 not_ready state and is not a restart instruction.

SSE/api/explorer/stream

Best-effort canonical-tip notifications (forward block, rollback, or same-height reorg). Legacy event:block frames retain the raw block payload and integer-height ID; additive event:block-v3 frames carry the public schema-3 envelope and height:hash ID. This is not a lossless event log or reorg replay service: refetch and reconcile by height + hash after every connect/reconnect or detected gap.

GET/explorer/address/{address}/feed.xml

Atom feed of an address's shadow payouts. Read it in a compatible feed reader without an account.

GET/api/explorer/network

Network telemetry, client-version shares, and public peer IPs with protocol, direction, connection times, ping, services, and traffic counters. Public peer data describes one observer at the stated observation time. Outbound endpoints can be used for addnode entries; inbound listening ports are not inferred.

GET/api/explorer/status

Chain status, observer agreement, tip freshness, per-index state, and canonical base/shadow coverage integrity.

GET/api/explorer/recent-blocks?limit=1..50&before=<height>

Newest blocks with base and shadow summaries; `before` pages backward through history.

GET/api/explorer/block/{height|hash}?tx_offset&tx_limit

Full block record: header, paginated transactions, and every shadow event anchored to the block.

GET/api/explorer/tx/{txid}?vin_offset&vin_limit&vout_offset&vout_limit

Transaction with prevout-resolved inputs and spentness where provable; unknowables stay null, never guessed.

GET/api/explorer/address/{address}?offset&limit&shadow_offset&shadow_limit

Base-chain activity within disclosed coverage plus the complete synthetic payout history with independent pagination.

GET/api/explorer/shadow/tx/{synthetic_txid}

Synthetic payout record: lifecycle state, maturity, demurrage facts, spend linkage.

GET/api/explorer/shadow/supply

Anchored shadow supply: pools, materialized and phase-locked totals, claim counts.

GET/api/explorer/events

Recent shadow events (claims, distributions, signals) from the sanitized public stream.

GET/api/explorer/analytics/leaderboard?limit=1..100

Addresses ranked by materialized payouts, with PoW/PoS split and active range.

GET/api/explorer/analytics/series?from=<height>&to=<height>

Bucketed per-block series (payout value, event counts) for charting, capped at 240 points.

GET/api/explorer/search?q=<height|hash|txid|address>

Classifies a query and returns the exact explorer path for it.