←
whit ☕️7,011 posts
whit ☕️ avatar

whit ☕️

@cryptomachia

director of marketing @EspressoSys // Maine chapter prez @standwithcrypto // prev @CoinbaseDev @darkblockio // ex-journo // dad x2

◷ Joined February 2018▧ 860 Photos and videos
whit ☕️ avatar
whit ☕️@cryptomachia·10 Dec 2025

I don't think people realize what we just shipped. The first one-click crosschain NFT mint. No bridging. No gas. No friction. 2021 me would be stunned. All possible because ApeChain & RARI use Espresso as a base layer. Kudos to @rarible & @EspressoSys eng teams on the launch.

Mint an NFT on @ApeChainHUB using funds from @RariChain with just one click. No bridges. No gas. No dust. No friction. The first seamless crosschain mint is live on @rarible rarible.com/apechain/collect… Experience what's possible when rollups use a base layer designed just for them.

Post attachment
whit ☕️ avatar
whit ☕️@cryptomachia·Nov 4

In Maine, @TroyJackson207, a pro-crypto Democrat ("pro" in the sense that he supports common-sense regulations) ousted Republican US Sen Susan Collins (@SenatorCollins). I'd like to think Collins' vote in Sept against cloture on the Clarity Act was the final straw, but let's not kid ourselves. The more useful takeaway is that supporting clear crypto rules isn’t a political liability. We'll take it. I look forward to working with @TroyJackson207 on getting market structure done right.

Congratulations to the pro-crypto champions who won their elections, including more than 50 pro-crypto new members heading to Congress. In the closest races, our advocates showed up: in Florida's 9th District, Darren Soto won by 1,477 votes. In that same district, we mobilized 10,267 SWC advocates, and SWC volunteers made 1,483 voter contacts via phone calls and door knocks. We look forward to working with the incoming Congress: incumbent Crypto Champions, new pro-crypto members, and undecided lawmakers who will soon meet the SWC community. Together, we will work together to deliver a better financial system for all.

Post attachment
whit ☕️ avatar
whit ☕️@cryptomachia·Oct 27

No, OpenAI has not broken any part of Ethereum. For those falling for the FUD, he’s referring to the Exponential Time Hypothesis (ETH), a math conjecture about how hard certain CS problems are. It has nothing to do with Ethereum.

An internal model at OpenAI has produced a claimed refutation of ETH! Russell Impagliazzo, Mohan Paturi, and I have been asked to help organize an open and independent examination of this claim. 1/4

whit ☕️ avatar
whit ☕️@cryptomachia·Oct 21

1 million TPS with subsecond finality. Based on intellectually honest benchmark tests designed to mirror mainnet’s 100 globally distributed nodes. Don’t sleep on Espresso.

Espresso mainnet can now handle up to 1 million transactions per second. And finality stays under a second, even at that peak load. How we did it, and why it matters ↓

0:29
whit ☕️ avatar
whit ☕️@cryptomachia·Oct 2

People use tweets like this to support the argument that L2s are dead (popular since Ethereum ditched the rollup-centric roadmap). I disagree. L2s are just applications and as such need to offer a compelling product & find pmf just like any other startup. If you don’t, you fail.

Blast@blastOct 2

Blast will be shutting down. We launched Blast with the goal of building a self-sustaining chain for users and developers. Unfortunately, the economics of operating the chain no longer make sense: the ongoing costs of maintaining Blast exceed the revenue generated by the L2, and we do not see a credible path to making the chain economically sustainable. As a result, we've made the difficult decision to wind Blast down. We're sorry to the users and developers who believed in Blast, built on it, and supported the ecosystem. Our priority now is making the shutdown as smooth and safe as possible. We're asking all users to withdraw their assets from Blast to Ethereum mainnet, including any balances held in the Blast PWA. To make this easier, we will be reducing the withdrawal delay to 24 hours. As part of the shutdown process, we'll first begin withdrawing Blast's Lido assets. This process is expected to take approximately one week. During this period, withdrawals will temporarily be unavailable, even after the withdrawal delay is reduced to 24 hours. Once that process is complete, withdrawals will resume with the new 24-hour delay. Users will have until October 26, 2026 to withdraw through the normal Blast interface. After October 26, assets will remain withdrawable, but users will need to interact directly with the Blast bridge contracts on Ethereum L1. We'll publish detailed instructions before then. We strongly encourage everyone to withdraw their assets to Ethereum mainnet before October 26.

whit ☕️ avatar
whit ☕️@cryptomachia·Oct 2

The optimal base layer is designed from scratch to be one, not retrofitted to serve as one.

Unlike legacy L1s built to be monolithic execution environments, Espresso was built as a base layer for other chains from day one, leaving execution entirely to the independent chains that rely on it for subsecond finality and throughput designed to scale to millions of TPS.

