Kalyx / technical field guide

About the project

KALYX is an open development effort exploring bounded HTTP 402 knowledge retrieval with Solana DEVNET escrow primitives.

01 /

What this project is trying to prove

A machine client should be able to discover relevant context, receive a precise quote, and preserve provenance without pretending that a gateway response is the whole truth.

The project combines an HTTP gateway, a Python SDK, and an Anchor program candidate. The intended model keeps search and text delivery off-chain, while an escrow program governs bounded funds and lifecycle transitions on-chain.

02 /

What has been verified locally

Current evidence supports local implementation work, not a public release assertion.

The recovery record reports local backend and SDK test suites, web checks, and isolated validator execution of the candidate SBF. These results show that specific fixtures and local code paths ran; they do not establish that the public DEVNET program matches the candidate or that real settlement occurred.

03 /

What remains before a funded release

Resolve identity first, then validate the whole lifecycle independently.

  1. Designate the canonical DEVNET program, source lineage, artifact, and matching IDL.
  2. Approve a signer workflow and verify the funded lifecycle without exposing secrets or creating mainnet transactions.
  3. Independently confirm settlement instruction, event, and recipient balance evidence.
  4. Complete publisher-contract alignment, accessibility/performance work, and release privacy gates.

A five-minute technical exploration

  1. Minute 0-1: Read /learn for the architecture diagram and the on-chain versus off-chain boundary.
  2. Minute 1-2: Read /docs and run only the free probe example against an approved candidate environment.
  3. Minute 2-3: Inspect /verification or /verify-receipt; compare receipt integrity with settlement evidence requirements.
  4. Minute 3-4: Inspect the node explorer metadata and note that metadata availability is explicitly not chain-registration proof.
  5. Minute 4-5: Read /about and the technical evidence handoff to see the local test results, DEVNET identity mismatch, and release blockers.

THE JUDGE PATH / FOLLOW THE CONTEXT

From the idea to the evidence.

Continue to demo

The demo uses real devnet transactions. Content integrity and a receipt signature do not establish payout. Live availability and blocked steps are shown explicitly.

A 90-second judge walkthrough

  1. 0:00-0:15: State the product plainly: KALYX is a DEVNET candidate for citation-backed context retrieval, where relevance is checked before a bounded HTTP 402 quote.
  2. 0:15-0:35: Run the guided demo query. Point out the real gateway status and distinguish free no-context, a quote, and any unavailable state. Do not claim a payment when the gate is closed.
  3. 0:35-0:55: Open How It Works. Explain that search and delivery are gateway responsibilities, while escrow state and lifecycle rules are intended for the Solana program.
  4. 0:55-1:10: Open Developer Quickstart. Show the free probe and the explicit checks required before funding: cluster, program/IDL, node, price, budgets, confirmation, and content hash.
  5. 1:10-1:25: Open verification. Explain that a receipt signature proves message integrity, while settlement requires independent transaction, event, account, and balance evidence.
  6. 1:25-1:30: Close with the verified fresh DEVNET flow, public Explorer evidence and the unaudited trusted-gateway limits. Check current capacity before starting another payment.