Submission notes

How Lo sabía! learns

A desk for markets, games, and culture that files the call before the outcome exists, then changes who it asks next. Built for Total Recall, the Tatum × Walrus Memory hackathon, on the markets and sports track.

Back to the desk

What it does

Lo sabía! is a small room of voices. You, June Park, Mara Voss, and Idris Pell take sides on open tickets. Some tickets are about a game or a market. Two of them are about Sui itself: whether the checkpoint sequence will advance, and whether reference gas will print higher. When a ticket closes, trust moves. The rail reorders. A voice the desk had only been listening to can take the lead, and a voice who keeps missing goes quiet.

The twist is the minority. If everyone leans the same way and one voice disagrees, a correct disagreement counts more than a correct crowd. June starts behind Idris. She is alone on the live checkpoint ticket. If that ticket clears, she passes him. That is the learning loop a judge can see without reading the code.

How it uses Tatum

The tape is not a decoration. Read tape calls Tatum's Sui mainnet gateway at sui-mainnet.gateway.tatum.io with the visitor's own API key, sent as x-api-key and only from the server. One refresh asks for four things: sui_getLatestCheckpointSequenceNumber, sui_getCheckpoint, suix_getReferenceGasPrice, and sui_getTotalTransactionBlocks. If the key also answers the Tatum rate API, the tape shows SUI in USD. If it does not, the epoch still shows, and nothing is faked.

Chain tickets arm against that read. Check on Sui fetches the tape again. A checkpoint ticket stays open until the sequence has moved at least 30. A gas ticket stays open if the price of gas has not moved at all. The outcome is the chain's, not a button labeled "I win."

How it uses Walrus Memory

Seal writes the room to Walrus Memory on Mainnet through the hosted relayer at relayer.memory.walrus.xyz, namespace lo-sabia, using @mysten-incubation/memwal and the delegate key from the Memory dashboard. The first seal is thirteen lines: four trust sentences, eight closed calls, and one room snapshot. That is the ten-memory bar, with the snapshot left over so a browser can be rebuilt.

Trust lines are plain speech the desk can recall: who to amplify, who to quiet, and the record that earned it. The snapshot is the tickets themselves. Recall asks for both, newest first. Forget this browser wipes the local order. Recall puts it back. If you do that after sealing, the product you see is whatever Mainnet still holds, not whatever happened to be in the tab.

Keys never go into a memory. They stay in this browser and are sent only for the call you just made.

How it learned, in one sitting

Idris opens ahead, five of six, because the earlier weeks were kind to him. Mara is quiet. June is close and usually with the crowd, which means her correct calls never counted extra. The live ticket is the first time she is the minority. Waiting a few seconds and checking the checkpoint is enough for Sui to move. She is marked right, Idris is marked wrong, and the sentence at the top of the rail changes its name.

Read the room sends those recalled lines to Grok and asks for two sentences. It is optional, and it is not allowed to invent a record that is not in the memories.

What to ship with the form

Earlier weeks in the room are a starting record so the rail is not flat on first open. They are labeled as earlier weeks. Anything marked tatum was checked against a live read.