Loading video...

Video Failed to Load

Go Home

Many people don’t fully appreciate what an incredible achievement it is to code an entire parallelized EVM blockchain client from scratch and just how challenging that task is. Imagine writing code that will secure billions of dollars in liquidity once Monad mainnet goes live with zero room for design...

17,369 views • 1 year ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

HTML Artifacts are a big part of how I work with agents now. Artifacts can be more than just static files. When combined with agents, they can take action or help you take action. This unlocks all kinds of interesting ways to work with agents. This is clearly the future. Check out this writing and scheduler artifact I built in a few minutes. It uses a bit of HTML and JS. All the data is in markdown (Obsidian vaults), so the agent can access and modify it at any time. No DB needed. No sophisticated functionalities. The agent decides all that for me based on the skills, context, and memory it has access to. The best part about this simple stack is that all the important information stays with me. This has allowed me to build a recursive self-improving system and automations that can better tap into coding agents like Codex or Claude Code. I could have paid or built an entire app for scheduling posts, and there are so many of them out there. But I don't need to. I've realized a simple artifact does the job. And the simplicity of it is actually an advantage. Very little maintenance for very high returns on personalization, time, and efficiency. The other benefit of this is that I can add features as I please. That level of personalization feels magical, and we should all be pursuing more of it. All of this just keeps compounding. Of course, this example is just about writing. But I have similar artifacts for research, design, experimentation, evaluation, and so much more. And no, I didn't actually publish the post example I shared in the clip. It was just for demonstration purposes. I actually spend more time than this when writing together with agents. Lastly, having built my own agent orchestrator tool has made me realize that simplifying the tool stack is a superpower. If you are curious about how all this works, I will do a live session next week:

elvis

18,374 views • 4 months ago

Say hello to Boojum 👋: zkSync Era’s new high-performance proof system for radical decentralization. Boojum is an upgrade that will transition zkSync Era to a STARK-powered proof system, providing world-class performance on consumer-grade hardware. 💡 Learn more: TL;DR 👇 Boojum is the name of our Rust-based cryptographic library, which we use to implement the upgraded version of the ZK circuits for zkSync Era and the ZK Stack. The name Boojum was inspired by Lewis Carroll's poem "The Hunting of the Snark," where the Boojum represents the most fearsome kind of Snark. We intentionally designed zkSync Era in a way that cryptographic upgrades can be made without a regenesis, meaning that the Boojum upgrade won’t cause any user disruptions. Why Boojum❓ From day one, zkSync’s mission is to advance personal freedom for all — making digital self-ownership universally accessible by building a blockchain network that is trustless, secure, permissionless, affordable, easy to use, resilient and limitlessly scalable. Boojum plays an important role in advancing this mission by delivering: 1. World-class performance zkSync Era’s current SNARK-based proof system is effective today, but it won’t scale to the volume that we envision for hyperchains. zkSync Era’s sequencer can already process over 100 TPS; Boojum orders of magnitude improvements to performance complements this well. 2. Reduced hardware requirements for decentralization Our long-term goal is to enable user-powered, decentralized proof generation. Boojum represents a breakthrough in this direction — with the prover running on consumer-grade GPUs requiring only 16 GB GPU RAM. Boojum’s Journey to Mainnet 🚴🏽‍♀️ Boojum is now live on Mainnet, generating and verifying ‘shadow proofs’ today with real production data so that we can carefully test the system ahead of fully migrating. Today, we’re also open-sourcing the repo; if you’d like to take a look, you can find it here 👇 This is the first of a series of posts on Boojum. We will provide updates on our progress, including more details on implementation, security, and performance. Watch here for more, anon ∎

ZKsync

828,309 views • 3 years ago

What Actually is Sei Network's “Giga” Upgrade? Sei Network’s (Sei) Giga upgrade is a major overhaul designed to make the network faster, more scalable and better suited for high-performance onchain trading. Put simply, Giga is rebuilding three critical parts of the blockchain: consensus, execution and storage. (1) The first track focuses on consensus, with upgrades such as Autobahn designed to improve how Sei validators agree on the state of the chain. (2) The Ares upgrade targets execution, the part of the blockchain responsible for actually processing transactions. (3) Eidos focuses on storage, which is becoming increasingly important as blockchain throughput rises. Why does storage matter? Every transaction a blockchain processes has to be recorded. If the database cannot write data as quickly as the network executes transactions, higher throughput eventually becomes meaningless. Eidos is designed to solve that bottleneck. (4) Sei plans to replace the traditional Merkle-tree structure used for EVM state with FlatKV, a flat key-value database where updating one piece of state requires essentially one write. A lattice hash, or LtHash, is then used to maintain a verifiable fingerprint of the entire state without repeatedly recalculating an entire hash path. (5) Eidos also separates live EVM state from other blockchain data. This means transactions accessing current state no longer have to compete with historical data for the same database resources. (6) Sei is also introducing LittDB-backed storage for blocks and receipts. These records are written once but queried repeatedly, making them a different workload from constantly changing blockchain state. Older historical data will eventually move away from active nodes into archival storage, allowing nodes to focus their resources on the data needed for real-time operations. The interesting part is how Sei plans to deploy all of this. Instead of shutting down the network and migrating the entire database at once, Eidos is designed to migrate storage while Sei continues producing blocks. The old and new systems can run side by side during the transition, with data moved in batches and integrity checks performed throughout the process. The first phase arrived on Sei mainnet with the v6.6 release in August 2026, beginning the separation of EVM state and introducing improvements to the pruning process. The broader Eidos architecture, including FlatKV, LtHash, the new receipt store and off-node archival storage, is expected to arrive through subsequent releases. Sei’s ultimate Giga target is 200,000 transactions per second. But reaching that kind of execution speed requires more than a faster transaction engine. The blockchain also needs a storage system capable of keeping up. That is essentially what Eidos is trying to build. Giga is not just about making Sei execute transactions faster. It is about rebuilding the infrastructure underneath that speed so the network can actually sustain it.

BSCN

27,310 views • 1 month ago

Claude Design + Shopify is f*cking ridiculous 🤯 You can now publish pages from Claude Design → Claude Code → Shopify. Built 100% with Claude Design, Claude Code, and the Shopify CLI. Perfect for DTC brands and agencies who want to skip the design → dev handoff entirely. Here's how it works: → Design any landing page in Claude Design → Export as a zip and drop it into Claude Code → Install the Shopify + Shopify AI Toolkit plugins → Prompt Claude to convert the HTML into a Shopify page template + push to live theme → Claude uploads the images, deploys the files, and creates a published page No more handing designs off to a dev and waiting 2 weeks for a Shopify page. What you get: - A workflow that turns any Claude Design page into a real Shopify page template - Editable sections so your marketing team can swap copy, images, and CTAs without code - Images uploaded straight to Shopify Files automatically - A files-only deploy that only touches what's new in your live theme - A repeatable pipeline you can use every time you design a new landing page This is essentially the design-to-deploy pipeline brands have been waiting for. I put together a step-by-step playbook for going from Claude Design → published Shopify page. Every install, every plugin, every command, and the exact prompt that runs the whole thing. Want the playbook for free? > Like this post > Comment "SHOP" And I'll send it over (must be following so I can DM)

Mike Futia

59,257 views • 4 months ago