Relation
rel_265
Curated · btcintel
claims we make, each with its source and citation · sources may contradict; we show the set, never a score
The claim
- fetch —sha256 dc1639caa5501d72rel_265btcintel:relations:265@v1 sha256:3af2c5ad2f50de0econfidenceauthority data · 60
Versions
| version | created | actor | content sha256 | citation |
|---|---|---|---|---|
| v1current | 2026-09-22 14:42 UTC | importer:mitre-attack | 3af2c5ad2f50de0e11372564c6a2e493156e85d3f25477cbb7f532cff257d7e6 | btcintel:relations:265@v1 sha256:3af2c5ad2f50de0e |
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/rel_265?version=1" | grep -i etag
# ETag: "3af2c5ad2f50de0e11372564c6a2e493156e85d3f25477cbb7f532cff257d7e6"
curl -s "https://api.btcintel.io/v1/claims/rel_265?version=1" | jq -r .content_sha256
# 3af2c5ad2f50de0e11372564c6a2e493156e85d3f25477cbb7f532cff257d7e6
# the first 16 hex are the citation's: btcintel:relations:265@v1 sha256:3af2c5ad2f50de0eEvery 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.
Community
Community notes about this claim's subject
Community content is indexed from Nostr and not endorsed by btcintel.
not computed yetNot indexed yet: the community index has not looked at this subject.