att_10066

The claim

• Luxortag matchvia bitcoin-data mining pools

  evidencerun Powered by Luxor Tech] · catalog pool-catalog-bitcoin-data · pattern Luxor Tech · match kind contains · signature 10

  fetch —sha256 ddc505c82dfa5868valid from 2026-10-16matcher pool-matcher-v1

  att_10066btcintel:attributions:10066@v1 sha256:02574936978a8a49copy citation
  confidenceweb crawl · 20

Versions

Verify

A citation names a claim id, a version and the first 16 hex of the content hash of that version. Fetch the version and compare: the hash must start with the citation's 16 hex, and the ETag of the answer is the same hash.

curl -sI "https://api.btcintel.io/v1/claims/att_10066?version=1" | grep -i etag
# ETag: "02574936978a8a4924c74b19f1a7e23beb24e26067431962fafd05b4e1009a71"

curl -s "https://api.btcintel.io/v1/claims/att_10066?version=1" | jq -r .content_sha256
# 02574936978a8a4924c74b19f1a7e23beb24e26067431962fafd05b4e1009a71
# the first 16 hex are the citation's: btcintel:attributions:10066@v1 sha256:02574936978a8a49

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.

Dispute

A dispute names the claim id and a reason; it is recorded under your npub, counted on the claim, and ops resolve it next to the claim with a reason and a date.