Keryx

Demo

About

Keryx turns a question and a USDC budget into an inspectable research job. Its agent discovers sources, explains BUY/SKIP/CACHE decisions, buys selected content through x402, and produces a cited answer. Creators receive weighted USDC rewards for cited contributions that pass the evidence checks. For ETHOnline, we extended an existing research engine with a buyer workspace and an independent buyer client. Buyers can inspect package pricing, prepare requests, follow jobs, review source decisions and quotations, and recover an existing purchase after losing a response. The client checks the recipient, network, asset and spending limit, records durable recovery state, and verifies portable receipts against the request and returned result. The workspace distinguishes a completed job from a sufficiently supported answer. It exposes quality limits, settled and pending creator amounts, and unused creator reserve. Packages are prepaid and fixed-price; unused reserve is not an automatic refund. This is not an on-chain escrow marketplace with evaluator-triggered release or refunds. Keryx is a Continuity Track project. The research engine, payment rails, registry and durable server jobs existed before the event. Event work includes buyer checkout and recovery, evidence-quality improvements, creator controls and operational hardening. Our demonstrations use owner-operated Arc Testnet pilots; we do not claim independent customer adoption or mainnet readiness. Pre-event baseline: 5e83d45 (September 2). Dated event log: https://github.com/tang-vu/keryx/blob/main/docs/ethonline-2026.md

How it's made

The app uses Next.js, React and TypeScript, with a SQLite database on the production VPS and a Supabase/PostgreSQL adapter available behind the same database interface. A durable asynchronous worker runs the research pipeline. Model-assisted planning and synthesis are combined with source decisions, quotation checks, explicit evidence coverage and bounded payment allocation. Arc Testnet is the deployed EVM network and USDC is the payment unit. The Solidity SourceRegistry records source ownership and payout configuration. viem connects application and wallet actions to Arc; Hardhat tests the contracts locally. Circle Gateway and the x402 batching tools connect paid source access and citation rewards to USDC payment flows. Cached content can avoid a new access toll while still earning a reward when cited. Our event work focuses on the buyer boundary: checking payment challenges against pinned terms, journaling before a purchase, retaining uncertain states after a lost response, and resuming the original job instead of buying again. Browser recovery uses durable local storage and cross-tab coordination. Portable receipt verification binds the saved request to the returned answer and payment ledger; it does not independently prove blockchain finality. Paid pilots exposed question-interpretation and receipt-projection defects, which drove targeted fixes and regression tests. Later work added creator authority checks, funding-recovery safeguards and incremental archive reads to reduce transient memory use. Vitest, Chromium checks, TypeScript, contract tests and production checks support the implementation. A revision-checked registry V2 is a separate tested candidate, not a deployed replacement. The public continuity log identifies the pre-event baseline and event changes.