BlokzsDATUM Observatory

Methodology

How a block becomes a signal

Every number in Blokzs traces back to an observable property of a block. Classification is binary: DATUM-built or OCEAN-built.

1. OCEAN attribution

  • We first identify blocks attributed to OCEAN using public Bitcoin / mempool.space data (pool slug “ocean”).
  • Height, hash, timestamp, reward, total fees, weight, size and transaction count are stored verbatim — no value is generated, smoothed or estimated.
  • The current dataset is a frozen checkpoint. The provider is mode-switchable: flipping it from checkpoint to live changes the source, not the UI.

2. Template origin

  • Each OCEAN block is classified as DATUM-built or OCEAN-built — a binary split from observable coinbase structure.
  • For each block the raw coinbase scriptSig is parsed into Bitcoin push operations. OCEAN stamps a pool marker (“OCEAN.XYZ”). DATUM Gateway uses a 0x0F delimiter plus a 7-byte unique-id push immediately after the tag push.
  • DATUM: 0x0F delimiter in the tag push and PUSH(7) unique-id immediately after the tag push (datum_coinbaser.c). Optional PUSH(14) extranonce in scriptSig on older Gateway builds.
  • OCEAN: pool marker present without the Gateway uid layout — e.g. no delimiter (963084) or PUSH(2) instead of PUSH(7) at the post-tag slot (963180).

3. Miner identity

  • For DATUM-built blocks, the secondary coinbase tag is extracted and shown exactly as published.
  • The tag may be arbitrary: cc, 888, Thats right, DATUM User, a company name, an anonymous phrase, or any other string.
  • These values identify an observable coinbase identity, not necessarily a legal person or company. Tag text never classifies a block as DATUM.

4. No invented attribution

  • If Blokzs cannot verify a miner identity, the tag field is left empty — classification still resolves to DATUM or OCEAN.
  • No inferred company names. No fabricated miners. No fake precision.
  • Pool-level expected blocks and luck use the observed OCEAN share of network blocks. Luck is never calculated for an individual miner tag without underlying hashrate data.
  • Speculative scores (sovereignty, template diversity, TIDES vs FPPS) are not shown as product metrics until they can be derived honestly.