Applying for the Product Educator role at @loops. I made a 3-part video series showing how I’d explain Loops to SaaS founders, developers, and product teams. The goal was not to make an ad. The goal was to make the product category clearer: modern SaaS email is not just newsletters. Part 1: What is Loops?

Happy New Week! 💜 A fresh week is a new opportunity to learn, build and grow. Start small. Stay consistent. Keep moving forward. What are you working toward this week? #HappyNewWeek #0xVerseAcademy #LearnBuildGrow

🆕: @Meta and @stripe are partnering to make it easy for businesses to accept agentic payments using the @Muse Connector Platform. Learn more: • muse.ai/platform • docs.stripe.com/agentic-comm… • Email jweinstein@ / @jeff_weinstein

Build an AI product people can actually use. We’re partnering with @GoogleAfrica to launch the Paystack AI Builder Challenge, a two-week hackathon. Bring your own idea or solve a real problem submitted by a Paystack business. Apply by Sept 24: paystack.com/hackathon

Do you remember when you joined X? I do! #MyXAnniversary

One positive consequence of all the recent detailed thinking about transaction formats - not just 8141, also "future of state" discussions eg. UTXOs, PBT, keyed nonces, and also recursive STARK mempool - is that we have a much more explicit understanding of how transactions have "actions" and "dependencies", and we can engineer around optimizing the two separately. An action is an effect that a transaction has. A dependency is a fact about the transaction and/or the state that must be true for the transaction to be valid. eg. a signature is a dependency, a Merkle proof of a UTXO is a dependency, a ZK-SNARK (or STARK) is a dependency, a call that sends ETH is an action Dependencies can be processed in parallel. Dependencies that involve state can be reasoned about by a mempool, especially if the specific state accessed is statically declared. Dependencies that are pure (no state calling allowed) can be processed once at the mempool layer and never need to be processed again - and potentially even replaced with a STARK verifying them, allowing not just execution but also data to be elided. In principle, dependencies and actions can all be expressed as calls (if needed, calls to precompiles). This would make the transaction format itself very bare-bones and minimalist (a list of calls, flags for the type of each call eg. dependencies would be static or pure calls, and origin, nonce, etc) and allows maximum cross-compatibility even if different EVM chains have different features. In 2015-era Ethereum, thinking explicitly about these differences was not very important: execution was execution, there were few enough transactions that we could process them all serially, and single-key ECDSA accounts were good enough for everyone. Ethereum's current scaling strategy, however, requires moving beyond that paradigm. Ethereum is beloved by many developers because the execution and state model is so dynamic and flexible. But dynamic and flexible is not friendly to scaling. Fortunately, >90% of Ethereum's activity by volume does not require anything dynamic and flexible. So, we require contracts, accounts and transactions to more explicitly specify what is dynamic and flexible and what is more statically-analyzable but more restrictive, and more statically-analyzable things get the lowest gas cost and thus scale the most. Effectively, learning from the best of both the 2015-era Ethereum model and a more Bitcoin-like model (reminder: Bitcoin has had what I call account abstraction since the beginning), and making a mixture of both (really, the full spectrum between both) available, with gas costs appropriate for the level of scale involved. New state types, the recursive STARK mempool, keyed nonces, etc all go in this direction. This all relates to transaction types, because a general-purpose transaction type is a very natural interface layer on top of which all of this can be implemented, and the current thinking around the EIP-8141 transaction type is going in this exact direction that is friendly to these kinds of future generalizations. So in that sense, 8141 done well is not just a culmination of 10 years of account abstraction work, it's also preparation for the next few years of responsible decentralization-friendly hyper-scaling.

Six weeks. → AI. → UI/UX. → HTML. → CSS. → JavaScript. → AI-assisted coding. → Vibe coding. → Replit. → Bolt. AI-powered product creation. Today, our Summer Tech Bootcamp comes to a close. But we weren't trying to teach students a list of tools. We wanted to show them what becomes possible when creativity, technology and AI come together. Idea → Design → Code → Product. That's the mindset we're building at 0xVerse. People who don't just use technology. People who build with it. Six weeks down. A lifetime of building ahead. 🚀

