BTCintel
nodeok
mempool78,479 tx
node next1.01 sat/vB
retarget29 blocks
chainmainnet

Relation

rel_621

relationversion 1 · current

Curated · btcintel

claims we make, each with its source and citation · sources may contradict; we show the set, never a score

The claim

  • MITRE ATT&CK Enterpriserecords thatHEXANEusesDanBot
    fetch —sha256 dc1639caa5501d72
    rel_621btcintel:relations:621@v1 sha256:ddf51ff90d63d5c7
    confidenceauthority data · 60

Versions

versioncreatedactorcontent sha256citation
v1current2026-09-22 14:42 UTCimporter:mitre-attackddf51ff90d63d5c7cd906f963f1e48c76fcb79193b7500f38a35e40accadeed7btcintel:relations:621@v1 sha256:ddf51ff90d63d5c7

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_621?version=1" | grep -i etag
# ETag: "ddf51ff90d63d5c7cd906f963f1e48c76fcb79193b7500f38a35e40accadeed7"

curl -s "https://api.btcintel.io/v1/claims/rel_621?version=1" | jq -r .content_sha256
# ddf51ff90d63d5c7cd906f963f1e48c76fcb79193b7500f38a35e40accadeed7
# the first 16 hex are the citation's: btcintel:relations:621@v1 sha256:ddf51ff90d63d5c7

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.

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.