
Prime Machin #1151 | Just trying my best to navigate the web3 space
Joined June 2024
- Tweets416
- Following40
- Followers305
- Likes36.9K
Watched the @WalrusProtocol presentation today and it got me thinking.
What the Sui Stack covers today (to my knowledge):
Sui: shared state, ownership and payments, readable through its official GraphQL API.
Walrus: file storage. Public by default, private when encrypted.
zkLogin and passkeys: sign-in with accounts people already have, managed through Enoki.
Seal: encryption and access rules defined in code.
Nautilus: verifiable off-chain compute in secure enclaves.
Walrus Sites: static site hosting.
Walrus Memory: persistent memory for AI agents.
That's a strong foundation!
What it doesn't cover (as far as I know):
- App-specific search and queries, beyond what the general API offers
- Push and email to an app's users when something happens on-chain
- Scheduled jobs, since contracts only run when someone calls them
- Everyday backend tasks like sending email or calling outside services
- Fast-changing data like counts and likes, without a transaction for each
- Private app data that's as easy to work with as a table with access rules
- Card payments for people new to crypto
- Logs, monitoring and costs in one view
- Code hosting and deploys, the way GitHub and Vercel handle them
Most of these are solved by third parties today, just outside the stack.
What I keep wondering about is one console that ties it all together. The Sui Stack pieces and the missing ones, in one place. Host my code, turn on sign-in, set up data and storage with privacy where it's needed, add backend logic and scheduled jobs, deploy the frontend, get alerts, see costs. And eventually a path to phones, with help getting apps into the App Store, Google Play or other channels.
One stop, from first commit to an app in people's pockets and on their computers.
I think that's what would make mainstream building on Sui really boom.
Curious whether something like this is on the roadmap, @Mysten_Labs @WalrusProtocol?
Okay now where talking!
@WalrusProtocol making huge step into making Walrus more easy to navigate and to build on, with more easy to understand interfaces and plugins for builders.
This is a giant leap in making Walrus a better place to store data, and have programmable data.
walrus.xyz/
walrus.xyz/products/walrus-m…
walrus.xyz/products/walrus-c…
Bullish for @DeepBookonSui and bullish for @SuiNetwork. Like they say, it’s going to be way easier for banks to make this move than to build onchain infrastructure for themselves.
This way they save themselves the technological development, which reduces risk, and they keep the distribution and frontend and customerbase for themselves, which means they don’t lose «face».
They can now adopt onchain finance without overhauling their business.
This quoted post is unavailable.
Last bull @DeepBookonSui was only touched through other frontends. This time around it will also have its own direct application introducing predict and margin. And, it will also be the onchain liquidity layer for institutional flow via Havenex.
Welcome new DEEP bull.
I don’t think we are talking about @DeepBookonSui enough. I think it’s sort of overlooked atm.
Yes it’s coming out with an app soon which will give retail a more direct use of deepbook, and yes margins and predict.
But, @HavenexHQ … that is what I’m currently focusing on, further down the line.
@kostascrypto and @EmanAbio have mentioned Havenex will use Deepbook for when it comes to onchain operations. And Havenex is not a retail CEX. They are positioning themselves toward institutional money, like funds, familiy offices, and banks.
The interesting part: Havenex opens up a new type of flow easier than before. Because now traditional banks wont have to totally flip their operations and infrastructure upside down to adopt onchain finance, they can do the easier route and adopt Havenex as their bridge into onchain, to serve stablecoins, crypto and more to their customers, while still maintaining custody and security.
Think about it, they don’t have to reinvent the wheel, they don’t have to completely restructure their infrastructure from within, they don’t have to become experts, they simply own the distribution, the top layer, the added value. Its reduced their adoption painpoints substantially.
This goes DEEP.