0:08
whit ☕️ avatar
whit ☕️@cryptomachia·Sep 19

Let it be known @foliosociety that @mattgriffinart is why I want to buy your The Three-Body Problem Trilogy edition. When sitting on my shelf, the art is as important as the title! Also, anyone who loves sci-fi art and reflections on the creative process should follow Matt.

Thought I'd share the story of how I used physics to make art for The Three-Body Problem Trilogy It's named after a famous maths problem .. Liu Cixin builds the entire epic on real science ..so, while I could just make stuff look science-y, I decided I didn't want to fake it..🧵

Post attachment
whit ☕️ avatar
whit ☕️@cryptomachia·Sep 17

Sad that Bloomberg is just squatting on the @crypto handle at this point. Last post was 17 months ago.

In today's Bloomberg Deals: Goldman Sachs on convertible bond demand, Brookfield revives talks on potential Grifols offer and China restricts companies from investing in US trib.al/P1ZMQVF

whit ☕️ avatar
whit ☕️@cryptomachia·Sep 17

Don't make bold claims if you'll immediately refute them. @jerallaire called @arc "something the world has never had before: an open, neutral [platform]...secured & operated by the most important financial institutions on earth" Bank-run chains aren't open, neutral, or new.

Arc@arcSep 16

Arc Mainnet is live. In his opening keynote, Jeremy Allaire frames Arc as the Economic OS for the internet: infrastructure for a world where money, markets, assets, applications, and agents can move and coordinate onchain. The network is open.

0:44
whit ☕️ avatar
whit ☕️@cryptomachia·Sep 17

Hey @HawleyMO - how did your farmers and community banks survive the creation of money market funds and high-yield online savings accounts?! Depositors didn’t blindly chase the highest yield available then, and they wouldn’t today w/ stablecoin rewards.

🚨 JOSH HAWLEY EXPLAINS HIS NO VOTE ON THE CLARITY ACT 🚨 Sen. Josh Hawley (R-MO) was one of four Republicans (including @SenThomTillis, who switched his vote at the last minute) to break with the party and sink the crypto bill's advance in the Senate. His reasoning: "My concern is all to do with farmers in my state. Ag is our number one industry in Missouri, and farmers are so concerned they won't be able to get loans from small-town banks, because investors will leave those banks chasing the yields available under the bill." @HawleyMO said Sen. @JerryMoran, who also voted no, has language that could fix it - calling the issue "pretty doable" to resolve. "We've got to make sure those banks stay in operation, stay competitive, and have enough capital to make loans or our Missouri economy will collapse."

1:12
Omid Malekan avatar
⟳ whit ☕️ retweeted
Omid Malekan@malekanoms·Sep 14

Many of us have mentioned how the stablecoin yield debate playing out in Clarity, and the arguments made against yield by the bank trades, mirror the battle over money market funds in the 1970s. Well here's some proof. Here's a letter submitted by the Independent Bankers Association of America (a predecessor to the ICBA) in a 1980 hearing of the Senate Banking committee on money market funds. As you can see, many of their arguments against stablecoins are almost verbatim a copy from what they argued back then: threat to deposits, harms lending, uniquely dangerous for smaller banks. And we know today that argument was dead wrong. Money market balances grew parabolically into the trillions, and yet banks remain flush with deposits.

Post attachmentPost attachmentPost attachmentPost attachment
whit ☕️ avatar
whit ☕️@cryptomachia·Sep 15

Base and Ethereum going their separate ways on account abstraction perfectly supports our thesis. Given the choice, L2s will choose architectural control over compromising their goals to fit inside another team's vision. This is why fragmentation is inevitable unless L2s have a base layer that's agnostic to their architecture and provides subsecond finality. When L2s get a new BFT finalized state every <1s, they can interoperate securely in real time (with other chains, bridges, CEXs, etc) rather than forcing users to choose between waiting 16min for Ethereum finality or taking on risk by trusting a centralized sequencer or third-party bridge. Ethereum is a monolith that was never designed to extend its BFT consensus to external chains. Espresso was.

