Hanko exit_liquidity

hanko

Hanko turns crypto market chatter into a sized position, or an honest refusal, with the evidence attached, and can prove that same decision byte for byte, years later.

Point it at a token and the voices you trust, on X, Telegram or Bluesky. It reads what each one actually said, checks whether they're independent voices or one thesis repeated three times, and decides:

ENTER TOKENA  size 3.28%  confidence 0.66

• independent_voices: 2 independent voice(s): voice_alpha, voice_gamma ~ echo voice_beta: marked as a repost or quote by the source ! wrong if price_usd < 1.0625 at any point within 72.0h (thesis fails if price falls 15% from entry) review at 2026-08-30T12:00:00Z

Sample output: real engine, synthetic inputs. voice_alpha/voice_beta/voice_gamma and TOKENA are fictional test fixtures. None of them is a real account or token.

Run that same input again in a year and it produces the identical decision id, because nothing about deciding touches the network, a clock, or a model. It only ever reads what was actually stored. That is the whole project: "prove it" is a command you can run.

Judging? Start at [/judges](https://tryhanko.xyz/judges): every line of the published rubric, mapped to a page or command you can check yourself. [tryhanko.xyz](https://tryhanko.xyz) has the pitch and a sample receipt (synthetic inputs, labelled). [/try](https://tryhanko.xyz/try) runs a piece of it, live, from your browser, no install. Full technical detail is at /docs.

---

RYO-CHAN Hackathon 2026 submission, three tracks. Track 1 (Autonomous Agents) is the agent above, built to the Multi-KOL Narrative Agent spotlight. Track 3 (New Skills) is exit_liquidity: what it costs to get *out* of a position, from an executable venue quote where one exists, in RYO's own response envelope. It is also the size gate the agent runs before committing. Track 2 (Dashboards & Interfaces) is three screens: the workbench, the failure drill and the Echo Index.

What it has shown, live

• A ledger that grows every three hours, with no key. A scheduled workflow reads public Telegram, Bluesky and news voices on BTC, ETH, SOL and BONK, decides, seals the run with its replay bundle, stamps it on OpenTimestamps and commits it to live/. Every decision is graded 72 hours later against the conditions it wrote down first. /ledger shows what changed since the last run, most important first (D-20).
• Graded against its own conditions, including when it was wrong. The first 32 scheduled decisions came due on 2026-10-27 and 28: every ENTER held (7 of 7, realised returns between -0.9% and +1.1%), and 7 of 25 refusals were proved wrong because a voice they said would flip them arrived. Those reviews also exposed two grading bugs, fixed in D-21.
• A sealed live ENTER that anyone can re-derive. BTC, 2026-10-23, runs/run_836b976720f63dc0.json. The manifest lists every watchlist entry, including the PASS and both ABSTAINs. It is anchored in Bitcoin block 972,817, mined 35 minutes after the seal, and hanko verify-run replays all four decisions from the committed bundle with no network and no key. (Until 2026-10-24 that bundle was not actually in the repository; D-19.)
• A measured exit cost. BONK, $50,000: the Jupiter quote says 2.3%. The skill's own constant-product model said 7.2%, and the report prints the 3.1x gap.
• A study that audited the agent. The Echo Index ran Hanko's echo check over 2,094 real posts from 15 crypto channels. Echo inflation was 1.005x, published as found. First, though, it found that Hanko's own detector missed verbatim copies padded with an ad or a footer (D-14, fixed).
• Nine failures injected on purpose. RYO down, every source down, a rate-limited quote venue, the model down, a prompt injection the model actually obeyed, tampered evidence, an edited sealed run, a source dying mid-sweep, a restart. All nine hold, computed live on /drill. The restart scenario broke the first time it ran (D-18, fixed).

A 判子 is the seal a person stamps on a document to commit to it. The mark goes on before the outcome is known and can't be taken back, which is exactly what this agent does with every decision it makes: sizes it, commits to it, and states in advance what would prove it wrong.

Submission

• [Project Submission Form](RYOCHAN-Project-Submission-Form.pdf) (PDF, this repo)
• [Demo video](https://youtu.be/fm0B4hZQCwQ)
• [Announcement post on X](https://x.com/IamHarrie/status/2096908693967179844?s=20)

Contents

• Verify it yourself in 60 seconds
• Who this is for
• Explore without running anything
• The one rule
• Layout
• Why it is built this way
• Use
• Status
• exit_liquidity, the new Track 3 skill
• Decision records
• The review loop
• The sweep
• Architecture, decisions, limitations

Verify it yourself in 60 seconds

No live credential, no account, no network. Every number below regenerates from synthetic fixtures committed in this repository (fictional sample voices and a fictional token, written for testing):

git clone https://github.com/IamHarrie-Labs/hanko && cd hanko

pip install -e ".[dev]"

pytest # 349 tests, offline, ~20s

make a decision, then prove it replays from stored bytes

hanko decide x --token TOKENA --subject voice_alpha --subject voice_beta \ --subject voice_gamma --market fixtures/market_tokena.json \ --as-of 2026-08-27T12:00:00Z --fixture fixtures/x_three_voices.json hanko audit # re-derives it, insists it reproduces

the Track 3 skill, against the same fixture, no network

hanko exit-liquidity TOKENA --size 50000 --market fixtures/market_tokena.json

the first live ENTER, re-derived from its committed bundle

hanko verify-run runs/run_836b976720f63dc0.json

break it on purpose: nine failure scenarios, offline

python -c "from hanko.drill import run; print([r['held'] for r in run()])"

re-derive every number in the Echo Index

hanko echo-index publish

Who this is for

Builders and traders who want an agent's reasoning to be auditable rather than taken on faith. Someone who has been burned by a bot that says "strong buy signal" with nothing behind it, and wants to see the evidence, the falsifiers, and the honest gaps instead. Also the judges reviewing this submission, who can replay any decision from the exact stored bytes it saw.

Not built for anyone who wants the agent to execute trades. It doesn't, and by the hackathon's own rules, none of the RYO tools it's built on can either. Everything here researches and sizes a position; nothing here moves funds.

Explore without running anything

/try , live against the real platform /docs , the full technical writeup

The one rule

fetch()  touches the network, is allowed to fail, and is never deterministic

parse() touches nothing, and is a pure function of its payload

The agent only ever sees the output of parse(). Because parse() is pure and payloads are content-addressed, any past decision can be re-derived from stored bytes and must reach the same verdict. Put a network call inside parse() and the reasoning trail stops being reproducible, and that property is what the whole submission rests on.

Layout

hanko/provenance.py      canonical JSON, sha256 addressing, Status, Coverage

hanko/evidence.py Evidence + Provenance: the source-agnostic unit hanko/sources/base.py the adapter contract hanko/sources/xsearch.py X, via the xAI Responses API and its x_search tool hanko/sources/rss.py RSS/Atom: free, and the only source with trustworthy timestamps hanko/sources/fixture.py local JSON: free development, and every failure mode in CI hanko/snapshot/store.py append-only content-addressed store, replay, integrity hanko/ryotools/ the six RYO tools over MCP and REST; structural fact extraction hanko/skills/exit_liquidity/ Track 3: what it costs to exit a position hanko/review/outcome.py grading a decision against its own commitment hanko/review/reliability.py calibration, per-voice and per-rule track records hanko/review/ledger.py append-only reviews, one per decision hanko/cli.py collect / decide / review / scorecard / audit / verify

Full tree:

hanko/

sources/ X, RSS, fixtures -- fetch() impure, parse() pure snapshot/ append-only content-addressed store ryotools/ the six RYO tools, MCP + REST decision/ evidence quality, verdicts, falsifiers, the ledger review/ falsifier checking, calibration, reliability skills/exit_liquidity/ Track 3: exit cost, capacity, drift, turnover sweep.py, cli.py, config.py, provenance.py, evidence.py site/ static landing page, /docs, /try -- the live web demo api/exit_liquidity.py the /try endpoint, real assess() call, no fixture tests/ 349 tests, one file per hanko/ package fixtures/ evidence and market fixtures used offline and in CI .github/workflows/ci.yml pytest on every push,