Skip to content

Conversation

@Tristan-Wilson
Copy link
Member

@Tristan-Wilson Tristan-Wilson commented Dec 18, 2025

Arbitrum needs to track all addresses touched during transaction execution to support address-based filtering at the sequencer level. This enables compliance use cases on certain chains where transactions interacting with certain addresses must be rejected before inclusion.

The implementation follows the existing arbTxFilter pattern in ArbitrumExtraData, adding a touchedAddresses map that collects addresses during execution. Three methods are added to the StateDB interface: AddTouchedAddress, GetTouchedAddresses, and ClearTouchedAddresses. The collection is automatically cleared at transaction boundaries via SetTxContext.

pulled in by OffchainLabs/nitro#4157

fixes: NIT-4221

Arbitrum needs to track all addresses touched during transaction
execution to support address-based filtering at the sequencer level.
This enables compliance use cases where transactions interacting with
certain addresses must be rejected before inclusion.

The implementation follows the existing arbTxFilter pattern in
ArbitrumExtraData, adding a touchedAddresses map that collects
addresses during execution. Three methods are added to the StateDB
interface: AddTouchedAddress, GetTouchedAddresses, and
ClearTouchedAddresses. The collection is automatically cleared at
transaction boundaries via SetTxContext.
@Tristan-Wilson Tristan-Wilson changed the title Add touched address tracking to StateDB for tx filtering [core] Add touched address tracking to StateDB for tx filtering Dec 18, 2025
@Tristan-Wilson Tristan-Wilson changed the title [core] Add touched address tracking to StateDB for tx filtering core: Add touched address tracking to StateDB for tx filtering Dec 18, 2025
@Tristan-Wilson Tristan-Wilson marked this pull request as ready for review December 18, 2025 16:39
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.

3 participants