TicketwiseSupport that learns your errors.
Paste a user's message with a failed Sui transaction. Ticketwise reads it from the chain through Tatum, explains it in plain words, and answers with what your team taught it. Those lessons live on Walrus, not on our server, so anyone can check them and a wiped server gets them back.
Try it in 30 seconds
- Click "Use a real failed transaction". It pulls a fresh failure from mainnet.
- If nobody has taught Ticketwise that error yet, it says so. Correct it and save.
- Triage it again. The answer now comes from your correction.
Correct it once. It remembers.
Most tickets for a Sui app are the same few contract errors, over and over. Teach Ticketwise what one means, and every later ticket with that error gets the right answer, with your name on it.
It reads the failure
Paste a digest or wallet address. Tatum's Sui gateway returns the abort code, module and function, and Ticketwise names the error from the contract's source.
You correct it once
Say what the error means for users, what to reply and which queue owns it. The correction goes to Walrus Memory with your name and the date.
It answers the next one
The next ticket with that error is answered from your correction. Switch memory off to see the answer without it.
What support learned, inside your editor.
Ticketwise is also an MCP server. Add it to your coding assistant or another agent, and it can triage a ticket or look up what the team taught about an error, from the same Walrus Memory the inbox reads. The engineer fixing the bug sees what support already knows.
Read-only on purpose. Teaching stays in the inbox, behind the team passcode.
226 of 226 later tickets answered from memory.
We pulled 661 real failed transactions from DeepBook v3, Cetus CLMM, Bluefin Spot (CLMM) over 13 days. Corrections were taught from the first 435. The last 226 were then triaged with memory off and on.
Every error in the later set had already shown up earlier. That's what support queues look like: the same errors keep coming back.
Why it needs Tatum and Walrus.
Tatum reads the chain.
Every answer starts from mainnet data: the transaction's status, abort code, module and function, read through Tatum's Sui gateway. Nothing is guessed from the user's description.
Walrus keeps what it learned.
Corrections and escalation rules live in Walrus Memory on Sui mainnet, not on this server. Wipe the search index and it rebuilds from Walrus. The Proof page lists the stored memories and the last check.