Applications are open for the Claude Campus Ambassadors program. This year, we’re expanding opportunities to more students, with three tracks for undergrads, graduate students, and PhDs/postdocs. Apply here: anthropic.com/campus

It’s been a long while I shared opinions as regards building on X. Times have changed and priorities also have. Let’s get back into the Arena. Happy Sunday to you

brother do you know how insane it would be if we have buy buttons native on @X for tickers? and then they added revenue-sharing on trading volume the same way they have ad-revenue sharing? hello?

breaking: how i dropped out of college and scaled the #93 fastest growing company in america and #3 in marketing. my story on working with the largest companies in the world and why now is the most important moment in the history of media. + how to win.

As a developer, you should know core system design concepts. This helps show potential employers that you can turn design requirements into production-ready code. This course covers app architecture, API design, caching, networking, databases, and more. freecodecamp.org/news/learn-…

Crypto makes it possible 100%

Every great founder learns to suffer. The rejections. The flat metrics. The 3 AM ceiling stares wondering if you’re delusional. Embrace it. High pain tolerance is one of the few advantages competitors can’t copy. Don’t seek ease. Seek strength.

I’ve realized I don’t actually enjoy collecting answers. I enjoy collecting understanding. One question turns into ten. One article becomes five. One API leads to an entire architecture rabbit hole. I rarely stop at “How does this work?” I’m usually asking: “Why was it designed this way?” “What problem was it solving?” “What breaks if we change it?” It’s exhausting sometimes. But I don’t know how to learn any other way.

Claude Code on desktop now works with the iOS simulator. Build and run your iOS app, and the simulator opens in a panel right next to your conversation. Available today in public beta.

AI coding agents can build software quickly. But they can also say: “Done.” “Deployed.” “Everything is working.” …while the database is still disconnected, an endpoint is failing, or the contract was never properly deployed. I kept running into this while building with AI agents. So for the Spark hackathon, I built ShipReceipt. ShipReceipt checks the actual project: → public GitHub repository → selected commit → live deployment → health and readiness endpoints → deployed Monad contract It then records exactly what passed and what failed. No AI decides the result. No fake green success screen. No hiding failed checks. One of the live receipts passed 4 out of 5 checks because the readiness endpoint returned a real HTTP 404. ShipReceipt marked it Partial and preserved the failure in the evidence. The detailed evidence stays offchain, while its integrity, result, issuer, and timestamp are recorded on Monad thus making later changes detectable. This can help developers verify AI-generated work, clients inspect software before accepting delivery, and hackathon judges review working submissions more confidently. AI can claim it shipped. ShipReceipt proves what actually worked. ShipReceipt is now live on the Build Anything showcase. Check out the project, test the live receipts, and please upvote it if you believe software completion should come with verifiable evidence: buildanything.so/showcase/sh… Live app: shipreceipt.vercel.app Partial receipt: shipreceipt.vercel.app/recei… Built on Monad Testnet. #Monad #BuildOnMonad #SparkHackathon #BuildInPublic #AIAgents

