<aside> <img src="/icons/help-alternate_purple.svg" alt="/icons/help-alternate_purple.svg" width="40px" /> FAQ

• Why is this needed?
• What are the risks? How can they be mitigated?
• What happens if I don’t adopt DOT as a gas token?
• What are the next steps? </aside>

GM 👋

This guide will showcase how you can integrate DOT into your chain so that it can be used as a fee token. We will cover two main methods to doing this, allowing you to choose the one that suits you and your project best.

Support from Remy & Cisco from Parity Engineering and multiple technical ecosystem agents will be available throughout the integration process.

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

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.

</aside>

<aside> <img src="/icons/checkmark_blue.svg" alt="/icons/checkmark_blue.svg" width="40px" />

Use the checklist to not forget anything while upgrading!

</aside>

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

If you’d like to explore ‘why’ Polkadot benefits from universally supporting DOT as a fee token, then please see the forum post which can be found here. This provides a high-level overview of the key pain points, how we can solve it and the benefits to the ecosystem.

</aside>

Table of Content

Integration Guides

Method 1 - Integrating DOT natively into your runtime

Introduction

Integrating DOT natively into your runtime. This method allows the parachain to natively accept DOT as a gas fee in the runtime without swaps.

Pros

No need to configure pallet_asset_conversion and set up liquidity pools.