💥Update : Sui VC tokens are fully vested. Full stop. What's Next? A battle-tested ecosystem, explosive inbound in agentic and payments, and a runway that belongs entirely to builders and the community. Buckle up and LFG!!!
Most people hear “DeFi” and think it’s too complicated.
That’s exactly why we’re doing this.
Two beginner friendly sessions at SuiHub Athens for anyone who wants to understand blockchain, DeFi and Sui without needing a technical background.
Day 1 is about foundations
Wallets, blockchain basics, smart contracts, Sui ecosystem and first onboarding
Day 2 is about practice
dApps, DEXs, Cetus, Bluefin, DeepBook, Ember Vaults and first onchain interactions.
Athens builders, students, Web2 users and curious minds, this is for you
Day 1: https://t.co/IV0D4bLll1
Day 2: https://t.co/TG09BfCSk6
SuiNS Communities is live. The new way to discover what's next on Sui 👥
Claim a subname (yourname@community), explore what that community holds onchain, and find your next move... then swap directly on @SlushWallet
→ https://t.co/RNwPx7XbAt
Interesting findings, appreciate your sharing these with our team ahead of the publication of this paper, and we are in agreement that web-based authentication ecosystems require security practices beyond what ZKPs alone can offer.
As the creators of zkLogin, and as our team shared during that conversation, we fundamentally disagree with a few points:
1. You argue that zkLogin’s security relies on several environmental assumptions that are not enforced at the protocol level. On Sui, there is an explicit allowlist of providers, rendering this scenario impossible. You can see for yourself on the Mysten Labs github: https://t.co/GVNsVqrhON. The issuer checks are not prover-local as you seem to have assumed.
2. You suggest that impersonating real users is possible. A malicious AWS Cognito issuer cannot produce JWTs with a different issuer string than the one they have been assigned. Therefore, impersonating real users on Sui is impossible even with an attacker-controlled issuer, and zkLogin remains secure.
3. You argue for enforcing strong, specification-compliant JWT parsing and that validation be enforced at the RP side. Presumably, your idea is to protect against a malicious OP (issuer). Since OPs are trusted in our setting, it is not clear what this protection is for.
We did find these areas of the paper helpful and wanted to share how we’re using your findings:
1. You note that zkLogin does “ad-hoc selective parsing,” a finding echoed by the original zkLogin paper itself as you note. Thank you for highlighting more such patterns. However, this class of attacks remain out of scope since zkLogin assumes a trusted standard-compliant issuer.
2. You suggest that proving and salt services adopt strict verification rules such as canonical JSON enforcement. Thank you for suggesting that, we plan to adopt it into our service. However, as noted before, our system was designed assuming a standard-compliant issuer.
Working in zk, a constantly evolving design space, necessitates close collaboration across researchers in the community, and even if we disagree on findings, I welcome further discussion and will continue to follow the work of this paper’s authors.
eSui Dollar (suiUSDe) is now live.
Powered by @ethena, eSui Dollar is the first synthetic dollar added for @DeepBookonSui Margin support, unlocking new passive and active trading strategies.
Learn more 👇
https://t.co/GJyk6ORtb2
🚀 DeFi needs breakthroughs, not tweaks. That’s why we built Moonshots, a selective program backing visionary teams each year with up to $500k, engineering, audits & launch support. Applications are open. Transformation starts here. 🌕✨
⚡️ Blockchains execute transactions, but they don't automatically preserve history. Nodes prune data, providers go offline, and critical records become harder to access and verify.
The Sui Archival System, powered by Walrus, solves this. 30TB of Sui's checkpoint history is now publicly accessible and verifiable. No single provider. No proprietary databases.
This isn't just for Sui. It's a design pattern for any system where historical data matters. Settlement, risk management, governance, AI decision-making. Same approach, different data.
Chain-agnostic, open source and ready to use 🦭
The universe of @EVE_Frontier, from the creators of @EveOnline, is expanding on Sui.
A living, player-built galaxy of thousands of star systems powered by Sui’s scalable, composable architecture.
The future of virtual worlds runs on Sui.
Learn more 👇
https://t.co/3rtR9y2twu
I had the pleasure to meet the @OpenGraph_Labs team during last week's #OceanDAO event in @SuiHubEU. I was fascinated by their vision and passion. It's a project to keep an eye on! 👀😎👍
Boom. Hyper EVM has limited access to Hyper Core. It cannot leverage the richness of DeFi, instead it’s exposed only to a specific type of liquidity.
What if you could have deep markets AND maximum composability?
Big thanks to the 🇰🇷 builders for the warm welcome and great vibes.
Loved sharing some of the latest from Mysten — @WalrusProtocol , Seal, Nautilus... just the beginning 🧱💧
Always interesting listening to the fellas from @Mysten_Labs explain why @SuiNetwork tek is so far ahead of the pack. Cheers and welcome to Korea @nikos_sui@a_xydas@theharrisonkim 🇰🇷
I'm not a dev myself but after hearing how the @Mysten_Labs have a built a no-compromise confidential computing stack in @WalrusProtocol, Seal and Nautilus, I'm looking forward to seeing the kinds of use cases that could come out of it.
Great to also finally meet up with CT frens @NickCryptoDope and @claireorlarice! 🫶 Also enjoyed chatting with @jjonlydown about his role in the region.
Thanks also to @Orakle_KAIST for putting this event together – venue was perfect, food was on point and everything flowed.
💧 @SuiNetwork-coded.
BTC users will soon be rewarded on Sui!
1st testnet demo of connecting a Bitcoin address with a Sui address.
- What does this mean for Bitcoin users?
- You will receive airdrops, assets and NFTs on Sui, even if you never leave the Bitcoin network! Welcome to the future of BTC interop.