Record entry · Crypto DEFI

Rune

What is happening now

  • Chainalysis Spots 1 TRX Pattern in $6.4B Binance Hack Laundering Trail

    Reported claim · first reported 30 Oct 2026 · 1 claim · best-carried claim: 2 separate publishers

How well we know this

49 documents · 30 publishers · 0% contain a typed assertion · last evidence 31 Oct 2026

  • Gap: assertion coverage 0: about 100% of mentions carry no typed assertion
Added 1 Nov 2026Mentions 22Sources 10Days of coverage 14

Why this name is on the record

Rune was added automatically on 1 Nov 2026 after 22 mentions across 10 sources over 14 days. 77% of that coverage came from a single subject area.

Reported alongside Rune

Names most often reported alongside it; bigger circles and heavier lines mean more shared documents. A dashed circle has no page of its own yet.

BitcoinAIEthereumThorchainCryptoBitgetTrumpOpenAIAaveAI agents

For developers

GET https://api.signalbureau.ai/api/registry?slug=rune

{
  "slug": "rune",
  "state": "active",
  "detail": {
    "state": "active",
    "source": "ontology",
    "label": "rune",
    "promotedAt": "2026-11-01",
    "category": "crypto_defi",
    "evidence": {
      "mentions": 22,
      "sources": 10,
      "days": 14,
      "concentration": 0.773,
      "standAloneShare": 0.702
    }
  }
}

The record behind this page, as data. The live response also carries the registry date and version.

Walk the record from Rune

Open where it comes from, follow a claim or a related name, and use the trail to come back. Every step says what it is, how it stands and when. Machines read the same record.

Rune

Entity.

Evidence
49 documents · 30 separate publishers · a mention shows the name is in use, not that any claim about it is true
Standing
Added automatically from coverage
Time
first seen 3 Sept 2026, last seen 31 Oct 2026
Measured
0% of mentions say something specific about it; the rest only name it
As of
1 Nov 2026
11 links from here

Who it moves with: the 10 names are in the map above.

What is claimed about it (1)

  • Reported by two: Reported by two sources that did not copy each other.

Situations it is named in (0)

none on file at this cutoff

For machines: this record as JSON

Watch this