@MetacampDAO and @WPReadingClub led an engaging and fruitful discussion about use cases and inner workings of real-time blockchains including @megaeth_labs and @magicblock! 🥳 #singapore #blockchain #web3 #ethereum #solana #education #community #metacamp #whitepaperreadingclub

🚀 30 hours. Rust. Web3. Mastered. 🦀 We just wrapped our #Rust bootcamp w/ @KshitijWeb3 — and students went from zero to building #Solana programs in four days (not months). Next cohort at @metacampDAO 👉 #Web3Dev #SolanaDev #RustLang #Blockchain

🔥 Wrapped up a powerful session with the @MetacampDAO Web3 community in Singapore! We explored blockchain use cases from stablecoins to real-world tokenization, and shared insights on the future of Web3. The energy to build is real. 🌐🚀 #Web3 #Blockchain #Singapore

🔥 Wrapped up a powerful session with the @MetacampDAO Web3 community in Singapore! We explored blockchain use cases from stablecoins to real-world tokenization, and shared insights on the future of Web3. The energy to build is real. 🌐🚀 #Web3 #Blockchain #Singapore

We finished a 3 hours Whitepaper Reading on AlpenGlow (@anza_xyz ) Notes: (1) Turbine now optional—Rotor handles block relay, simpler but maybe easier to censor (2) relay nodes become incentive-driven (3) certificate signatures cut on-chain bytes, not network traffic (4) Solana’s scaling lever is lower latency; slots fixed at 400 ms (5) PoH clock removed—400 ms leader timeout enforces ordering (6) protocol favors quick cancellations over inclusions, possibly boosting resubmits. Questions: (1) What are the key trade-offs in rolling out Alpenglow? Is it censorship resistance? (2) How are certificates created and verified? (3) How exactly does Alpenglow replace PoH for ordering? (4) As relays are a new middle men, can they direct-message txs to validators they trust and create a fork? Does that create censorship? Any pointers would be great @TheWattenhofer @DiscoKobi @qkniep @brenn @bw_solana