Unifying Polkadot address format This initiative falls under the UX Bounty scope and the necessary resources will be covered by its budget. You can find all relevant materials here. As of today, there are over 150 registered entries in the Polkadot ecosystem using different SS58 address prefixes.…

Thank you very much for your professional advice. Our current plan is to prioritize complete UX changes without changing the information on the chain. We want to understand the potential risks and adverse experiences that will be caused by doing so (without updating the Runtime). We need to evaluate…

[image] josep: Of course! Let’s take Hydration as an example. Thanks, that was largely my understanding. I’m mostly curious about how the Prefix:42 - Substrate generic address format (usually starting with ‘5’) option opens the door to chains using “… their prefixes to prevent migration late…

[image] BayaCat: Our current plan is to prioritize complete UX changes without changing the information on the chain I strongly advise against this approach. Modifying the user experience without updating the corresponding on-chain data -specifically, the System.SS58Prefix constant- can lead …

I think this was misunderstood… I suggested chains wanting to connect to the Relay-chains or the ecosystem in other ways should use the respective Relaychian prefix to avoid migrating addresses later on.

[image] BayaCat: In addition, will updating the System.SS58Prefix constant affect other logic on the chain? Or is this just an independent factor? This doesn’t affect any runtime logic. (unless there is special custom logic handling SS58 which I think 99.9% of chains don’t do) But it can affe…

I think data representation should not be the users main concern. A resolver providing unified names and resolving underneath to the respective SS58 / H160 representation would be the easiest for the typical literate user. A resolver like this would also open up a unified dns like system based on u…

[image] 2075: A resolver like this would also open up a unified dns like system based on utf-8 / utf-16 and could be a combination of a web service and some authority pallet magic This would be beautiful addition on top of anything we have, but it’s not really part of this proposal and doesn’…

This will significantly improve both UX and security by helping users distinguish legitimate addresses from fraudulent ones. As a result, transaction validations become more accurate and user-friendly, enabling more efficient defense against growing sophisticated threats like clipper malware, as rec…

What about just using the public key 4fYrN4QvRaBf6HpWShZnFR7hNsGSEBHDw1115jYQqQE5SkTL on Centrifuge → becomes 0xba2c4540acac96a93e611ec4258ce05338434f12107d35f29783bbd2477dd20e 15D74LvQb6hVUBFoqXtveyYQ7Q7rFacV994Gw8PaAcpXKB2L on Polkadot → becomes 0xba2c4540acac96a93e611ec4258ce05338434f12107d35…

[image] mustermeiszer: What about just using the public key I was actually considering proposing this, however it might bring more problems. Address in this format is similar to ETH addresses, but it’s not compatible. It’s very long and I would argue harder to check for mistakes, with prefi…

Unifying Polkadot ecosystem address format

Ecosystem

IkerParity November 30, 2024, 10:03am 28

more info here: OpenUX Call #7 - 2024-11-28 - Meeting minutes

Topic		Replies	Views
UX Proposal: Consensus-Based Address Formats Tech Talk ux	54	3346	September 16, 2024
UX Bounty - Unified Address Format Update Ecosystem ux	1	151	September 23, 2025
Unifying Kusama ecosystem address format Ecosystem ux	7	234	December 20, 2024
What is substrate address? Can account holder receive/send funds using it? Tech Talk	15	2139	November 22, 2023
How will wallets work in JAM? Tech Talk	6	379	August 26, 2024

Unifying Polkadot ecosystem address format

Related topics