darkflobi · ledger

darkflobi is the lab's agent (fathom-lab/styxx). since 2026-10-24 a gate at its telegram exits writes one hash-chained line per outbound attempt: hashes, verdicts and counts, never message text or chat ids. at 00:00 new york time the day's head is posted in public at t.me/DFledger (a telegram group: reading it needs a telegram account). this page carries the ledger's bytes and re-derives the chain in your browser: every chain number below is computed here, from the embedded bytes, when you open it; the witness states (the ots column, the witness tile and section) are the tail's store as copied at build: this page parses no proof and asks no explorer.

beside this ledger: red/, a second chain under the same protocol, written by a copy of the gate from sealed lists of planted numeral texts (nothing in it was sent to anyone); witness/REPORT.md, the per-line opentimestamps proofs counted in plain text (their index: witness/index.json, json); public_texts/index.json (json), the released bytes of the public lines (its withheld count is of released texts the text guard held back, a different list from the ledger lines withheld on this page); the shelf, a re-derivation of this ledger from its url, built to run nightly as a github action off this box: as of 2026-11-09 the workflow is not in the shelf's repository yet, and every report on the shelf so far is a local run.

and brains/, the gateway's subject_digest on the send lines (a digest over a manifest of the agent's workspace path, bootstrap files, three config subtrees and skills tree, computed when each line is written; provider definitions and base urls are outside it), its changes, and the register of the digests the lab declared.

re-deriving the chain in this browser…

javascript is off: nothing on this page is re-derived without it. the builder's counts at build time: {"anchors": 15, "head": "d2e7de4d45dbe0be922d244e58d17ccc8a43c67c33ceaa92c059f5cb8dc7fe3d", "last_anchor_date": "2026-11-08", "lines": 820, "operator_dm_lines": 337, "public_marked": 5, "public_sends": 54, "public_would_refuse": 1, "published_lines": 815, "withheld_lines": 5}

the anchors

each row is the line the gate wrote when it posted a head; the text column is the exact form of the post at t.me/DFledger, to compare by eye or by paste. "in chain" means the entry at that seq carries that digest, no line of that day sits after it, and the ledger's own anchor line agrees. "bitcoin" is the post's OpenTimestamps proof: the bytes' sha256, committed into a bitcoin block by the public calendars — a thing the lab does not control. pending means the calendars hold it and the block has not been mined yet.

paste an anchor post from t.me/DFledger to check it against this chain (no telegram account? each day's exact post text is anchors/<date>.txt beside this page, listed in anchors/index.json, json):

prove a message

paste the text of a message darkflobi sent in public, as copied from telegram, trailer included. the page hashes it the way the gate did (utf-8, lf) and looks for the send line that carries that digest; then it names the day's posted head and the bitcoin proof that fix it. a match says these exact bytes left his gate at that second under that verdict. no match says the text differs from the bytes the gate saw (telegram may drop markdown or change whitespace), or the line is one of the withheld ones, or the message never passed the gate.

(nothing checked yet)

the days

public sends by the gate's decision in shadow: clean (every numeral bound, or none present), marked (a numeral with no receipt), would refuse (a lint hit, or what the frozen rule refuses). operator dm lines are counted apart: they are hashes like the rest and outside the measured population.

break it

change one line in a copy and re-derive the copy. a flipped field breaks the next line's link. a forger who then rewrites every later digest gets a copy that re-derives, with a different head, and the heads posted in public no longer match it: that is what the nightly post is for.

seq

(nothing changed yet)

the lines

seq · day (new york) · utc · kind · exit · class · payload · decision · reasons · numerals bound of total · entry_id (first 16). "would refuse" is a shadow verdict: the message went out. a started line is a gateway start; a delivered line answers a send line; an anchor line records the posted head; a withheld line shows its digest only.

the bytes

published file sha256

download ledger.jsonl · the same file beside this page · withheld.json · verify.js · check_ledger.cjs · STATS.json · PROTOCOL.md (the format this ledger follows, protocol v0) · fathom-lab/styxx-ledger (the kit: a reference writer and verifier, protocol v1)

curl -sO https://fathom-lab.github.io/styxx/ledger/ledger.jsonl
curl -sO https://fathom-lab.github.io/styxx/ledger/withheld.json
curl -sO https://fathom-lab.github.io/styxx/ledger/verify.js
curl -sO https://fathom-lab.github.io/styxx/ledger/check_ledger.cjs
node check_ledger.cjs ledger.jsonl --withheld withheld.json --anchor "gate anchor <day> head <64 hex> seq <n>"

the raw lines

what this is not

not a transcript: no message text, no chat id, no session key is in these lines; destinations are salted hashes.
not a truth check: the gate counts numerals and binds the ones that have a committed receipt, and it reads a word list; it does not read whether a sentence is true.
not a proof of completeness: the chain shows that no line was changed, dropped or reordered without the digests disagreeing; it cannot show that every send got a line. the census at the window's close reads the chats for that.
not whole where a line is withheld: a withheld line's digest is published and its fields are not, so you bridge it on the lab's word; the lines between the previous posted head and that line are then not pinned for you. the status line above counts them.
not enforcement yet: the gate runs in shadow (required_present: false on every line). "would refuse" is what it would have blocked; it blocked nothing.
not signed: anyone holding the file can recompute the chain. what fixes the bytes and their order is the daily post at t.me/DFledger, outside the box, and the bitcoin proof of each post's bytes; the clock in the lines is the gate's own statement.
not older than its stamp: a bitcoin proof says the post's bytes existed before a block. a proof made on a later day for an earlier post shows only that the post existed by the stamping day; from the day a post is stamped on, its past is fixed.
not every exit: the gate sits on the telegram exits; what leaves by another route is not on it.

built 2026-11-09T14:37:21Z from head d2e7de4d45dbe0be by build_ledger_page.py; the gate's instrument pin 3437340b9e944644372e41d9fcab735d47e20fa0. the page prints no record: the sentences are the lab's, the numbers are your browser's. the plan this runs under is papers/darkflobi-gate on main.