# Unifying Polkadot ecosystem address format

**URL:** <https://forum.polkadot.network/t/unifying-polkadot-ecosystem-address-format/10042>\
**Category:** Ecosystem\
**Tags:** ux\
**Created:** [September 16, 2024, 3:02pm UTC](https://forum.polkadot.network/t/unifying-polkadot-ecosystem-address-format/10042 "2024-09-16T15:02:57Z")\
**Posts on this page:** 10\
**Page:** 2

<div class="post-metadata">

**Author:** ![sodazone](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/sodazone/32/7216_2.png) [@sodazone](https://forum.polkadot.network/u/sodazone)\
**Post date:** [September 26, 2024, 7:45pm UTC](https://forum.polkadot.network/t/unifying-polkadot-ecosystem-address-format/10042/21 "2024-09-26T19:45:48Z")

</div>

Depending on the kind of account (e.g. proxy, multisig) there’s no public keys, but can be represented as “public key”. If we stick to the notion of address ito public key should be okay IMHO. Not a public key but can be unequivocally represented by a bit string of the same size.  
Of course, you won’t be able to recover a public key from “pseudo public key addresses” of a signature, this could be a concern. Well, in fact signatures are impossible for such addresses that doesn’t represent a public key.

---

<div class="post-metadata">

**Author:** ![joepetrowski](https://avatars.discourse-cdn.com/v4/letter/j/2acd7d/32.png) [@joepetrowski](https://forum.polkadot.network/u/joepetrowski)\
**Post date:** [September 27, 2024, 4:57am UTC](https://forum.polkadot.network/t/unifying-polkadot-ecosystem-address-format/10042/22 "2024-09-27T04:57:23Z")

</div>

I would be against just using the public key (or 32-byte `AccountId`). The SS58-encoded address also includes a checksum, which has a few nice user-protection properties.

One, it protects users against missed/altered characters. If you miss or change a character in the address, the whole address becomes “wrong” and UIs would reject it as a bad address (go to a UI and try it).

Second, there was a case a while back where someone pasted in an 20-byte Ethereum address and the UI just padded it with 12 bytes of 0s to make it into a Polkadot `AccountId`. This was obviously inaccessible.

The encoding with the checksum (besides being a bit shorter and easier on the eyes) also protects users from these mistakes.

---

<div class="post-metadata">

**Author:** ![Thebicsam](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/thebicsam/32/2999_2.png) [@Thebicsam](https://forum.polkadot.network/u/Thebicsam)\
**Post date:** [September 28, 2024, 9:13am UTC](https://forum.polkadot.network/t/unifying-polkadot-ecosystem-address-format/10042/23 "2024-09-28T09:13:44Z")

</div>

Using just **JUST ONE WALLET ADDRESS** for all parachain if possible PLEASE  
No difference prefix please, it is still too complicated

---

<div class="post-metadata">

**Author:** ![Thebicsam](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/thebicsam/32/2999_2.png) [@Thebicsam](https://forum.polkadot.network/u/Thebicsam)\
**Post date:** [September 28, 2024, 9:16am UTC](https://forum.polkadot.network/t/unifying-polkadot-ecosystem-address-format/10042/24 "2024-09-28T09:16:19Z")

</div>

100% support this if possible in technical

---

<div class="post-metadata">

**Author:** ![jak-pan](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/jak-pan/32/1962_2.png) [@jak-pan](https://forum.polkadot.network/u/jak-pan)\
**Post date:** [October 14, 2024, 12:24pm UTC](https://forum.polkadot.network/t/unifying-polkadot-ecosystem-address-format/10042/25 "2024-10-14T12:24:50Z")

</div>

This is now in pre-voting [[Wish for change] Unifying Polkadot Ecosystem Address Format | Polkassembly](https://polkadot.polkassembly.io/referenda/1217) (Still needs the deposit)

---

<div class="post-metadata">

**Author:** ![AurevoirXavier](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/aurevoirxavier/32/7225_2.png) [@AurevoirXavier](https://forum.polkadot.network/u/AurevoirXavier)\
**Post date:** [November 27, 2024, 3:58am UTC](https://forum.polkadot.network/t/unifying-polkadot-ecosystem-address-format/10042/26 "2024-11-27T03:58:53Z")

</div>

The referenda was approved.

Is there any strategy or timeline for what’s next?

---

<div class="post-metadata">

**Author:** ![jak-pan](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/jak-pan/32/1962_2.png) [@jak-pan](https://forum.polkadot.network/u/jak-pan)\
**Post date:** [November 29, 2024, 2:41pm UTC](https://forum.polkadot.network/t/unifying-polkadot-ecosystem-address-format/10042/27 "2024-11-29T14:41:20Z")

</div>

The wish for change successfully passed with overwhelming support and the dApp integration guide is under review. Once the review concludes early next week, we will push it with all the information on how to integrate this change.

cc @AurevoirXavier

---

<div class="post-metadata">

**Author:** ![IkerParity](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/ikerparity/32/88_2.png) [@IkerParity](https://forum.polkadot.network/u/IkerParity)\
**Post date:** [November 30, 2024, 10:03am UTC](https://forum.polkadot.network/t/unifying-polkadot-ecosystem-address-format/10042/28 "2024-11-30T10:03:17Z")

</div>

more info here: [OpenUX Call #7 - 2024-11-28 - Meeting minutes](https://forum.polkadot.network/t/openux-call-7-2024-11-28-meeting-minutes/10999)

---

<div class="post-metadata">

**Author:** ![Alex\_Houdz](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/alex_houdz/32/3042_2.png) [@Alex\_Houdz](https://forum.polkadot.network/u/Alex_Houdz)\
**Post date:** [January 21, 2025, 6:10pm UTC](https://forum.polkadot.network/t/unifying-polkadot-ecosystem-address-format/10042/29 "2025-01-21T18:10:15Z")

</div>

Hey everyone, ICYMI, we have published a [comprehensive guide](https://www.notion.so/braille-clients/UXB-1-Unified-Address-Format-Integration-Guide-149e1c2781f380978125d51d8d21017a?pvs=25) and a [checklist](https://www.notion.so/braille-clients/UXB-1-Unified-Address-Format-Checklist-12de1c2781f380f48b50efebd2dfa7f5) to help upgrading to the new address format.

If you need help or have any question you can also contact us in this [Support channel on Telegram.](https://t.me/+Fq1WpfW5LEdkNTU8)

---

<div class="post-metadata">

**Author:** ![Alex\_Houdz](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/alex_houdz/32/3042_2.png) [@Alex\_Houdz](https://forum.polkadot.network/u/Alex_Houdz)\
**Post date:** [May 21, 2025, 3:45pm UTC](https://forum.polkadot.network/t/unifying-polkadot-ecosystem-address-format/10042/30 "2025-05-21T15:45:42Z")

</div>

Hello all!

Today marks the beginning of the ugprade season starting with Hydration that just did it this morning 🥳

_(Shoutout to Bifrost and Hyperbridge for already using the right format)_

–

Here’s a TL;DR update:

Out of **27** rollups contacted  
✅ **5** are already using the new format

🕒 **11** acknowledged and will upgrade (ETA pending)

❌ **11** haven’t responded yet

–

👉 Read the [full update on X.](https://x.com/PolkadotUX/status/1925211003970523300)  
👉 Review the [tracker](https://docs.google.com/spreadsheets/d/1p0_-GfA4IBR0dAZzJHBGSLbrAnGJcBseIAW9JRjCugM/edit?gid=187140610#gid=187140610)

[Previous page](https://forum.polkadot.network/t/unifying-polkadot-ecosystem-address-format/10042.md?page=1)
