<h2 id="summary">Summary</h2>
<p>This proposal aims to simplify and unify the address format across the Polkadot ecosystem to improve user experience and reduce user confusion. Currently, over 150 registered entries use different SS58 <span style="background-color: #000000;">address</span> prefixes, creating fragmentation and complicating the user experience.</p>
<p>This proposal is a result of multiple discussions which were consolidated in the polkadot forum. This post provides more detailed explanation and reasoning behind the proposed changes:</p>
<p><a href="https://forum.polkadot.network/t/unifying-polkadot-ecosystem-address-format/10042">https://forum.polkadot.network/t/unifying-polkadot-ecosystem-address-format/10042</a></p>
<p>🚧 This initiative falls under the UX Bounty scope and the necessary resources will be covered by its budget. You can find all relevant materials <a href="https://www.notion.so/braille-wtf/UXB-1-UX-Issue-1-Unified-Address-Format-9e7c414ae769471c9016c9d8463a4d49">here</a>.</p>
<h2 id="proposedchanges">Proposed Changes</h2>
<ul style="list-style-type: circle;">
<li>
<p>Adopt a unified SS58 address format for all compatible Polkadot parachains:</p>
<ul>
<li>Use Prefix:0 (addresses starting with '1') for all compatible chains that wish to connect to Polkadot ecosystem</li>
<li>This allows users to easily recognize their accounts across different chains</li>
</ul>
</li>
</ul>
<p>Implement readable address prefixes roughly based on <a href="https://eips.ethereum.org/EIPS/eip-3770">EIP-3770</a> to help prevent users from sending assets to the wrong chain</p>
<ul>
<li>This allows users to easily see the intended destination chain when copying address</li>
</ul>
<p>&nbsp; &nbsp; &nbsp; &nbsp;<img src="https://i.ibb.co/NYTBQKv/7eb16e0314f51c593e14306d7e2fec67b6142122.png" alt="readable-prefix" width="252" height="348" /></p>
<h2 id="benefits">Benefits</h2>
<ul>
<li>Simplifies user experience across the ecosystem</li>
<li>Reduces confusion caused by multiple address formats</li>
<li>Minimizes the risk of users sending assets to incorrect chains</li>
<li>Streamlines development processes for builders in the ecosystem</li>
</ul>
<h2 id="implementation">Implementation</h2>
<p>As a part of the UX bounty, we will do the following to ease implementation of this proposal:</p>
<ul>
<li>Create detailed guides for developers to ensure a seamless transition</li>
<li>Create specification for the prefix decoding</li>
<li>Develop explanatory documents and tools for users and developers to be able to provide support during the transition period (i.e. address conversion tool, prefix decoder)</li>
<li>Work with wallet providers, dApps, and exchanges to help them update their interfaces</li>
</ul>
<h2 id="notes">Notes</h2>
<ul>
<li>The wish for change serves as guidance; chains and dApps can choose their own prefixes, however this wish for change proposal aims to show, that the users of the Polkadot ecosystem wish to simplify the UX within the ecosystem and it is advisable to follow this change.</li>
</ul>
<h2 id="impact">Impact</h2>
<p>This change will significantly enhance the user experience within the Polkadot ecosystem, making it more accessible and user-friendly for both new and existing users. It will also reduce the complexity for developers building on the platform.</p>

Make some on-chain remark.

Can be executed by every `origin`.

- **Problem Statement:** Simplify and unify the address format across the Polkadot ecosystem to enhance user experience and reduce confusion.
- **Significance:** Over 150 registered entries currently use different SS58 address prefixes, leading to fragmentation and user confusion.
- **Proposed Solution:** Adopt a unified SS58 address format for all compatible Polkadot parachains and implement readable address prefixes based on EIP-3770.
- **Expected Outcomes:** Streamlined user experience, reduced confusion, minimized risk of sending assets to incorrect chains, and streamlined development processes for ecosystem builders.

#1217 [ Wish for change ] Unifying Polkadot Ecosystem Address Format

No Active Proposals