Foundry USA · block 975,519
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,519 to Foundry USA, by the tag in its coinbase.
mempool mining pools · web crawl · 20 · in force since 12 Nov 2026
- version
- 1 of 1
- in force
- in force since
- 12 Nov 2026
- 04:17 UTC
- first read
- 12 Nov 2026
- 04:17 UTC
- rests on
- 1
- a match of the catalog's pattern in the coinbase's text
- disputes
- 0
- none open · none resolved
Attributions
the claim · what it says, what it rests on, since whenwhat is said
- pool
- Foundry USA
- how
- by the tag in its coinbase
- source
- mempool mining poolslicence: MIT
- class
- web crawl · 20read on a public web page
Pool catalog: mempool/mining-pools (MIT)
what it rests on 1
- text found in the coinbase
=/Foundry USA Pool #dropgold/vca- the catalog's pattern
Foundry USA Pool- how it matched
- the text contains the pattern
- matcher
- v1
- the source's file
sha256 30380cf68d478e7d33b2dd073ba61a78019f829768031b2867e24ba9eb7116f1
the days
- the block was mined
- 12 Nov 2026 04:20 UTC
- reported by the source
- no report date: the record carries none
- first read
- 12 Nov 2026 04:17 UTC
- in force since
- 12 Nov 2026 04:17 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 servedCitea citation names one claim at one version
- citation
btcintel:attributions:20943@v1 sha256:9aa1507be213c54a- 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
- Version 1 · written 12 Nov 2026 04:17 UTC by the pool matcher, v1in forcethis page
btcintel:attributions:20943@v1 sha256:9aa1507be213c54a
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_20943?version=1" | grep -i etag# ETag: W/"9aa1507be213c54ac9a3fcb64aa857d9534683e6f0ad0d2c278c73f6661b6779-gzip" curl -s "https://api.btcintel.io/v1/claims/att_20943?version=1" | jq -r .content_sha256# 9aa1507be213c54ac9a3fcb64aa857d9534683e6f0ad0d2c278c73f6661b6779# the first 16 hex are the citation's: btcintel:attributions:20943@v1 sha256:9aa1507be213c54a- it must give
9aa1507be213c54ac9a3fcb64aa857d9534683e6f0ad0d2c278c73f6661b6779
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.