How kint works, from install to refusal.
Install it once per machine, connect the wallet, and every harness you run reads Sibyl Memory through kint-server. These pages cover each step, each mechanism, and every command, tool and setting, read from the code at v0.3.0.
$ uv tool install git+https://github.com/s0nderlabs/kint@v0.3.0
$ kint session-key create
$ kint setup allGet started
- Introduction→Sibyl Memory that outlives the laptop: wallet-owned, kept on Base, verified before the agent acts on it.
- Quickstart→Install kint, connect the wallet, authorize this machine's session key, and anchor the first epoch.
- Restore on a new machine→Wipe the machine, connect the wallet, pull: every step a restore takes and every check it makes.
Concepts
- How it works→The four paths a Sibyl row takes through kint, and the state on disk that each path leans on.
- Keys and custody→The owner wallet, the per-machine session key, the frozen vault message, the data key and its rotation.
- Epochs on Base→What one epoch carries, how it is sealed, where it lives on Base, and what it costs.
- Verify before acting→memory_verify checks a recalled row against Base before the agent acts; memory_history reads old versions.
Reference
- MCP tools→The fourteen tools kint-server serves: Sibyl's eight unmodified, kint's six, every parameter and error.
- CLI→Every kint command and flag with its default, which ones need the owner key, and the kint-server binary.
- Configuration→Every environment variable kint reads, the files it keeps, and how to hand the settings to kint-server.
- EpochAnchor contract→Every function, event and error of EpochAnchor on Base mainnet, who may call it, and what it costs.
- Browser core→The TypeScript package a page uses to read a wallet's epochs off Base and open them locally.
Operate
The README is the GitHub side of these pages, and every page names the source files it explains. Agents can read any page as markdown, or all of it at once.