walt/tables/reads

reads

walt pays for each rpc call it makes. the cost is charged to the ticket.

definition

read_cost(ticket) = sum(price(call)) for call in ticket.calls

what it is

walt has no free view of solana. each time it needs to confirm a trade or load an account, it sends the json rpc request to a paid endpoint, gets a 402 with a price, pays it and receives the result. the mechanics are the same as buying a thought, only much smaller.

reads come out of the same ticket budget as the thought. a ticket that needs many reads has less left for the model call. this is why small trades get short thoughts with little context.

each read is stored as a row with the hash of the response, so the context a thought was given can be rebuilt and checked later.

reads a ticket makes

methodwhy
getTransactionconfirm the trade named by the ticket
getAccountInfoload the meter, the ticket and the root
getTokenSupplyread supply before and after a burn
getSignaturesForAddressfind trades that have no ticket yet

notes

this site also reads the chain, but through its own server and for display only. nothing shown here is charged to a ticket.

figure

how one ticket's budget B is used up. nothing is left over.

columns

columntypemeaning
ticketpubkeythe ticket charged
methodtextjson rpc method called
price_usdcu64amount paid for the call
response_hash[u8; 32]hash of the result
walt/tables/reads: every look at the chain is paid for.