Ethereum Foundation pushed a standards-level fix to EIP-8130, correcting sentinel address values that implementers depend on for compliant contract behavior.

# -----------------------------------------------------------
# EIP-8130 Sentinel Address Audit Walkthrough
# -----------------------------------------------------------
# This walkthrough helps you verify your codebase is aligned
# with the corrected sentinel addresses from the latest
# EIP-8130 update.
#
# Step 1: Pull the updated EIP and identify the corrected
# sentinel address values.
#
# Visit: https://github.com/ethereum/EIPs/pull/<PR_NUMBER>
# or:    https://eips.ethereum.org/EIPS/eip-8130
#
# Look for the sentinel address constants. Example (pseudo):
#
# OLD_SENTINEL = 0x0000000000000000000000000000000000000001  # ← previously published, now incorrect
# NEW_SENTINEL = 0x<corrected_value_from_updated_spec>        # ← current correct value

# Step 2: Grep your Solidity contracts for the old value.
# In your project root:
#
# grep -rn "0x0000000000000000000000000000000000000001" contracts/
#
# Any hits in EIP-8130-related logic need to be updated.

# Step 3: Update the constant in your Solidity source.
#
# // SPDX-License-Identifier: MIT
# pragma solidity ^0.8.24;
#
# contract EIP8130Registry {
#     // ✅ Updated sentinel per corrected EIP-8130 spec
#     address constant SENTINEL = 0x<corrected_value_from_updated_spec>;
#
#     mapping(address => address) internal _linked;
#
#     function isSentinel(address addr) public pure returns (bool) {
#         return addr == SENTINEL;
#     }
# }

# Step 4: Update your test assertions.
#
# // In your Foundry test file:
# function test_sentinelMatchesSpec() public {
#     // This should now assert against the NEW corrected value
#     assertEq(
#         registry.SENTINEL(),
#         0x<corrected_value_from_updated_spec>
#     );
# }

# Step 5: Run your full test suite and look for failures.
#
# forge test -vvv
#
# Any test that was passing against the old sentinel value
# and now fails is a test that was silently wrong — fix the
# test AND the implementation.

# Step 6: If you publish an SDK or library that exposes
# EIP-8130 constants (TypeScript, Python, etc.), update there too.
#
# // TypeScript example
# export const EIP_8130_SENTINEL = "0x<corrected_value>" as `0x${string}`;
#
# # Python example
# EIP_8130_SENTINEL = "0x<corrected_value>"

# Step 7: Pin the EIP commit hash in your documentation
# so future auditors can verify which spec version you built against.
#
# // In your README or natspec:
# // EIP-8130 spec reference: https://github.com/ethereum/EIPs/commit/<hash>
# -----------------------------------------------------------