btcintel

Foundry USA · block 968,768

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 968,768 to Foundry USA, by the payout address.

mempool mining pools · service data · 50 · in force since 27 Sep 2026

version
1 of 1
in force
in force since
27 Sep 2026
01:39 UTC
first read
27 Sep 2026
01:39 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
bc1qtm7ye0wm085hhv88japwkalmwkt3amec5z9c7a3unv05tfg6y2pstr3xfzoutput 0 of the coinbase pays it · the catalog lists it for this pool
matcher
v1
the source's file
sha256 146337aeaa4b877f735c59197cad904fcfa3ee7e34e2cc9bbb8593504cafaed5

the days

the block was mined
27 Sep 2026 01:39 UTC
reported by the source
no report date: the record carries none
first read
27 Sep 2026 01:39 UTC
in force since
27 Sep 2026 01:39 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:1573@v1 sha256:234cc980625932f5
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 27 Sep 2026 01:39 UTC by the pool matcher, v1in forcethis pagebtcintel:attributions:1573@v1 sha256:234cc980625932f5

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_1573?version=1" | grep -i etag# ETag: W/"234cc980625932f5710942128acd5a10eada7d2defdac46fac9a6ff7dde2a0a8-gzip" curl -s "https://api.btcintel.io/v1/claims/att_1573?version=1" | jq -r .content_sha256# 234cc980625932f5710942128acd5a10eada7d2defdac46fac9a6ff7dde2a0a8# the first 16 hex are the citation's: btcintel:attributions:1573@v1 sha256:234cc980625932f5
it must give
234cc980625932f5710942128acd5a10eada7d2defdac46fac9a6ff7dde2a0a8

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.