Best Practices

When integrating with Auth, adhering to these best practices is crucial for ensuring a secure, efficient, and seamless user experience. These practices focus on utilizing Auth addresses, managing transaction fees, and handling bridging processes effectively.

Experiences use the Auth Address by default and avoid using EOAs

It is essential to default to using Auth addresses rather than EOAs. Since all assets on the root are owned by the user's Auth address, utilizing Auth addresses ensures a consistent and secure asset management process. It is recommended to configure your experience to interact exclusively with Auth addresses, ensuring the security and integrity of users' assets.

Implement fee proxy and use gas in Auth Address by default

Experiences should implement a fee proxy, that allows users to pay transaction fees using their choice of tokens. This enhances user flexibility and convenience.

As root assets are managed through the Auth address, it is recommended that gas fees also be paid from this address. This centralizes the management of transactions and simplifies the process for users.

Bridging to Auth Address by default

All bridging activities should default to the Auth address. For example, when a user transfers an asset from one network to another, the destination should be their Auth address to maintain consistent asset management.

Avoid using custodial and Xaman EOA’s in the UI

Custodial and Xaman EOAs should not be used or visible in the user interface. For example, when displaying wallet information or transaction history, only the Auth address should be shown, hiding any custodial or Xaman EOAs to avoid confusion.