btcintel

SpiderPool · block 975,434

block attributionin forceversion 1

The attribution of one block to a pool by one source, mempool mining pools. The block's page lists every source's attribution, side by side.

mempool mining pools attributes block 975,434 to SpiderPool, by the payout address.

mempool mining pools · service data · 50 · in force since 11 Nov 2026

version
1 of 1
in force
in force since
11 Nov 2026
12:47 UTC
first read
11 Nov 2026
12:47 UTC
rests on
1
an output of the coinbase that pays a listed address
disputes
0
none open · none resolved

Attributions

the claim · what it says, what it rests on, since when

what is said

how
by the payout address
source
mempool mining poolslicence: MIT
class
service data · 50from the service's own publication

Pool catalog: mempool/mining-pools (MIT)

what it rests on 1

payout address
1BM1sAcrfV6d4zPKytzziu4McLQDsFC2Qcoutput 0 of the coinbase pays it · the catalog lists it for this pool
matcher
v1
the source's file
sha256 30380cf68d478e7d33b2dd073ba61a78019f829768031b2867e24ba9eb7116f1

the days

the block was mined
11 Nov 2026 12:48 UTC
reported by the source
no report date: the record carries none
first read
11 Nov 2026 12:47 UTC
in force since
11 Nov 2026 12:47 UTC
file read
not served: the record carries the file's hash and no time

An attribution is one source's reading of one block by one method. The block's page lists every source's, in one fixed order and with no winner.

The record

cite it · its versions · check that what you quote is what is served

Citea citation names one claim at one version

citation
btcintel:attributions:20704@v1 sha256:f4b099d78b41997b
this version
the link that pins version 1it keeps showing version 1 when a later one is written
as a file
a block attribution is not exported as STIX: the API serves no file for it

Versions1 version

  1. Version 1 · written 11 Nov 2026 12:47 UTC by the pool matcher, v1in forcethis pagebtcintel:attributions:20704@v1 sha256:f4b099d78b41997b

Verifythe hash of what is served must begin with the citation's 16 hex

A citation names a claim, a version and the first 16 hex of that version's content hash. Fetch the version and compare: the hash must begin with the citation's 16 hex. The ETag of the answer carries the same hash: production answers it weak (W/) and with its encoding's suffix (-gzip), or bare.

curl -sI "https://api.btcintel.io/v1/claims/att_20704?version=1" | grep -i etag# ETag: W/"f4b099d78b41997b9dbd4f85c3f3a55879cc98a2719020756781aee62af1e78b-gzip" curl -s "https://api.btcintel.io/v1/claims/att_20704?version=1" | jq -r .content_sha256# f4b099d78b41997b9dbd4f85c3f3a55879cc98a2719020756781aee62af1e78b# the first 16 hex are the citation's: btcintel:attributions:20704@v1 sha256:f4b099d78b41997b
it must give
f4b099d78b41997b9dbd4f85c3f3a55879cc98a2719020756781aee62af1e78b

Every change to the content writes a new version with its own hash; the previous version keeps its hash and its citation, so a quote never changes under the reader.