AZIP-21: Rename Fee Juice to AZTEC#50
Open
rolldavid wants to merge 1 commit into
Open
Conversation
Contributor
|
@rolldavid can we bump to AZIP-21 to reserve the AZIP-20 namespace for a future token standard? |
697c38f to
cbbccc6
Compare
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
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.
Summary
Proposes renaming the protocol's enshrined fee-payment asset from Fee Juice to AZTEC, along with every identifier derived from it (~1,527 occurrences across ~249 files in
aztec-packages). "Fee Juice" does not convey what the asset is: the in-protocol representation of the $AZTEC ERC20 token, bridged from L1, that is spent to pay transaction fees.Naming scheme
Two registers, as requested:
AZTEC— the Noir contract (AZTEC::at(address)), SDK classes (AZTECPaymentMethod,AZTECPaymentMethodWithClaim), getters (getAZTEC), andProtocolContractAddress.AZTEC.aztec_fee_payment_token— module/file/directory names, storage, protocol constants (AZTEC_FEE_PAYMENT_TOKEN_ADDRESS), and local variables.Why it's safe
The change is purely lexical. The canonical address (
5), the balances storage slot (1), the storage layout, the L1↔L2 bridge mechanics, and all wire/serialization formats are unchanged — pinned by a build-time assertion in the Test Cases. It therefore needs no new rollup version and carries no on-chain payload / no AZUP execution: it ships as source PRs againstaztec-packagesin a normal release.Notes for the editor
20to21at reviewer request, to reserve the AZIP-20 namespace for a future token standard.Corebecause it touches the enshrined protocol contract and protocol constants, but it is a naming-only change with no behavioral/economic impact — open to reclassification.