Context Bundle compression makes 4337 efficient on L1. As of 2023-01-17, Daimo's running compression in prod, submitting 1-op bundles directly Pimlico has a testnet prototype of a real bundler API Road to prod [x] Document rough spec. https://github.com/daimo-eth/bulk/issues/7#issuecomment-1897309585

Abstract This standard allows contract wallets to receive encrypted messages. The sender calls getEncryptionPublicKeys(), a view function, and uses the result to perform key agreement. Messages are encrypted to each of the returned keys. Motivation Contract accounts have many great advantages. When implementing just ERC-4337, however, they lack two important primitives: encryption and signing. An EOA, by contrast, consists of an secp256k1 keypair, and so has those capabilities automatically. ERC-1271 generalizes signing to contract accounts.

I've been thinking a lot about anon forums and credible neutrality. How do you do community moderation? Having an appointed group of mods feels antithetical. Yesterday, I shipped a bare prototype of community moderation via the "Best" feed. How much moderation do you need? On one extreme (1), you have a system where the community can vote someone off the island. (2), they can't ban you but can flag posts to hide them. The other extreme, (3) is just community-driven ranking so that good posts bubble to the top, with no way to explicitly hide bad ones. Avoiding sockpuppetry. All of this relies on sybil resistance. Zucast as currently implemented is mildly vulnerable to sybiling. I think that for a forum like this, you want the system at the center to guarantee 1-person-1-account or something close to that. Local credible neutrality. One wrinkle is that Zucast is not trying to be globally neutral. After all, it is a curated set of people that went thru an admissions process! Instead it's about neutrality within the group. Everyone posts from a clean slate--Vitalik and a visitor could be adjacent numbers. And it's credible in the sense that the code is open, anyone can convince themselves that even the server operator has no way to know who #69 is, & there's an append-only log at the center that people can check has not been tampered with. Every entry in the log is cryptographically verifiable.