The Polkadot UX Bounty aims to improve the user experience across the Polkadot ecosystem by addressing UX issues and establishing best practices and standards. These guidelines are designed to help teams implement user-friendly solutions that reduce friction, enhance clarity, and promote ecosystem-wide cohesion.

Unified Address Format

<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" />

Read the full guide [UXB-1] - Unified Address Format - Integration Guide

</aside>

The current fragmentation of address formats in the Polkadot ecosystem—over 150 SS58 prefixes—creates unnecessary complexity and confusion for users. Unifying the address format will simplify interactions, reduce developer workloads, and enhance the ecosystem's competitiveness.

Best Practices for Implementing a Unified Address Format

  1. Notify Stakeholders: Inform wallets, CEXs, on/off ramps, and ecosystem tools about the upgrade to the new address format.
  2. Coordinate with Wallets: Ensure wallet teams implement necessary changes before proceeding with the transition.
  3. Address CEX Compatibility: Work with CEXs to update their systems and provide an option to copy the old address format temporarily.
  4. User Notifications: Use non-intrusive notifications to prepare users for the change, offering clear explanations.
  5. Support Both Formats Temporarily: Allow components handling addresses to display and input both old and new formats during the transition.
  6. Validate Address Inputs: Implement robust validation to prevent incorrect address usage.
  7. Preventive Measures: Warn users to avoid sending funds to unsupported CEXs or chains.
  8. Update Documentation: Ensure all technical documentation, SDKs, and wikis reflect the new address format.

DOT as a Gas Fee Token

<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" />

Read the full guide [UXB-2] - DOT as a Universal Fee Token - Integration Guide

</aside>

The requirement for users to hold native tokens for every parachain they use presents a significant UX barrier. Allowing DOT to function as a gas fee token everywhere will streamline liquidity, improve onboarding experiences, and prevent issues like trapped assets.

Best Practices for Integrating DOT as a Gas Fee Token

  1. Choose the Right Integration Method: