BTCintel
nodeok
mempool78,486 tx
node next1.01 sat/vB
retarget33 blocks
chainmainnet

Relation

rel_379

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 thatMofangusesShimRat
    fetch —sha256 dc1639caa5501d72
    rel_379btcintel:relations:379@v1 sha256:3a0af9a32a1893f8
    confidenceauthority data · 60

Versions

versioncreatedactorcontent sha256citation
v1current2026-09-22 14:42 UTCimporter:mitre-attack3a0af9a32a1893f81a760758e7037e1b83dccba5f672fdab06804f6ccce53e75btcintel:relations:379@v1 sha256:3a0af9a32a1893f8

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_379?version=1" | grep -i etag
# ETag: "3a0af9a32a1893f81a760758e7037e1b83dccba5f672fdab06804f6ccce53e75"

curl -s "https://api.btcintel.io/v1/claims/rel_379?version=1" | jq -r .content_sha256
# 3a0af9a32a1893f81a760758e7037e1b83dccba5f672fdab06804f6ccce53e75
# the first 16 hex are the citation's: btcintel:relations:379@v1 sha256:3a0af9a32a1893f8

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.