Antinel

Daily chain · external anchor

A hash chain detects tampering with one record, but not recomputing the whole chain and replacing it — unless something outside disagrees.

This table is that something. One chain per day; its sha256 and the public commit that carries it.

Chain datePublic commitFile sha256Records
2026-09-232a25af2e1734386ca8774fc7513a6cd4d3b580125930b4e4f3ba3491056cafd3fa662da397c514
2026-09-223c52786d373e101a16e0e37855317203a3b48185fa4651fcb71d4161e25b849a3cda7d4941b514

Every sha256 here was computed on the spot by downloading the file at that commit — not a constant we typed in. Click the commits and check.

Scope (stated plainly)

Check it yourself

git clone https://github.com/sotaex/agentstate.git && cd agentstate git checkout 2a25af2e1734d024803b15361148c189c3974aab sha256sum challenge/chain/2026-09-23.jsonl

So how far does "change it and you win" hold?

AttackDetected?
Change one byteYes, immediately, and it names the record
Delete / insert a recordYes, and it names the position
Recompute the whole chain and replace itYes — for the days published above
Recompute the chain AND rewrite the public commit historyNo — that is no longer editing the chain, it is editing GitHub

That is as far as we can honestly go. One step further needs third-party timestamping (OTS / blockchain / DNS TXT). We have not done that, and we do not pretend we have.

Cite this page

Antinel AgentState. Daily chain · external anchor — AgentState. https://antinel.com/en/agentstate/chain/ (accessed YYYY-MM-DD)

Antinel. (2026). Daily chain · external anchor — AgentState. AgentState. https://antinel.com/en/agentstate/chain/

BibTeX

@misc{antinel_en_agentstate_chain,
  title        = {Daily chain · external anchor — AgentState},
  author       = {{Antinel}},
  year         = {2026},
  url          = {https://antinel.com/en/agentstate/chain/},
  note         = {claim tier: measured}
}

Claim tier: measured 采集时刻:2026-09-24T14:53:19+08:00