Ethereum is for shipping. Here are some of the things the Ethereum ecosystem launched, upgraded, and announced over the past month. 0/ @RobinhoodApp launched Robinhood Chain (@RobinhoodCrypto) on mainnet, an Ethereum Layer 2 built on the @arbitrum stack, enabling 24/7 trading of tokenized stocks and ETFs for users in over 120 countries through Robinhood Wallet. The network surpassed $1B in DEX volume in just over a week. 1/ @aztecnetwork achieved Stage 2 rollup decentralization under @l2beat's framework, removing governance control over its core protocol and taking another step toward trust-minimized infrastructure. 2/ @VitalikButerin shared updates to Ethereum's evolving technical roadmap, outlining the next phase of Lean Ethereum and the protocol's long-term direction. 3/ @ethlabs_org launched as a non-profit R&D lab for Ethereum and ETH. Their mission is to make Ethereum the settlement layer of the global economy. 4/ @ethereuminsti launched as an independent non-profit dedicated to accelerating the institutional adoption of Ethereum, its L2s, applications and overall ecosystem. 5/ @aave introduced Stable Vaults, fixed-rate stablecoin yield vaults designed for seamless integration into consumer applications. 6/ @zama launched the First DeFi Yield Venue for Confidential USDC (cUSDC) in partnership with @Morpho and @SteakhouseFi, bringing private stablecoin lending to Ethereum. 7/ @swissknifexyz launched a new Privacy Protocol Tracker, making it easier to compare fees, wait times, supported chains, and other metrics across Ethereum privacy protocols. 8/ Global tickets for @EFDevcon 8 went live, alongside speaker applications for this year’s conference in Mumbai, India. 9/ @Optimism and @toss__official signed an agreement to explore bringing the Korean Won onchain, expanding blockchain-based financial infrastructure for one of South Korea's largest fintech platforms. 10/ @OctantApp completed Epoch 12, its first full quadratic funding round using a zero-knowledge vote coprocessor and new voting application, distributing 88.1 WETH to Ethereum public goods projects. 11/ @0xprivacypools launched the trusted setup ceremony for Privacy Pools V2 ahead of its next protocol deployment. 12/ Gwei Name Service launched an ownerless, immutable Ethereum naming system built without administrative ownership. 13/ @ammalgam launched on Ethereum mainnet, introducing oracle-free lending without impermanent loss. 14/ @lodestar_eth added support for Fast Confirmations, allowing Ethereum node operators to confirm transactions in a single slot using validator attestations. 15/ @PrivacyBoost introduced preconfirmations for private transfers, allowing transfers to be treated as usable in around one second before final settlement. 16/ The @ethereumfndn published Ethereum Basics for Governments and Institutions, a new primer introducing Ethereum as a credibly neutral digital public utility for policymakers and enterprise leaders. 17/ @OndoFinance launched @OndoPerps, enabling tokenized stocks to be used as collateral for perpetual futures across equities, commodities, and indices. 18/ @base introduced Base Privacy, giving enterprises infrastructure to trade, pay, and settle onchain with built-in confidentiality and compliance features. 19/ @BGDA_UK launched BAGEY, a natively tokenized UK regulated fund on Ethereum where the blockchain serves as the legal register of record. 20/ @sparkfinance launched the Stablecoin FX Layer on @Uniswap v4, introducing shared liquidity infrastructure that lets stablecoins access a common liquidity layer. 21/ @Trueo_ launched user-created prediction markets, allowing anyone to create a market by asking a question and letting participants trade on the outcome through a fully onchain prediction market. 22/ @kpk_io integrated @OpenCover Covered Vaults, allowing depositors to add opt-in onchain insurance to curated vaults, with coverage underwritten by @NexusMutual. 23/ @PropellerSwap launched Turbine on Ethereum mainnet, enabling large trades to settle with lower slippage by sourcing liquidity across onchain, offchain, and peer-to-peer markets. 24/ Hosted by @web3privacy, the Neocypherpunk Summit brought together around 1,000 builders and researchers in Berlin to advance privacy, open-source infrastructure, and human rights. 25/ @eth_systems launched as a company building modular privacy infrastructure for institutional Ethereum.

Discover Our AI Career Tracks Artificial Intelligence is transforming every industry, and now is the best time to get started. 🔹 AI Automation – Automate workflows, business processes, and repetitive tasks using AI. 🔹 AI Vibe Coding – Build websites, apps, and AI-powered solutions faster with modern AI development tools. 🔹 AI Engineering – Learn to design, build, and deploy intelligent AI systems for real-world applications. Whichever track you choose, you'll gain practical, hands-on experience by building real projects. Our new cohort starts on August 3rd, and registration is still ongoing. Register now: 0xverse.academy/register The future belongs to those who know how to build with AI.

Check out ShipReceipt on Build Anything buildanything.so/showcase/sh…