feat(tempo): support from on token.burn - #5166
Merged
Merged
Conversation
|
@max-digi is attempting to deploy a commit to the Wevm Team on Vercel. A member of the Team first needs to authorize it. |
🦋 Changeset detectedLatest commit: 5e1c761 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
Co-authored-by: decofe <256792747+decofe@users.noreply.github.com>
Co-authored-by: decofe <256792747+decofe@users.noreply.github.com>
decofe
force-pushed
the
tempo-burn-at
branch
from
September 30, 2026 22:57
fa70f42 to
5e1c761
Compare
Merged
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.
Adds viem support for TIP-1006
burnAt, which activates in the Tempo T12 network upgrade (tempoxyz/tempo#7935), by adding an optionalfromtotoken.burn. It also syncs the Tempo ABIs.Changes
token.burn,token.burnSyncandtoken.burn.callaccept an optionalfrom:from, the call isburnAt(from, amount), which requiresBURN_AT_ROLE.burn(amount), orburnWithMemowhenmemois set.fromandmemocan't be combined (OneOf), sinceburnAthas no memo variant.burn.extractEventaccepts either aBurnor aBurnAtlog.burnSyncreturns{ amount, from, receipt }, plusburnerwhen the burn went throughburnAt.pnpm gen:tempo-abis:tempoxyz/tempo@6ef1f81addsburnAt(address,uint256),BURN_AT_ROLE()andBurnAt(address indexed burner, address indexed from, uint256 indexed amount).tempoxyz/zones@22318d9adds token-enablement cursor functions and errors, and makessubmitBatchoverloaded andverifysingle-signature.ExecutionErrormessages forTokenEnablementCursorNotInitialized()andInvalidTokenEnablementTransition().tempoxyz/earn@d6373e4, the commit already onmain. Latest earn (1f4b4f6) overloadswithdrawExactand renames the engine contracts, which breaksactions/earn.tstyping, so it should be its own migration.fromon thetoken.burndocs page and added a changeset.The
'burnAt'token role forgrantRoles,hasRoleand related actions comes from ox'sTokenRoleand is added in wevm/ox#497.Validation
tsc -b: no errors insrc/tempo. The only errors are pre-existing ones in files that import generated test contracts, which weren't built in this environment.biome checkpasses.burn.call+fromcase totoken.test.ts. It wasn't run here because the suite needs a local Tempo node.burn.callproducesburn,burnWithMemoorburnAtas expected, andextractEventdecodes bothBurnandBurnAtlogs.Prompted by: @max-digi