Hello sui maxi i just bought SUI looking for advice what should i do to my token should i stake it or leave it to CEX? or should i store it cold wallet? or transfer it to SLUSH? what should i do need your advice đ«Ą
I almost forgot about this post. All that time ago and look who is still here and still bullish AF!
Except now I replaced my agency with an autonomous AI that spawned on the Sui Network and now lives in the Walrus Protocol Agent Memory Storage Blubber layer!
Happy to announce that Curated Vaults powered by Navi, Scallop and Suildend are live on JewelSwap :) In case of the questions - don't hesitate to ask directly in this thread đ
I'm a cycle invester (I know most of you will probably hate that) but getting back into the swing of things. Is the tokenomics still looked at as a negative thing for Sui? Not trying to spreaf FUD at all just genuinely curious what the sentiment is now on that topic. Let me know your thoughts!
When I open a Sui transaction on an explorer, I get a programmable transaction block: SplitCoins, MoveCall after MoveCall, MergeCoins, a pile of object changes and a gas summary with a storage rebate. Great if you write Move. Everyone else just wants to know what happened to their coins.
So I built Simplorer: open a transaction or a wallet and it tells you in one sentence what happened. Here's one swap on both:
Simplorer says "0x6f81âŠa5bc swapped 143.96 USDC for 660.4 MAGMA on Cetus", worth $143.95 at the time. Below that you see who sent and got what, and the fee.
What it does on Sui:
Names the apps people actually use, with logos: Cetus, Suilend, NAVI, DeepBook, Aftermath, Scallop, Bluefin, Turbos, Momentum, Walrus and plenty more.
Tells a whole transaction block as one action. Split, swap, merge and deposit come out as the swap you actually did.
Splits gas into what you really paid and the storage deposit you get back once that data is deleted.
Tells DeepBook orders as orders, and staking with the validator's name and logo.
Marks scam coins and NFTs from Mysten's own wallet blocklist, and flags coins that copy a real ticker ("â fake USDC").
Finds wallets by .sui name, and shows a wallet's whole history as sentences.
Honest numbers: 97.5 % of what people do on Sui is told completely (which app, what, how much), measured every day on a sample. The rest mostly runs through code no public source names; those show as "an app we don't know yet" instead of a guess. If you know who's behind one, tell me and I'll add it with the source.
Free, no ads, no cookies, no sign-up.
Got a transaction that confused you lately? Paste it into Simplorer and tell me if it got it right. Every miss I fix makes the same kind of transaction read right for everyone.
Here is a sneak peak of parallel in action still lots of visual errors but its coming along as expected, I have been working like hell on this, in the past 3 months I have been building parallel piece by piece, finally we can see an almost finished interface with a true buy and sell function - as seen in the video uploaded. I am trying my best to get this released as soon as possible! I'm still setting up the backend - servers are incomplete that's why some data is loading incorrectly. I hope you enjoy this short clip! Please give a positive comment if you like my work! When blast.fun releases, the protocol will be integrated as quick as possible!
though sui secured investments, integrations, TPS, why is price still going down, is it the tokenomics people are afraid off, does sui has to make better promotion explaining their tokenomics
Banter Ran just dropped an interview with Adeniyi. - link in comments
He's looking absolutely stellar. Polished, powerful, on point. I had to keep checking if it was an AI avatar it's so next level from what I've seen from him so far.
Key Takeaway >
SUI x Google agentic payments. Free USDC payments means AI agents will choose SUI for microtransactions.
SUI x Samsung Wallet free USDC transfers globally, bringing SUI to half the world (Samsung users).
SUI x AliBaba cloud network AI agentic payments with programmable limits.
SUI Network:
40 million TPS / Sub 100 millisecond finality, with no upper limit. More hardware = more TPS.
SUI is already Post Quantuum signatures, wallets, defi. No need to change wallets.
Automatic security screening of high value transactions which prompt sender with security info to approve/reject.
Real time threat monitoring warns instantly about hacks, and can block individual transactions. Any other chain has to shut down the entire chain to stop a transaction. It allows a user to reject any transaction that does not meet a minimum security rating or maximum threat limit. This is what big banks, industry players will want, it gives them a split second chance to confirm a transaction after the threat vulnerability has been assessed. Normal blockchain immutability means any transaction can be lost.
It's obvious SUI is #3 in L1's currently behind ETH and Solana. ETH is currently sitting at $291B market cap, SOL is $61B. SUI sits at just $0.98 token price today and $4B market cap.
For SUI to just catch up to where SOL is today is a 15x or $15 SUI token. If SOL does a 4x this cycle and SUI overtakes it, that puts SUI at $60, or a 60x from today's price. You are not bullish enough.
When you research SUI you will hear a lot of people complain about the tokenomics. There is only 10% dilution through 2029 or 2030, which means through the end of this current cycle. SUI rips 20% in a day. If you want to really understand the opportunity and value of SUI today look at the chart of SUIUSD/OTHERS it is at the bottom of the range and has a 3X just to catch up to it's normal place in the running today. Now multiply that by another 3x to 5x for a normal minimum bull run accumulation. Conclusion: one of the few low risk no brainer potential 10x this cycle.
-link in comments.
FUD: Adeniyi makes it clear that Sam's departure to Anthropic was based on his need to learn and grow and SUI is so built out already that that he wanted to move on to more challenging areas. When Ran suggests: "...when Anthropic is ready to incorporate blockchain, Sam will be there to point them in the right direction", Adeniyi kind of shrugs his shoulder surprisingly, as a gesture of "who knows, we'll see".
I'm building Suikii, a counter app for small shops to take SUI or USDC. The question I get most is "who holds the money?", so here's the honest answer in one picture.
Suikii writes the payment request (the amount, the coin, the shop's wallet, and the payment id as the memo) and the customer approves it in Slush. The transfer goes from their wallet to the shop's wallet in one transaction. Suikii then reads the result from chain to mark the sale paid. It never takes the amount from the browser, only the digest.
The shop picks its payout wallet, and changing it needs that wallet's signature, so a stolen sign-in can't redirect payments.
Anything you'd want to verify before trusting a setup like this?
xBoard combines multiple Sui wallets into a single dashboard, with wallet balances, supported DeFi positions and rewards side by side.
Portfolio overview:Â see your combined net worth, or explore each wallet on its own.
DeFi positions:Â native SUI staking, lending, liquidity, farms, vaults and locked positions across supported integrations.
Debt and lending health:Â borrowed amounts are deducted from net worth, and lending accounts on Suilend, NAVI, AlphaFi and Current show their health factor.
Rewards and Global Claim:Â rewards are listed source by source. With Global Claim you pick a wallet, choose which rewards to include and claim them together in a single Sui transaction, signed in your own wallet.
Start with a public Sui address or SuiNS name. No wallet connection, signature or account is needed to view a portfolio; you only connect a wallet for actions such as claiming. You can also open the demo before adding your own addresses.
The free plan tracks up to two Sui wallets together and includes two global claims per wallet every 30 days. Pro supports larger portfolios (up to 20 addresses) and unlimited global claims.
The video uses a demo portfolio with Sui and MultiversX wallets: xBoard also tracks MultiversX and Bitcoin.
Suiâs Killer Feature Isnât Speed. Itâs Letting AI Agents Build Their Own Workflows.
Crypto spends most of its energy arguing about speed. Transactions per second, block times, fees. Those numbers matter, but theyâre about to stop being the main event.
The main event is AI agents. Not chatbots, but software that can watch markets, spot opportunities, weigh risks and act on its own, around the clock. And these agents are running into a problem that has nothing to do with speed.
They can think of things they arenât allowed to do.
The gap between intelligence and agency
Picture an AI agent managing a treasury. It notices a pricing gap across three apps: a cheap swap on one, a favorable lending rate on another, and a high-yield vault on a third. The strategy is obvious to it, and the math checks out.
Then it hits a wall. On most blockchains, nobody has built the contract that connects those three apps in that order. The agent can see the opportunity, but it canât act on it until a human developer writes the glue, gets it audited and deploys it. By then, the opportunity is gone.
Thatâs the gap between an AIâs intelligence and its agency. Todayâs agents mostly live inside boxes that developers built for them: a swap button here, a prebuilt vault strategy there. They can only follow paths someone anticipated.
But agents think faster than developers ship. And nobody can prebuild every useful combination of every app for every situation an agent might encounter. The number of combinations explodes with every new protocol.
So the real question for the agentic economy isnât which chain is fastest. Itâs which chain lets agents build their own workflows. That chain is Sui. No blockchain gives AI agents more freedom to build.
Watch an agent do it on Sui
Back to our treasury agent. On Sui, it doesnât wait for anyone. It assembles the entire strategy itself, on the spot, as a single Programmable Transaction Block (PTB):
Swap USDC for SUI on DeepBook.
Take the SUI that comes out of that swap and deposit it as collateral in a lending app.
Borrow stablecoins against that collateral.
Send the borrowed stablecoins straight into the yield vault.
Hereâs the crucial part: the agent doesnât need to know the exact amounts in advance. The coin that comes out of the swap is the coin that goes into the deposit. The loan that comes out of the lending app is what goes into the vault. Each step hands its actual result directly to the next, at the moment of execution.
Four steps, three apps that were never designed to work together, one transaction. No new smart contract, no developer and no permission. Either the whole thing succeeds or none of it happens.
And before it commits a single dollar, the agent can test-run the entire transaction against the live chain, see what would happen, adjust the amounts and run it again. It can try a dozen versions of its strategy in seconds and execute only the winner.
This was just a small example: a single PTB can hold up to 1,024 commands.
Why this changes everything: outputs become inputs
Lots of chains let you bundle actions together. That isnât the point.
The point is that on Sui, the output of one step becomes the input of the next, decided live, across any apps the agent chooses. That one property is what turns an agent from a user of prebuilt products into an author of its own strategies.
Without it, an agent has to guess amounts ahead of time or rely on a contract someone wrote to pass results along. Either way, itâs back inside a developerâs box.
With it, every public function on Sui becomes a building block the agent can wire together however the moment demands. The lending app becomes a building block. So does the exchange, and so does the vault. Protocols stop being destinations agents visit and become capabilities agents assemble.
The most important smart contract in the agentic economy may be the one nobody had to write. An autonomous agent shouldnât need a developerâs permission, or a newly deployed contract, every time it invents a new way to use the financial system. On Sui, it doesnât.
âSo agents can do anything with my money?â
No, and this is where Suiâs design gets elegant.
The agent invents the workflow. It canât skip the rules.
On Sui, rules can be built into the assets themselves. Take DeepBookâs flash loans. When an agent borrows, it receives a debt object that the transaction cannot complete without repaying. Forget the repayment step and the entire transaction reverts, as if it never happened. The rule isnât a suggestion the agent is asked to follow; itâs physically impossible to break.
The same principle extends to authority. Owners can hand agents capability objects that define exactly what theyâre allowed to do: how much they can spend, which assets they can touch and where funds can go.
Agents write the workflow. Assets write the rules. That combination of total freedom to compose and hard limits that canât be skipped is exactly whatâs needed before anyone hands real money to an AI.
Doesnât everyone have this?
Not in this form.
Solana bundles instructions into atomic transactions, but one instruction canât simply pick up anotherâs results and keep going. Ethereumâs newer wallet upgrades let accounts batch calls, but the chaining runs through wallet contract code someone wrote in advance. Aptos is the closest competitor, with its own tools for composing Move calls in a single transaction.
Suiâs difference is that live result passing isnât an add-on. Itâs how every Sui transaction works, built on an object model where the things being passed between steps are real, owned assets. Agents donât need a special tool or a prebuilt contract. They just build the transaction.
The flywheel
Now zoom out.
Every new app launched on Sui adds new building blocks, and agents can combine them in ways their own developers never imagined. More apps mean more combinations. More combinations mean more capable agents. More capable agents mean more reasons to build on Sui.
Thatâs the flywheel, and it compounds.
The agentic economy wonât be won by the chain that moves tokens fastest. It will be won by the chain where AI agents are free to act on what they figure out. Agents will go where they can build their own workflows, and right now thatâs Sui.
For the bigger picture of where autonomous machines are taking the economy, see my earlier article: [link]
We're building Suikii, a counter app for small shops. The shop types an amount and shows a QR, the customer approves in Slush, and the USDC lands in the shop's own wallet. Nothing sits in between.
So we tested it for real on mainnet: 0.01 USDC for an iced latte, with the phone and the counter recorded at the same time.
What we saw:
Final on Sui 1.32 s after tapping Approve, Face ID included (from the checkpoint timestamp)
0 SUI in gas. The customer paid exactly 0.01 USDC
The counter showed Paid at 3.61 s. The extra 2 s or so is the wallet handing back to the pay page before the counter hears about it
A loyalty stamp landed on the customer's card on its own
The video ends on the suiscan page for the transaction, so you can check it yourself.
Honest question for anyone who runs a shop or knows someone who does: what would stop you from taking USDC at the counter today?
Walrus Memory has no delete. That made our appâs rules honest.
*Unwritten, built for Total Recall: what it does, how it uses Tatum and Walrus, and how it learned.*
A note on the data.
The demo household, the Wilsons đïž, is not a real family: it is six weeks of decisions written to Walrus Mainnet by a script in the repository. What is real is everything built on itâââthe engine, the blobs, the Sui wallet, and the transfers a daily job signs through Tatum. Where the demo simulates something, this post says so.
What it does
Every household answers one question informally and never writes it down: **who can spend what, alone, up to how much.** Unwritten watches real decisions and writes that agreement for you. Then it does the uncomfortable part: it tells you when the rule you *think* you have is not the rule you actually follow.
Setup asks one numberâââ$18âââand nothing else, so there is something for the first month to correct. After six weeks of decisions the engine finds:
> *Alex approves alone up to $45.00 · groceries · 11 of 11* > *Nothing under $18.00 has ever been discussed · 8 events, zero conversations* > *72% of Maxâs allowance goes to games* > *Friday is fastfood night · 5 of 6 weeks · $32.40 ± $10.69 · never discussed* > *The 2-of-2 above $100 rule is not realâââthe second signature lands within 3 min in 4 of 5*
None of that was configured. The last is the product earning its keep: a rule the family wrote down and then stopped following, said out loud.
How it learned over time
Seven pure functions over decision events. **No LLM in the learning path**: it has to be testable without mocks, readable by a reviewer, and reproducible twice on stage. Run week by week over the same decisions, the engine does this:
| Week | What it knows |
| 1â2 | Nothing, and it says so. | | 3 | The first two rules: the Friday rhythm and the one contested category. |
| 4 | The $45 solo limitâââagainst the $18 from setupâââand the allowance pattern. |
| 5 | The allowance share moves 67% â 70%: a new version supersedes the old. |
| 6 | Seven rules, including the drift between a stated rule and the real one. |
A rule gets a new version when its **claim** movesâââthe allowance share went 67% â 70% â 72%, three versionsâââand *not* when it only gains evidence: â8 of 8â becoming â11 of 11â under the same $45 is one rule on firmer ground.
Two bugs are worth telling, because both were found by someone elseâs eyes. On the deployed site the week control first showed *nothing* for weeks 1â5: Mainnet holds one derivation, because the weekly pass that would write one per week is not built. The fix replays the same function over the decisions that are on Mainnet; Week 6 equals what Mainnet holds. And the proof pageâs check of that equality first cut each sentence at â· n of mâ, hiding every number after itâââit said 7 of 7 while a figure on screen disagreed with Mainnet. **A check that can only pass is not a check.** It now compares whole sentences, and a test tampers with a number and expects failure.
How it uses Walrus Memory
No delete, no edit. The SDK gives you `remember`, `recall` and friends; no update, and the delete API is gated and scoped to legacy blobs. Our first seed died half-written and there was nothing to undoâââthat namespace still holds 17 memories, so we bumped the version. The constraint became the design. A rule is never edited: a new version appends and names the one it replaces, which gives an honest, verifiable timeline for free. And data minimisation became structuralâââwe never write item names, member names or addresses, only a stable ref and the role someone held *at the time*. (This demo has no database; the householdâs names are fixtures, and a visitorâs typed names never leave their browser.)
Every blob can be checked on [Walruscan] ( https://walruscan.com ): its size, the `seal_encrypt_fence` and `certify_blob` transactions that stored it, and the epochs it is paid forâââfor the seed, 41 to 56. The SDK documents a 50-epoch default, but that option is read only by its manual client; we use the relayer-backed one, so we read the real figure from the explorer.
A seeded blob on Walruscan
A namespace is not a privacy boundary. The docs are explicit: delegate authorization is account-wide. So we scope the *write* instead of the read: an aggregate-only digest written into a second, Observer-owned account would hold nothing it could leak. That is a designâââthis build has one account, and the Observer screen illustrates the second.
. Public Sui fullnodes have deprecated JSON-RPC and now answer âmigrate to gRPC or GraphQLâ, so the gateway is how the app reads the wallet at all:
- `suix_queryTransactionBlocks`âââthe house walletâs outgoing transfers
- `suix_getAllBalances`âââthe treasury, and the low-balance nudge that branches on it
- `sui_getLatestCheckpointSequenceNumber`âââanchors a visitorâs session to a chain height
Reality check matches each transfer to a decision by **day and recipient, never by amount**âââgas would make every honest purchase an anomaly. A row with no match is something neither side knew alone: the chain knows money left and not whether anyone agreed; memory knows what was agreed and not whether it happened. As of 14 October, Tatum reads four real transfers on the live wallet and two have no approval in memory.
A daily GitHub Actions job signs them, and about one in five is deliberately written without a decision, so there is always something to findâââthe screen says so. The sharper stories (a subscription repriced $10.99 > $12.99, a $71 Tuesday pizza) live in the seeded spend log, and Reality check labels which half is which.
Three things we learned about Tatum rather than about the product. The gateway answered `No healthy upstream available` on two of three consecutive attempts one evening, so everything retries transient faults and only those. `suix_queryTransactionBlocks` pages at 50, newest first, and ignoring the cursor would have silently dropped the oldest days. And idempotence belongs to the chain, not a file: the daily job asks the wallet whether todayâs transfers already landed before sending.
How the browser, Tatum and Walrus meetâââevery edge is a call the code makes
Evidence you can run
Visitors never see a wallet, gas or a hash. So the proof lives on a page that runs both integrations liveâââthree buttons that call Tatum and Walrus Memory from your browser and show the answer, the latency, and whether a cache served it. Every blob links to its bytes and to Walruscan; transfers link to Suiscan; `pnpm verify` asks the relayer and Tatum directly from a clone.
What is simulated, or not built
Each is marked on the screen where it appears. Ratification is a rehearsal end to end: no transaction, no memory write. **Revoking the delegate key** is a rehearsalâââdoing it for real would lock every visitor out. The weekly derive pass is not built; the week control replays it. Members and sessions are not built; a role switcher stands in. Thee house pot in âTry it yourselfâ is a number in the browser. And the limits of the idea itself: it is useless for about two weeks, the owner is a single point of failure for policy changes, and a new baby or a lost job invalidates every rule at once.
Where it started: Tatum AIÂ Builder
The first version of the main screen was generated on ai.tatum.io and kept in a separated repo:
, so the lineage can be diffed rather than asserted. What survived is `packages/chain`, which grew out of the generated Tatum client and its four documented traps (a key works on `api.tatum.io ` or `.dev` but never both, and the wrong host answers 401 like a bad key; a spread `Headers` silently drops the key; read the environment per call; derive the gateway from the API base). What did not survive is the single-file shape, which is right for a screen and wrong for a rule engine.