Skip to content

fix: support CeloDynamicFeeTxV2 (CIP-64) in span batches#430

Merged
palango merged 3 commits intocelo-rebase-16from
celo-span-batch-cip64
Mar 25, 2026
Merged

fix: support CeloDynamicFeeTxV2 (CIP-64) in span batches#430
palango merged 3 commits intocelo-rebase-16from
celo-span-batch-cip64

Conversation

@palango
Copy link

@palango palango commented Mar 13, 2026

Span batch encoding/decoding failed on Celo CIP-64 transactions (type 0x7b) because the tx type switch statements only handled legacy, access list, dynamic fee, and set code types.

Add spanBatchCeloDynamicFeeTxV2Data to carry the FeeCurrency field through the encode/decode round trip, and wire it into all 5 switch sites: newSpanBatchTx, decodeTyped, convertToFullTx, recoverV, and convertVToYParity.

Resolves https://github.com/celo-org/celo-blockchain-planning/issues/1360

palango and others added 2 commits March 13, 2026 15:09
Span batch encoding/decoding failed on Celo CIP-64 transactions (type
0x7b) because the tx type switch statements only handled legacy, access
list, dynamic fee, and set code types.

Add spanBatchCeloDynamicFeeTxV2Data to carry the FeeCurrency field
through the encode/decode round trip, and wire it into all 5 switch
sites: newSpanBatchTx, decodeTyped, convertToFullTx, recoverV, and
convertVToYParity.
@palango palango requested review from karlb and piersy March 25, 2026 12:00
Copy link

@karlb karlb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Too bad this isn't just adding a CeloDynamicFeeTxV2Type to a list. The diff isn't short, but at least it is quite simple.

@palango
Copy link
Author

palango commented Mar 25, 2026

Tests only fail on RPC limits.

@palango palango merged commit db898d3 into celo-rebase-16 Mar 25, 2026
60 of 61 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants