docs(fee-abstraction): the zero address is not a native-fee alias - #2313
Merged
Conversation
palango
requested review from
karlb and
seolaoh
and removed request for
a team
September 4, 2026 12:02
karlb
approved these changes
Sep 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The fee abstraction specification page did not say how a CIP-64 request expresses native CELO, and the zero address looks like a plausible alias. It is not one. The canonical chain has always rejected a
feeCurrencyof the zero address as an unregistered fee currency, and this states that rule, once for the JSON-RPC request and once for the encoded transaction and the blocks that carry it. celo-org/celo-kona#314 makes celo-reth enforce the same rule; this docs change merges before that PR deploys, since the rule already holds on the chain.mint broken-linkson the branch head reportssuccess no broken links found.