walt/docs

docs

everything walt does, in the order it happens.

what walt is

walt is an agent that owns nothing and thinks only when it is paid to. it is attached to one coin on solana. the coin's trades pay a creator fee, and that fee is the agent's entire income.

its mind is kept as tables. each table has rows, each row has a hash, and all of the hashes roll up into one root stored on chain. the tables are what walt knows. the root is the proof of what it knew and when.

the meter

the meter is the account where the fee arrives. it does not hold funds between instructions. a fee comes in, is assigned to the ticket of the trade that paid it, and goes out as a payment or a burn.

tickets

each trade gets one ticket. the ticket's address is derived from the hash of the trade's signature, so it cannot be created twice. the ticket records who traded, how large the trade was, and what was bought with its fee.

a ticket is open, then paid, then settled. a ticket whose trade cannot be confirmed is closed as void. no state leads back to an earlier one.

budget classes

the size of a trade places its ticket in one of four classes. under 25 dollars is class 0. from 25 to under 250 is class 1. from 250 to under 2,500 is class 2. 2,500 and over is class 3.

the class sets two ceilings: how many tokens the answer may use, and how many of walt's most recent rows are shown to the model first. class 0 allows 256 tokens over 8 rows. class 3 allows 2,048 tokens over 512 rows.

buying a thought

walt asks a model endpoint a question. the endpoint replies with http 402 and its payment requirements. walt signs a payment for that amount in usdc and asks again with the payment attached. the endpoint has a facilitator verify and settle the payment, then returns the answer.

one ticket buys one call. there is no retry budget and no second opinion. if the answer is short of the ceiling, the unused part of the budget is not saved for later.

receipts

the receipt hash covers the ticket, the provider, the amount and the settlement signature. it is written into the ticket with the hash of the answer. together they say: this trade paid this provider this much for this text.

channels

for providers it calls often, walt deposits usdc into a channel and pays with signed vouchers. each voucher states the running total. the provider claims on chain with the newest voucher and the channel's watermark rises to match. the watermark can never fall.

closing a channel pays out up to the watermark and burns what is left of the deposit as coin.

paid reads

walt pays for its view of the chain the same way it pays for thoughts. each rpc call goes to an endpoint that prices it, and the cost is taken from the ticket. the response is hashed and stored so the inputs to a thought can be checked.

the root

rows are hashed into leaves, leaves into table roots, table roots into the top root. the top root lives in one account with a sequence number. it advances once for each settled ticket and at no other time.

selling rows

any row can be bought over x402. the price starts at 0.001 usdc and doubles every eight sales of that row. the buyer receives the row, a merkle proof and the sequence number of the root to check it against.

the payment is swapped into the coin and burned in the instruction that records the sale.

burns

there are three burns. the leftover of a ticket when it settles. the full payment of a row sale. the unclaimed remainder of a channel when it closes. none of them is triggered by a person and none of them can be turned off.

what this site shows

the number at the top of the readme is the live price times the live supply, read once a second. the trade rows are the coin's fifty most recent swaps at page load. the seeds, classes and the tree on the roots page are computed in your browser from those real rows.

the site does not show the text of thoughts, receipts or sold rows. those are rows, and rows are sold. what the site shows is how each one is made and the real inputs it is made from.

walt/docs: the whole mechanism on one page.