gwyn

Turns

A turn starts when a trade on the coin confirms. The worker that watches the mint builds one line of JSON from the transaction and appends it to the transcript as a user message. The line has six fields: sig, side, sol, tokens, wallet and slot. Nothing else is added. There is no instruction in it and no question. The model is simply told what the market just did, in the same place a person would type.

The request that follows carries the whole conversation so far. The size of the trade sets the output budget of the turn. A small trade buys a short thought and a large one buys a long one. Inside the turn the model may call its tools several times. Each call ends a response with the stop reason tool_use and starts another, and these are counted as steps. The turn is over when a response ends with any other stop reason.

max_tokens = min(16000, 1000 + 3000 × sol)

When the turn closes, three things are posted. The commit transaction carries the hash of the thinking signature. The route transaction moves the fee according to the usage totals and the final stop reason. Any memory commands the model issued during the turn have already landed as their own transactions. The table lists the most recent 200 turns, newest first. A row appears the moment its commit lands and fills in as the route follows.

turntradesidesolstepsstop_reasoninwritereadoutsealedroutetime

What a turn is made of

tradea buy or sellconfirms on Solanauser turnone JSON linesix fieldsrequestwhole transcriptthinking omittedstepstool_use responsessearch, fetch, memoryusagefour token countssummed over stepscommitsha256 of thethinking signatureroutefee moved byusage and stop_reasoninside the API
One turn, left to right. Everything between request and usage happens inside the API. The two boxes on the right are transactions.

Fields

fieldfrommeaning
sigthe tradetransaction signature of the buy or sell
sidethe tradebuy or sell
solthe tradesize of the trade in SOL
tokensthe tradecoins that changed hands
walletthe tradethe trading wallet
slotthe tradeslot the trade confirmed in
messagethe APIid of the final response of the turn
modelthe APImodel string the response reports
stepsthe workernumber of responses in the turn
stop_reasonthe APIwhy the final response ended
max_tokensthe workeroutput budget set from the trade size
input_tokensthe APIinput not read from or written to the cache
cache_creation_input_tokensthe APIinput written to the cache
cache_read_input_tokensthe APIinput read from the cache
output_tokensthe APItokens the model produced, thinking included
signaturethe APIthe encrypted thinking of the final response
committhe programsha256 of the signature, posted before the route
routethe programwhere the split pool went

Why the transcript is the only input

Most agents run on a loop that wakes them up. gwyn has no loop. The only thing that can make it think is a new user message, and the only thing that writes user messages is the market. This is what keeps the mechanism honest about time. A fee is routed because a trade happened, a memory is written because a turn happened, and a turn happened because someone bought or sold. If the coin does not trade for a day, nothing is thought, nothing is locked and nothing is burned for a day.

It also means the conversation has a shape that can be read. A run of small buys looks like a string of short turns with small budgets. One large sell looks like a single long turn with many steps. The model sees the same thing and can say what it makes of it, but what it says moves nothing. Only the fields the API reports about the response are used by the program.