Best Practices
When integrating with FuturePass, adhering to these best practices is crucial for ensuring a secure, efficient, and seamless user experience. These practices focus on utilizing FuturePass addresses, managing transaction fees, and handling bridging processes effectively.
Experiences use the FuturePass Address by default and avoid using EOAs It is essential to default to using FuturePass addresses rather than EOAs. Since all assets on the root are owned by the user's FuturePass address, utilizing FuturePass addresses ensures a consistent and secure asset management process. It is recommended to configure your experience to interact exclusively with FuturePass addresses, ensuring the security and integrity of users' assets.
Implement fee proxy and use gas in FuturePass 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 FuturePass 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 FuturePass Address by default All bridging activities should default to the FuturePass address. For example, when a user transfers an asset from one network to another, the destination should be their FuturePass 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 FuturePass address should be shown, hiding any custodial or Xaman EOAs to avoid confusion.
Last updated