rel_377

The claim

• MITRE ATT&CK Enterpriserecords thatFIN5usesFLIPSIDE

  fetch —sha256 dc1639caa5501d72

  rel_377btcintel:relations:377@v1 sha256:40e17b4be9052379copy citation
  confidenceauthority data · 60

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/rel_377?version=1" | grep -i etag
# ETag: "40e17b4be905237986428dd4a49d3c00ff6e131d8b5436dd4b816064113b22d8"

curl -s "https://api.btcintel.io/v1/claims/rel_377?version=1" | jq -r .content_sha256
# 40e17b4be905237986428dd4a49d3c00ff6e131d8b5436dd4b816064113b22d8
# the first 16 hex are the citation's: btcintel:relations:377@v1 sha256:40e17b4be9052379

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.