Currently, the address field expects addresses to start with 0x. However, on the XDC network, addresses can also be formatted using the xdc prefix instead of 0x. Some users may encounter issues or UI confusion (e.g., buttons greyed-out) when using these valid xdc-prefixed addresses.
Please update address validation and relevant UI to also accept and correctly handle xdc-prefixed addresses, to ensure compatibility with official XDC tokens and wallets.
Additional context: XDC addresses formatted with xdc prefix are still valid and supported in the ecosystem. Users copying addresses in this format should not experience errors or rejections, provided the address and the token are both supported.
Potential enhancement:
- Accept both
0x and xdc prefixes for addresses on XDC network
- Warn users if they attempt to use a non-official or "mocked" token
See Slack conversation for user reports and original thread.
View original Slack conversation
Currently, the address field expects addresses to start with
0x. However, on the XDC network, addresses can also be formatted using thexdcprefix instead of0x. Some users may encounter issues or UI confusion (e.g., buttons greyed-out) when using these validxdc-prefixed addresses.Please update address validation and relevant UI to also accept and correctly handle
xdc-prefixed addresses, to ensure compatibility with official XDC tokens and wallets.Additional context: XDC addresses formatted with
xdcprefix are still valid and supported in the ecosystem. Users copying addresses in this format should not experience errors or rejections, provided the address and the token are both supported.Potential enhancement:
0xandxdcprefixes for addresses on XDC networkSee Slack conversation for user reports and original thread.
View original Slack conversation