ERC-6538 primary sources

Primary source packet

URL: https://eips.ethereum.org/EIPS/eip-6538
Why it matters:
- Canonical statement of purpose: a standard way to store and retrieve an entity’s stealth meta-address.
- Makes the core split explicit: ERC-6538 extends ERC-5564 by standardizing the registry / discovery layer rather than the announcement-and-derivation mechanics.
- Confirms the singleton-per-chain design, direct registration path, delegated registration path, and nonce invalidation flow.

URL: https://raw.githubusercontent.com/ethereum/ERCs/master/ERCS/erc-6538.md
Why it matters:
- Best plain-text source for the exact Solidity reference implementation and interface.
- Shows the specific storage model: stealthMetaAddressOf[registrant][schemeId] plus nonceOf[registrant].
- Makes the EIP-712 domain-separator and EIP-1271 contract-signature support easy to inspect.

URL: https://ethereum-magicians.org/t/stealth-meta-address-registry/12888
Why it matters:
- Useful governance / design context for why a shared stealth meta-address registry was proposed separately from the stealth-address generation standard.
- Helps frame ERC-6538 as the registry companion to ERC-5564 rather than as an independent privacy scheme.

URL: https://raw.githubusercontent.com/ScopeLift/stealth-address-erc-contracts/main/README.md
Why it matters:
- Strong practical evidence that ERC-6538 is being treated as deployable shared infrastructure rather than a dormant spec.
- Lists canonical deployment addresses for the ERC6538 registry across mainnet and several L2s / sidechains.
- Shows that ecosystem tooling treats ERC-5564 and ERC-6538 as a paired contract surface.

URL: https://raw.githubusercontent.com/ScopeLift/stealth-address-sdk/main/README.md
Why it matters:
- Shows the registry layer in operational use: lookup of stealth meta-addresses, registration-payload preparation, announcement fetches, and scanning helpers.
- Good evidence that ERC-6538 is the discovery layer that downstream apps and wallets are expected to call.

ERC-6538 is not just an implementation footnote to ERC-5564.
It makes the registry/discovery layer explicit, which is analytically separate from stealth-address generation, announcement emission, and recipient-side key derivation.
That separation is exactly the kind of reusable mechanism insight the corpus wants to preserve: the privacy primitive and the canonical lookup surface are different control planes.