Jeff Wentworth

“They say there’s the Nagoya Skip, but I say, Play Nagoya First!!!” - @eddievedder

TFW you use up all the leftovers in the fridge at the end of the week

Time to don your @HardhatHQ! And remember --via-ir is always the right choice! :)

Having bad home wifi is the modern equivalent of your VCR flashing 12:00. "What time is it at Billy's house?"

I could've sworn I just saw Claude Code say: ✺ Whinging...

The conspiracy theorist in me thinks that agentic coding tools are being tuned to add superfluous code to burn tokens, and which I then have to have them remove, burning more tokens.

Broccoli has achieved “designated vegetable”status in Japan. Such designation makes it subject to subsidies and other regulatory measures to ensure it is available year round for a reasonable my stable price.

the riskiest live demo i’ve ever pulled off: 2000 phones synchronized with light and audio down to the millisecond. i'll never forget this night.

In crypto, "small" errors don’t stay small. Floating-point arithmetic inevitably introduces precision issues, yet there are surprisingly few tools for easy arbitrary-precision calculations. So we built BigNum.app. If this is useful for your work 👇 bignum.app

暗号資産で「少しの誤差」は、少しでは済みません。 浮動小数点では精度のズレが避けられないのに、手軽に任意精度で計算できるものが意外とない。 そこで、計算機 BigNum.appを作りました。 必要な方の参考になれば👇 bignum.app

An old school nomikai and an old school hackathon have more in common than you think

🌿Cilantro Soapiness: the first ever genetic test ran on a Dark Bio Ark enclave. Against my own genome, no less! A test, vibe coded with AI, without looking at the code, never having to worry about malicious code touching sensitive data, because the Ark guarantees safety. 🤍

TFW when you forget to switch back to Auto from Extended Thinking Pro when asking "convert 1 tbsp baking powder to grams". Best answer to that question ever, though.

If you've added a favicon, it's no longer a minimum viable proof-of-concept

@VitalikButerin We’ll need to update our Account Abstraction delegation checker: eip7702.app

Now, account abstraction. We have been talking about account abstraction ever since early 2016, see the original EIP-86: github.com/ethereum/EIPs/… Now, we finally have EIP-8141 ( eips.ethereum.org/EIPS/eip-8141 ), an omnibus that wraps up and solves every remaining problem that AA was intended to address (plus more). Let's talk again about what it does. The concept, "Frame Transactions", is about as simple as you can get while still being highly general purpose. A transaction is N calls, which can read each other's calldata, and which have the ability to authorize a sender and authorize a gas payer. At the protocol layer, *that's it*. Now, let's see how to use it. First, a "normal transaction from a normal account" (eg. a multisig, or an account with changeable keys, or with a quantum-resistant signature scheme). This would have two frames: * Validation (check the signature, and return using the ACCEPT opcode with flags set to signal approval of sender and of gas payment) * Execution You could have multiple execution frames, atomic operations (eg. approve then spend) become trivial now. If the account does not exist yet, then you prepend another frame, "Deployment", which calls a proxy to create the contract (EIP-7997 ethereum-magicians.org/t/eip-7997-det… is good for this, as it would also let the contract address reliably be consistent across chains). Now, suppose you want to pay gas in RAI. You use a paymaster contract, which is a special-purpose onchain DEX that provides the ETH in real time. The tx frames are: * Deployment [if needed] * Validation (ACCEPT approves sender only, not gas payment) * Paymaster validation (paymaster checks that the immediate next op sends enough RAI to the paymaster and that the final op exists) * Send RAI to the paymaster * Execution [can be multiple] * Paymaster refunds unused RAI, and converts to ETH Basically the same thing that is done in existing sponsored transactions mechanisms, but with no intermediaries required (!!!!). Intermediary minimization is a core principle of non-ugly cypherpunk ethereum: maximize what you can do even if all the world's infrastructure except the ethereum chain itself goes down. Now, privacy protocols. Two strategies here. First, we can have a paymaster contract, which checks for a valid ZK-SNARK and pays for gas if it sees one. Second, we could add 2D nonces (see docs.erc4337.io/core-standards… ), which allow an individual account to function as a privacy protocol, and receive txs in parallel from many users. Basically, the mechanism is extremely flexible, and solves for all the use cases. But is it safe? At the onchain level, yes, obviously so: a tx is only valid to include if it contains a validation frame that returns ACCEPT with the flag to pay gas. The more challenging question is at the mempool level. If a tx contains a first frame which calls into 10000 accounts and rejects if any of them have different values, this cannot be broadcasted safely. But all of the examples above can. There is a similar notion here to "standard transactions" in bitcoin, where the chain itself only enforces a very limited set of rules, but there are more rules at the mempool layer. There are specific rulesets (eg. "validation frame must come before execution frames, and cannot call out to outside contracts") that are known to be safe, but are limited. For paymasters, there has been deep thought about a staking mechanism to limit DoS attacks in a very general-purpose way. Realistically, when 8141 is rolled out, the mempool rules will be very conservative, and there will be a second optional more aggressive mempool. The former will expand over time. For privacy protocol users, this means that we can completely remove "public broadcasters" that are the source of massive UX pain in railgun/PP/TC, and replace them with a general-purpose public mempool. For quantum-resistant signatures, we also have to solve one more problem: efficiency. Here's are posts about the ideas we have for that: firefly.social/post/lens/1gfe… firefly.social/post/x/2027405… AA is also highly complementary with FOCIL: FOCIL ensures rapid inclusion guarantees for transactions, and AA ensures that all of the more complex operations people want to make actually can be made directly as first-class transactions. Another interesting topic is EOA compatibility in 8141. This is being discussed, in principle it is possible, so all accounts incl existing ones can be put into the same framework and gain the ability to do batch operations, transaction sponsorship, etc, all as first-class transactions that fully benefit from FOCIL. Finally, after over a decade of research and refinement of these techniques, this all looks possible to make happen within a year (Hegota fork). firefly.social/post/bsky/qmaj…

Sakura season is the pumpkin spice season of Japan

Who’s given their @openclaw a fax number?

Last week in Web3 Abstraction: - Vitalik pushes a cypherpunk @Ethereum vision - @Base plans move off the OP Stack - EIP-7702 delegation checker app by @curvegridinc - EIP-8151: ecRecover key deactivation - EIP-7851: disable delegated EOAs - Read more 👇 go.etherspot.io/O0tDdgw

Gm from the @gftnforum_jp day one!