Addresses

One would think that addresses would be resolved by now and chains would have uniform handling of this by now. That is not the case at all.

For a formal specification of how Union handles addresses, check the docs.

TLDR

Cosmos addresses use bech32 encoding with this format:

{HRP}1{address}{checksum}

The human readable part (hrp) differentiates between chains (like union or stars). It's followed by the number 1, then the address, and finally a 6 byte checksum.

When querying transfers across multiple chains for address union1abc...123, searching for that specific string would miss transfers from the same address on other chains like stars1abc...xyz.

Union's SDKs and APIs solve this by supporting searches by:

• display style (chain-specific format shown in browsers)
• canonical format (without hrp/chain-specific info)

You can query the API to see all versions of an address:

gq https://development.graphql.union.build/v1/graphql -q '
query GetAddressTypesForDisplayAddress {
  v2_util_get_address_types_for_display_address(args: {
    p_display_address: "union1d03cn520attx29qugxh4wcyqm9r747j64ahcj3"
  }) {
    display
    canonical
    zkgm
  }
}
'

nix shell nixpkgs#nodePackages.graphqurl

Your query should return exactly the following data.

{
  "data": {
    "get_address_types_for_display_address": [
      {
        "display": "union1d03cn520attx29qugxh4wcyqm9r747j64ahcj3",
        "canonical": "0x6be389d14fead665141c41af576080d947eafa5a",
        "zkgm": "0x756e696f6e31643033636e353230617474783239717567786834776379716d39723734376a36346168636a33"
      }
    ]
  }
}