Topic Title: Best practices for adding a custom network + token (Efikcoin Eternal) to MetaMask automatically from a dApp

Smart Accounts
, , , ,
1

  • Integration details: What are you building and where are you integrating Smart Accounts?

  • Describe problem/question: What is the specific issue or question?

  • Code snippets: Copy relevant code and config.

  • Exact error and logs: Add any error output or console messages.

  • Package details: Mention SDK version and related dependencies.

Hello fellow devs,

I’m building a project called Efikcoin Eternal – a token on (which chain? e.g., BSC, Polygon, Ethereum). I want users to be able to add both the custom network and the token to MetaMask with one click from my dApp.

I know about window.ethereum.request({ method: ‘wallet_addEthereumChain’, params: […] }) and wallet_watchAsset for the token.

My questions to the community:

1. What’s the most reliable way to detect if the network is already added before prompting the user?

2. For a new token with no CMC or trust‑wallet asset listing yet, are there any pitfalls with wallet_watchAsset?

3. Has anyone successfully combined both network‑add and token‑add in one user flow without errors?

4. Any security tips for preventing phishing warnings on custom networks?

Would love to hear your experi

ences. Thanks!