The problem with the rabbit r1 is that he tried to make it a productivity tool instead of a cute companion like the muse charm. CONSUMERS DO NOT CARE ABOUT PRODUCTIVITY

EIP-8250 (Keyed Nonces) and EIP-8272 (Recent Roots) are now considered for inclusion in Hegotá. Both run alongside EIP-8141 (Frame Transactions) on our public privacy testnet, where you can already try them. We're excited to keep pushing privacy on Ethereum closer to users. If you haven't tried it yet, find out how here: faucet.privacy.ethrex.xyz/

a little preview of the honey pit. a combat arena where you can load in your 721T NFTs and battle it out. here is a battle where I play as a Looper against a HivePunk. Jpeg frends next. but any 721T can load in. i'll also be adding a method to upgrade a regular 721 to 721T.

OPENAI 🔥: The upcoming ChatGPT Pro Max plan will cost $500. So far, this will be one of the most expensive AI subscriptions available on the market. I hope "it will be worth the wait" 👀

i think ultimately the issuing side's best positioned for consumer machine commerce vs. the wallets / networks / wrappers. the issuing side: • controls the auth (i.e., truly, ultimately decides if money moves) • can program the delegation layer (merchant / MCC, time, amount, duration etc.) • owns the downside ... so CARES fundamentally (fraud, disputes, CS, refunds) • knows the customer and owns IDV (has customer relationship, can provision, has events/signals) hard to see issuing side giving up scope to other players here medium- longterm. wallets own interface, networks own protocol, issuing owns permission. interface/permission seem most critical-

Features moved to "considered" status for Hegotá today (the fork following Glamsterdam): - three Frame txs EIPs (tx assertions via state diff opcode, keyed nonces, recent roots) - remove bloom filters - bump nonce of zero-nonce storage accounts - remove storage-clear refund & refund cap - unified tx content floor & block access list byte floor - call & return opcodes for the EVM - reserve EXTENSION (0xae) opcode Some that the call in 2 weeks will cover that ecosystem devs might be interested in chiming in about: - TCREATE opcode - account code restricted ecRecover - SETCODEFROM code reuse instruction - precompiles for ML-DSA verification - deactivate SELFDESTRUCT - EVM-ify the identity precompiles - read BLOCKHASH from storage and update cost "Considered" status doesn't definitely mean it'll be included, so if you're a dev and see one that you're excited about, find its champion on Forkcast and ask them if they need any help around it!