I'm sad to report that the AA collab between 8130 and 8141 (Frames) broke down last week, and Base and Ethereum are now going separate ways to implement different AA standards. I want to share some reflections on this collab and on the future of the EVM. For a long time, the EVM has been a unifying force between L1 and L2s. Thanks to a standard account model (EOA) and a standard transaction type (EIP-1559), users have been able to enjoy their wallets working seamlessly across EVM chains. Similarly, a AA standard shared across L1 and L2s would ensure a consistent multi-chain UX for smart accounts, including post-quantum (PQ) accounts which we will eventually all use. As the crypto industry matures, however, L1 and L2s are starting to diverge in the values they provide and the use cases they target: - For the L1, it's all about CROPS -- censorship-and-capture resistance, open source, privacy, and security. In short, Ethereum L1 wants to be the most decentralized programmable settlement layer of the world, which is what makes it a good base layer for L2s in the first place. - For L2s, it's all about scaling, customization, and compliance -- things that commercial and enterprise use cases demand, and that the L1 does not provide. These diverging needs have pushed the shared layer -- the EVM -- to its limit, and AA proved to be the breaking point. While L1 and L2s both value core AA use cases such as gasless transactions and passkey wallets, they differ sharply in what these features must comply with: - For the L1, AA transactions must be uncensorable, private, and quantum-resistant, which call for a transaction type optimized for PQ signature aggregation and privacy protocols, and an account model that can be freely programmed and extended by developers without permissions from the chain. These needs lead to AA standards such as ERC-4337, EIP-7701, and now EIP-8141 aka Frame Transactions. - For L2s, AA transactions must work at high scale, and they must be legible such that the protocol can enforce clear rules about what kinds of accounts/transactions are permitted vs not. These needs lead to AA standards such as Tempo Transactions and now EIP-8130 by Base. With the AA collab, the authors of 8130 and 8141 tried to define a shared standard that can work for both L1 and L2s. While we identified a number of technical solutions, they all required one side or the other to compromise at least a little bit on their core goals. But ultimately, Ethereum wanted to be the best version of Ethereum, and Base wanted to be the best version of Base, and while both sides acknowledged the benefits of ecosystem interoperability, it was ultimately secondary to the need for each chain to achieve their core goals. So separate ways we went, putting the burden on wallets to deal with the fragmentation that ensues. Now, just because we ended up with fragmentation doesn't necessarily mean it was a bad outcome. If reducing fragmentation comes at the cost of homogenizing chains to the point that they fail to solve problems for the users they care about, that would not be a price worth paying. While I was initially sad that the collab did not come to a successful conclusion, I took solace in the fact that both Ethereum and Base are now free to innovate on AA to the maximal extent in accordance with their own visions, unshackled from the need to accommodate the other side. If they execute well, and if the wallet community can bridge over the fragmentation, we may well end up with the best possible UX for the end users. So where does that leave us -- the broader Ethereum community including Ethlabs -- if we want to continue pushing for a consistent UX across EVM chains? I see two paths forward: - We can establish a coordination mechanism that encompasses more stakeholders than ACD itself (where only L1 client devs have voting powers), to govern shared L1<>L2 resources such as the EVM. That way, L2s can participate in shaping the EVM, as opposed to having to accept whatever the ACD decides, or being forced to fork if they don't like the decision (such as in this case with Base). - We can accept that fragmentation of the EVM and wallet UX across L1 and L2s is inevitable due to their conflicting needs, and dedicate our resources to building wallets and applications that can abstract over the differences. Indeed, the collab was an exercise in the first path -- we invited Base, Arbitrum, and other stakeholders to directly influence how native AA shapes up for the L1. While it ultimately failed in this case, I feel a better outcome could've been achieved if we had established a dialog between both sides way earlier, as opposed to well after L1 core devs had rallied around Frames. On the other hand, I also learned from this exercise that some differences are unavoidable, and indeed it would be counterproductive to overly pursue interoperability at the cost of differentiation. In other words, we sometimes just gotta let the chains cook. For that reason, I've also become more bullish about the second path -- building wallets and applications that can speak the native transaction types of each chain, and hide the complexity from users through UX abstractions. This puts a lot of onus on the wallet/application developers of course, but on the bright side, it's also an opportunity for wallets/applications to stand out and differentiate, by competing to provide great UX across chains despite the underlying fragmentation. Ethereum is the art of staying together while remaining different. We must accept that chains will succeed by innovating, and innovations will naturally result in differences. On the other hand, we must never give up on dialogue when we can achieve interoperability without compromising core product goals. As Ethereum and crypto grow to eat the world, the push and pull between innovation and collaboration will only intensify, and it's up to all of us -- builders across L1 and L2s, applications and wallets -- to determine whether diverse innovations will split Ethereum apart, or make it thrive as one.

whit ☕️ avatar
whit ☕️@cryptomachia·Sep 10

I wrote a point-by-point rebuttal to the most common arguments you'll hear from the community banking lobby about the CLARITY Act and stablecoin rewards. Thanks @wadepreston for the review and suggestions.

whit ☕️ @cryptomachia Sep 10 Article Community Banks' Attack on CLARITY’s Stablecoin Rewards Collapses Under Scrutiny Community banking trade groups, led by the Independent Community Bankers of America (ICBA), are lobbying hard against the CLARITY Act. Almost all of that opposition centers on one provision, Section