Skip to content

Clarify wrapped/unwrapped address naming in token registry #5

Open

Description

@thedavidmeister

While cross-referencing the token registry against on-chain state, the address field in each token entry is the wrapped vault (ERC-4626), and extensions.unwrappedAddress is the receipt vault (ERC-20). However, the field naming is ambiguous — "unwrapped" in the registry means the receipt vault, but the actual addresses users interact with on st0x.io are the wrapped vaults.

This creates confusion when the site displays token addresses without clarifying which layer of the stack they represent:

  • Receipt (ERC-1155)
  • Receipt vault / "unwrapped" (ERC-20, e.g. tMSTR)
  • Wrapped token vault (ERC-4626, e.g. wtMSTR)

The registry currently only tracks wrapped and unwrapped addresses. The ERC-1155 receipt contract address is not included at all.

Suggestion: Either rename unwrappedAddress to something unambiguous (e.g. receiptVaultAddress) and add a receiptAddress field, or add a comment/docs clarifying the naming convention.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions