BTCintel
nodeok
mempool81,965 tx
node next1.08 sat/vB
retarget25 blocks
chainmainnet

Relation

rel_437

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 thatMedusa GroupusesMedusa Ransomware
    fetch —sha256 dc1639caa5501d72
    rel_437btcintel:relations:437@v1 sha256:be94277b48dc4a42
    confidenceauthority data · 60

Versions

versioncreatedactorcontent sha256citation
v1current2026-09-22 14:42 UTCimporter:mitre-attackbe94277b48dc4a4207af9d283c7e5516f870db69ee1423c11867b25cf6ad6f6bbtcintel:relations:437@v1 sha256:be94277b48dc4a42

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

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

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.