Repository navigation
v0.1.0-preview.8
Pre-releasepreview.8: plain abalone takes a pasted gift link and redeems after an 8-character consent; abalone credit forget; one session per credit; credit inspect writes nothing; provider keys move from node keys to abalone key; experimental direct Chutes route for abalone sandbox; source tree reorganised (new trial.json).
This release needs its own trial.json: the trial still pins 33 source files, but some of them changed or moved, so a bundle assembled for preview.7.1 or earlier is refused by this runtime. The issuer, signed approval and issuer-pin.json are the same as preview.7.1.
What a friend sees first:
- Plain
abaloneat a terminal, with no ready credit, asks for the gift. Paste the fullhttps://amiller.github.io/abalone/redeem#code=…link, the bare code, or a path starting with/,~/,./or../to a 0600 file holding it. The input is not echoed. Anything else is refused by name. Further lines of a multi-line paste are discarded, so they cannot answer a prompt or reach Pi. - It then prints the same offer as
abalone credit inspectand asks you to type the first 8 characters of its offer hash. Typing them redeems that offer and opens the session in the same run. Anything else stops with nothing claimed and nothing written to disk. Input typed ahead of the consent prompt is discarded. - Plain
abaloneuses thetrial.jsonthatinstall.sh --creditsaved beside the runtime;abalone --trial /ABS/trial.jsonselects another. Without a terminal it prints the step-by-stepcredit inspect/credit redeemcommands and exits with status 2. With one ready credit it still opens it, and with several it still lists them. - An interrupted redemption ends with the recover message and the exact
abalone credit recover --credit <id>command. abalone credit forget --credit <id>removes a saved credit and its lock file. It is refused while a session is using the credit, and for a credit whose claim may be in progress unless--forceis given (runcredit recoverfirst; the saved keys are the only way to finish that claim). Forgetting does not revoke the credential: only the sponsor or the issuer's operator can, and Abalone has no revocation request yet.- One session at a time uses a credit. A credit session holds the credit's lock until it closes, and usage is written under that lock.
- The installer now says that plain
abaloneat a terminal takes the gift link, before the step-by-stepcredit inspectline.
Security-relevant behaviour changes:
abalone credit inspectwrites nothing: no record, lock or temp file. The gift code and Noise seed stay in memory.abalone credit redeemcreates~/.abalone/credit/<id>.json(mode 0600) with the gift code and Noise seed before it sends the first claim, socredit recovercan finish an interrupted redeem. A wrong offer hash or a locally lapsed claim window is refused before any file is written.credit recoveron an unknown id creates no lock file. In preview.7.1, inspect wrote the record and a lock file.- What each mode keeps on this computer is now listed in docs/security.md ("Local host and retention"). For
abaloneandabalone credit session: Pi runs with--no-session, so the conversation exists only in process memory. Pi's settings, crash and debug logs, harness state and scratch go to a tmpfs run directory,/dev/shm/abalone-<uid>/run-*. The launcher removes it on a normal exit, an error, or SIGTERM/SIGHUP; the empty 0700 parent stays. After SIGKILL or a native crash the run directory stays in/dev/shmuntil the next session starts, which now removes run directories whose launcher no longer holds the lock on theiralivefile, or until reboot. Tools run as your account with your realHOME. - The saved credit record holds the gift code, Noise seed and recovery key, then the delivered model credential and its envelope, then reported token usage. It survives close.
<id>is the SHA-256 of the gift code. Abalone does not verify what the model provider retains. - A fresh session is not deletion. The administrator and same-user processes can read all of the above while it exists; tmpfs may swap; workspace files, terminal scrollback, host names in
~/.abalone/egress.jsonl, backups and copied files have their own lifetimes; deleting a file is not secure erasure. - Provider keys moved out of
node keys.abalone node keys add|list|use|rmand~/.abalone/node/keys.jsonare gone.abalone key add <provider> [--label <l>] [--input-file /abs/0600-file]reads the key from hidden standard input or a 0600 file; a key given as an argument is refused and not echoed. The key is checked with one authenticated call that carries no prompt, then saved as a 0600 record in the credit store.abalone key listnever prints the key or its last four characters.abalone key forget <provider> [--label <l>]removes it.abalone sandboxuses the provider's most recently added key; plainabaloneandabalone credit sessiondo not use configured keys. - Migration for keys: keys in an existing
~/.abalone/node/keys.jsonare not read. Re-add them withabalone key add <provider>, then delete the old file.ABALONE_DEV_NODEis renamedABALONE_PROVIDER_KEYS. abalone node serve|relayis renamedabalone peer serve|relay, with the same code; its default ledger directory moves from<STATE>/nodeto<STATE>/peer.- The coupon v1–v3 client modules are deleted. The live
/dsmack/coupon/4path keeps every offer check; the client refuses v1, v2 and v3 coupons.abalone coupon-sessionwithout--attestednow refuses with "No coupon was read or sent".
Layout change:
curated/→agents/pi/, withcurated/manifest.json→agents/pi/admitted.jsonpi/→vendor/pi/,aci/→vendor/phala-aci/anchors/nearai_mainnet.json→verifiers/near/,anchors/chutes_measurements.json→verifiers/chutes/,anchors/apple-app-attestation-root.pem→lib/contracts/→plugins/coupon/contracts/evals/→skills/evals/<name>/, beside the skills but outside the admitted skill trees, so the skill hashes do not change; the shared runners (llm.py,bin/near, README) →tools/eval/
providers.json and policy.json stay at the root; only the paths inside them change. The trial still pins 33 source files in the same order: 9 are renamed and 9 have new bytes.
If you set ABALONE_CONFIG, move your manifest: $ABALONE_CONFIG/curated/manifest.json → $ABALONE_CONFIG/agents/pi/admitted.json.
The Pages site (site/ and its workflow) moved off main to an orphan pages branch. tools/release.sh now requires --site-template FILE (friend.html from that branch).
New dependency: @noble/post-quantum 0.5.4, for ML-KEM-768 in the Chutes route. It was already in the lockfile through age-encryption; it is now a direct, exact-pinned dependency. HKDF, ChaCha20-Poly1305 and gzip come from node:crypto and node:zlib.
Chutes route (experimental, abalone sandbox only, needs your own Chutes key):
abalone key add chutes then abalone sandbox --model chutes/<model>. Before any prompt byte leaves, the client verifies the Chutes instance it will send to: a fresh TDX quote checked against Intel PCS with TCB UpToDate, report_data binding our nonce to the instance's ML-KEM key and its evidence certificate, MRTD and RTMR0-3 matching a row of a reviewed snapshot of Chutes' own unsigned measurements list, and NVIDIA NRAS GPU evidence with its signature checked. The whole request, tools included, is sealed to that instance's key; the reply comes back unstreamed, as one sealed message. A failed instance is not cached; the next listed instance is tried once, then the request is refused.
What it does not establish: the instance id is Chutes' label, not attested (the quote binds the key, not the id). The chute's serving code that reads the decrypted prompt is not measured, and nothing binds which model answers. The measurement anchor is a copy of Chutes' unsigned feed, and a newer image is refused until the anchor is refreshed by review. Chutes' API sees the account, model, instance, request and reply sizes, and timing. The live suite (tests/chutes.sh) was not run on this head; Chutes remains experimental, and the instance id is Chutes' label.
Not in this release:
- A mode for an unverified provider key.
- Zcash payment for a coupon.
- Plain
abaloneusing configured provider keys (#21); onlyabalone sandboxuses them.
install.sh --credit claims nothing. It verifies abalone-ca6a250.tar.gz and the four public inputs (trial.json, issuer-pin.json, staging-approval.json, readiness.json) against the hashes pinned in the installer, saves them, and says that plain abalone at a terminal takes the gift link. Check the downloads with FRIEND-SHA256SUMS.
The issuer is the same Mac mini recipient-v1 epoch as preview.7.1 (Apple App Attest identity, operator/KMS-readable custody, same signed approval) with a $1.00 total cap, a Base mainnet guard at 0x3f614a51c8badc67f5d340933b9471aa2008cc16, and an approval that expires 2026-10-18T18:00:00Z. This is a Linux x86_64 Node 24 trusted owned host debug trial with synthetic prompts only, explicit verified OutOfDate warnings, and no VPN requirement. Production privacy, local OS tool isolation, issuer private custody and rollback protection remain unqualified.
The client and source archives correspond to commit ca6a250. That commit passed the full offline gate (54 suites) and an independent review of the preview.8 changes; the built package passed a full-byte source/package comparison with 25 reviewed node-gyp build files allowlisted by exact hash.
install.sh SHA256: a80cf10e48bfb0215827ab96cd746277396f8c19fa222ae9985b0da55b10c37b. The signed approval expires 2026-10-18T18:00:00Z. Each gift carries its own claim-by time, at most seven days after it was minted and about eleven minutes before the approval expires; abalone credit inspect shows it.
Known gaps (each rated Low or Info in review):
- Chutes: a request that arrives while another is verifying the first listed instance shares that verification; if it fails, the second request is refused instead of trying the next instance. A retry works.
- NEAR: an unknown
modelTcbpolicy is refused only after the gateway quote is checked, not before; nothing is sent either way. - The stale run-dir sweep refuses every owned-host launch, with a raw errno message, if a
run-*entry in/dev/shm/abalone-<uid>is not a plain directory with a plainalivefile. Remove the entry by hand. - Run-dir liveness follows the launcher, not Pi: after
kill -9of the launcher, an orphaned Pi keeps running and the next session removes its run directory. It has no credential broker, so nothing leaks. - Run directories without an
alivefile (from earlier releases, or a launcher killed during setup) are never swept; they go at reboot. - The agent's read capability covers
skills/**(lib/caps.mjs:23), which now includes the eval gold answers inskills/evals/. Sandbox bash could already read them; the attestation eval hides them while it runs. abalone key listprints nothing when no key is configured.- A credit saved under preview.7.1 has not been tested under preview.8.
- coupon-no-replay passes in the offline gate but fails 4 of 9 tests in laptop worktrees with symlinked dependencies.
- The tools/install.sh.in header does not document the
--peermode that the installer still accepts. - The parser checks
<arg_NAME>names against the operation but not<arg_key>names: an extra name is ignored, and<arg_key>op</arg_key>renames the operation, which the model can do by naming it directly anyway.