.Sui has a massive headstart and the most flexible architecture for the post-quantum and AI era. This conversation with Kostas Kryptos tells you exactly why, and what every other chain still has to figure out. If you hold anything onchain, watch this pod. Timestamps: 0:00 Intro 6:00 What a... quantum computer actually is (the 10-year-old version) 10:00 Quantum will be used for trading before it ever breaks Bitcoin? 13:00 Post-quantum algorithms (solved) vs hardware (decades out) 17:00 "If you think quantum breaks crypto by 2030, you can make free money" 19:00 Everyone missed this: AI is now researching quantum alongside humans 25:00 The post-quantum-algorithm debate: Falcon, Dilithium, Sphincs and why each chain picks differently 27:00 Why Bitcoin will ONLY adopt hash-based post-quantum algorithms 31:00 This is why Sui's architecture wins: 128KB transactions, native multi-sig, flexible authenticator 36:00 How Sui can natively support any signature scheme 40:00 The Sui-only algorithm: protect existing EdDSA addresses without moving a coin 44:00 Design philosophy: what Sui kept from Libra, and what it threw out 47:00 Why Sui can keep gas low even with post-quantum signatures 49:00 How Kostas first started working on this in 2016 at R3 Corda 51:00 Attending tech conference one day after his son was born: meeting Sam Blackshear , joining Libra 55:00 The bigger near-term threat: AI-aided attacks, not quantum 58:00 Why Mysten Labs is now sharing its security tooling with the community 1:02:00 Sui's $100K post-quantum bounty: break it, keep itshow more

@SuiNetwork @kostascrypto They need to see that SUI also knows how to do memes that don't rugpull like the one I am simply obsessed. 🌐 Explore SuiDex: 💥 Check out: CA: 0xdeb831e796f16f8257681c0d5d4108fa94333060300b2459133a96631bf470b8::suitrump::SUITRUMP

On @Sui, a Coin<SUI> isn’t a balance entry in a contract mapping. It’s a literal object with a unique ID, an owner field, and type-enforced ownership semantics at the Move language level. Two Coin<SUI> objects with the same value are still distinct objects. You can wrap them, split them, merge them, freeze them, share them. They have identity in a way Ethereum balances genuinely don’t. The object model isn’t just a different storage layout, it’s a different ontology of what an on-chain asset is. on account-based chains, assets are positions in a ledger and the “object” framing is a category error. On Sui, assets are actually objects in a meaningful sense, where the object is a data structure with identity, owner, and type-enforced behavior, maintained by the validator set as canonical state. They’re still not physical, and they still exist only as state of a public computation, but they’re objects in the computer science sense, which is much closer to how lawyers think about property than how Ethereum models balances. This is actually a feature for the institutional thesis, not a problem with it. TradFi’s entire conceptual model of asset ownership is object-based: this share certificate, this bond, this title. The account/balance model that Ethereum imported from banking is the abstraction layer on top of underlying object-like instruments, but the underlying instruments were always things with identity. Sui’s object model maps more cleanly to legal ownership semantics than Ethereum’s balance model does, which is one of the structural reasons Sui ends up being a better substrate for tokenized real-world assets than account-based chains. Lawyers can reason about Move objects in a way they can’t reason about ERC-20 entries.

so, bigger transactions let #Sui include larger proofs, signatures, or metadata in a single on-chain action. That means developers do not need to split complex post-quantum, privacy, or AI workflows across many transactions, making apps easier to use and easier to combine with other on-chain actions 💪🏼

@SuiNetwork @kostascrypto And the design choice or the origin of the architectural choices makes this possible was made in 2018. that's crazy

@SuiNetwork @kostascrypto This is simply not true. Algorand $ALGO FTW 🙌

Algorand is great but with a max tx size of like 1,000 bytes, its gonna struggle super hard in a post-quantum world Yeah it uses Falcon signatures right now cause they actually fit at around 666 bytes, but it completely locks them out of better NIST standards like Dilithium or SPHINCS+ which need thousands of bytes just for one single signature This is pretty big bottleneck imo

@SuiNetwork @kostascrypto Thanks for chiming in !! Algorand has upgraded block parameters before and can do so again through governance if needed for bigger signatures or higher throughput. Algorand has the brightest minds in the space !! Rest assured that everything will be optimized. 🤝 $ALGO 🌎🇺🇸⚡️

sure, they can vote to raise the block size, but bigger txn limits mean nodes have to process way more bloated data. That completely tanks performance and pumps up hardware costs, which destroys the whole point of being fast and decentralized Also the brightest minds can't compress a 40,000-byte SPHINCS+ signature into a 1,000-byte limit without breaking the protocol or forcing devs into absolute workaround hell. Optimization can only do so much before you run straight into a brick wall.

@SuiNetwork @kostascrypto We are both acknowledging the same thing here. There are tradeoffs with everything, especially Quantum Resistance. The Algorand team is uniquely well suited to solve all of these problems. Exciting times ahead !!

@SuiNetwork @kostascrypto 🫡

@SuiNetwork @kostascrypto 🤝

@SuiNetwork @kostascrypto Tx size limit of @solana is increasing this year. That largely removes the previous bottleneck for PQC.

@SuiNetwork @kostascrypto @solana still you cannot implement hash-based post-quantum algorithms without significantly degrading latency and throughput

@SuiNetwork @kostascrypto @solana Sure, that's the same for all blockchains when it comes to hash-based signatures.

no true. sui can absorb heavy hash-based post-quantum signatures without crushing network performance (max txn size 128 KB /131,072 bytes). Bitcoin is def going hashbased. Sui can easily absorb that. plus because of the way sui derives addresses, it can seamlessly absorb new post-quantum algorithms without needing a hard fork or breaking existing wallet infrastructure (cryptographically agile design). currently, the network natively recognizes several classical flags (0x00: ed255190x01: secp256k1 (bitcoin/ethereum curve) 0x02: secp256r1 (passkeys/apple secure enclave) 0x03: Multisig) adding post-quantum signatures is trivial @kostascrypto says this on record in the pod

@SuiNetwork @kostascrypto @solana Sure, it will be some work, but Solana can also add versioned addresses.

@SuiNetwork @kostascrypto @solana still not par with what sui can do. The way it is now. its an inferior design and will stay that way for the foreseeable future