Finally Polkadot have this abstraction, it was indeed a pain in the ass for dummies.
Aye no doubt.

Hey [@Bayacat](fAGgdvAYwqCwpt3Wda1mzpACnNyESbfgfgvm1RLSudBsUEu-bifrost-polkadot)! 

Thank you for pushing this! 

We are working on this too through the UX Bounty with [Jakub](https://x.com/JakPanik) and [Nino](https://x.com/gosu128)

Let's connect so we can group up our efforts? 

Here's my [telegram](https://t.me/houdz) or my email: alex@braille.wtf

🫶

Hey [@Bayacat](fAGgdvAYwqCwpt3Wda1mzpACnNyESbfgfgvm1RLSudBsUEu-bifrost-polkadot), Jakub just published his proposal on the Polkadot forum

https://forum.polkadot.network/t/unifying-polkadot-ecosystem-address-format/10042

Hope you can join the discussion! 

# Background

In response to an earlier proposal on the Polkadot forum: https://forum.polkadot.network/t/ux-proposal-consensus-based-address-formats/6072

I think this is a good suggestion. As Bifrost is an active parachain , we can also follow up on the suggestions in this proposal and update our address format in UX to a more universal address format with stronger consensus.

# Format Selection

I suggest that the address format on the UX of both Bifrost-polkadot and Bifrost-kusama networks be modified uniformly. 

For Prefix, choose to use the `prefix:0` of the Polkadot relay chain.

Because when users come into contact with Polkadot, they often first acquire DOT assets, or interact with system parallel chains such as Assethub. These chains currently show as `prefix:0` on polkadot.js. So I think `prefix:0` is the address format with the strongest consensus.

# UX Update Scope

The update of the address display format will not make any changes to the chain, nor will it affect any services on the current chain, but it involves a wide range of areas that need to be modified to maintain consistency, mainly in the following :

### Bifrost Team Responsible

- Bifrost Dapp
- Polkadot.js

Execution time: `2024-09-18 10:00 UTC+0`

### External coordination

- Subscan
- Subsquare
- Mimir
- Wallet
    - Nova
    - Talisman
    - Subwallet
- CEX
    - MEXC
    - Kucoin
    - Gate
    - Kraken
    - Coinex

Execution time: `2024-09-18 10:00 UTC+0` 

(It is recommended to synchronize, but it depends on the actual external communication and implementation. It can be allowed to be implemented later.)

# About chainspecs update

Since the entire proposal has not yet formed a broad consensus in the ecosystem, we can first update the non-on-chain content related to UX. We should be more cautious about on-chain information, and we can temporarily not update the relevant chainspecs.

# Proposal execution content

Since the proposal content is completely an off-chain operation, the proposal is marked for execution by remarking the link of this proposal post and a simple description on the chain.

- Bifrost is updating the way addresses are displayed on their platform.
- The new address format will be more universal and have stronger consensus.
- The update will not affect the chain or any services on it.
- Bifrost is responsible for updating their Dapp and Polkadot.js.
- Other external services like wallets and exchanges may also need to update their systems.

Proposal: Adjust Bifrost address to Consensus-Based Address Formats

Background

Format Selection

UX Update Scope

Bifrost Team Responsible

External coordination

About chainspecs update

Proposal execution content