Frame Transactions and the Three Gates to Privacy

Submit
ethresear.ch

Frame transactions and the three gates to privacy

AI summary of the linked article

Frame transactions under EIP-8141 could let privacy withdrawals pay their own gas, removing relayers, but the article argues that default mempool, FOCIL and node rules currently exclude privacy withdrawals from every default path to censorship resistance. Under default parameters, a Groth16 pairing check exceeds the 100k MAX_VERIFY_GAS cap, so the transactions are rejected from the public mempool and excused from FOCIL enforcement. The article says the gap stems from how FOCIL enforces inclusion. A validation-index approach, which replaces the O(k²) append loop with per-transaction index claims, would allow the per-inclusion-list VERIFY budget to rise to 2^20 gas.

No comments yetWhat caught your eye? Start the discussion.