←
Neil Han1,632 posts
Neil Han avatar

Neil Han

@NeilHANYD

Guest lecturer at NTU FinTech; ex-Twilio, PingCAP, SK

◷ Joined September 2010▧ 336 Photos and videos
Neil Han avatar
Neil Han@NeilHANYD·Sep 28

Mastering Blockchain Scalability - now on Amazon in all three formats. Born as the textbook for my NTU blockchain course. Rollups, DA, parallel execution, consensus - via Arbitrum, ZKsync, Celestia, Solana, Sui. Amazon: amazon.com/dp/B0HL6PVH2S

Neil Han avatar
Neil Han@NeilHANYD·Sep 25

It grew from my blockchain-infrastructure work and SC6019 teaching context at NTU. It is an independent open work, not an institutional endorsement.

Neil Han avatar
Neil Han@NeilHANYD·Sep 25

The book includes worked calculations, explicit assumptions, graduate exercises and solution sketches, threat-model worksheets, a practitioner evaluation handbook, and a benchmark-reporting template.

Neil Han avatar
Neil Han@NeilHANYD·Sep 25

Consensus throughput is not execution throughput. Ordering, execution, data propagation, quorum formation, and finality impose different costs. A design can move one bottleneck while leaving the system bound somewhere else.

Neil Han avatar
Neil Han@NeilHANYD·Sep 25

Parallel execution does not remove shared-state bottlenecks. Independent transactions scale differently from workloads fighting over hot accounts, contracts, queues, or markets. Benchmarks should report the conflict distribution, not only peak throughput.

Neil Han avatar
Neil Han@NeilHANYD·Sep 25

Data availability is not archival storage. A system can prove that data was available at a decision point without promising that every historical byte remains served forever. The distinction changes both architecture and recovery.

Neil Han avatar
Neil Han@NeilHANYD·Sep 25

Rollups are not one security model. Ask who sequences, where data goes, who proves, what the bridge verifies, how upgrades work, whether forced inclusion exists, and what users can do when the normal path stops.

Neil Han avatar
Neil Han@NeilHANYD·Sep 25

The book follows transactions end to end: submission → ordering → execution → data → proof/dispute → settlement → recovery. That same path is used to compare L1s, L2s, channels, rollups, modular systems, and bridges.

Neil Han avatar
Neil Han@NeilHANYD·Sep 25

A TPS result is incomplete unless you know: * workload and hardware * state and contention * data publication * verification cost * finality rule * trust assumptions * failure and recovery path

Neil Han avatar
Neil Han@NeilHANYD·12 Sep 2025

Meanwhile, we’re exploring new ways to boost adoption via GEO and infra designed for Vibe coding. The goal is to make crypto-native payments just faster, more accessible for developers and businesses. This is just the beginning and I’m excited to share more with you all soon. 🚀

Neil Han avatar
Neil Han@NeilHANYD·10 Aug 2025

Logically speaking, true innovation is often an idea most people doubt or dismiss — yet it inevitably happens and drives society forward~

Post attachment
Neil Han avatar
Neil Han@NeilHANYD·19 Jul 2025

AI agent verticals are growing like crazy — even single DB usage is skyrocketing. But only those with the right GTM will capture the wave 😏 Otherwise, you’re just watching from the sidelines.

Post attachment