🏦Additional Compatible Wallets Setup
Additional Wallets That Are Compatible With PHI Smart Chain. A Step By Step Guide To Connect Your Favorite 3rd Party & Open-source Wallets To PHI Smart Chain.
Last updated
Additional Wallets That Are Compatible With PHI Smart Chain. A Step By Step Guide To Connect Your Favorite 3rd Party & Open-source Wallets To PHI Smart Chain.
Last updated
Connection Details
You will need to setup your wallet in order to use PHI Smart Chain, and you can use the parameters below to configure it with your preferred wallet provider. If you are using a private ledger, you will have to contact your server administrator to request the connection parameters of the network you are trying to connect to.
Fastest Way To Automatically Set Up Both Chains Within Any Web3 Wallet Is Go To
Connect Your Wallet Within Your Wallets Dapp Browser By Clicking "Metamask" Even If Your Inside Another Wallets Dapp Browser. Do This With Each Each Exchange & The Chains Will Be Automatically Added To Your Wallet.
Below You Will Find The Manual Connection Details.
Network Name: PHI
New RPC URL: https://connect.phi.network
Chain ID: 144
Symbol: Φ
Block Explorer: https://phiscan.com
For Your Convenience Copy & Paste The Listed Above Credentials In The Add Network Form.
We only recommend the usage of alternative RPCs for advanced users, or if the main RPC isn't working for you. Please get in touch with support team if you can't connect to the network. Some wallets - mostly on mobile devices - won't accept non-SSL RPCs.
If you have deployed and is trying to connect to a private ledger, you will have to setup your own RPC, and use a regular wallet to connect to it.The settings can change on a case-to-case basis, and more documentation with specific instructions will be produced once we have launched our private ledger applications suite.
If you want to deploy your own public RPC, you can liaise with the integration team so they can guide you through the process. Deploying a public RPC is a great public service to our community, as it effectively broadens our public connection bandwidth and ensures that users will still be able to interact with the network on an event where our public RPCs are down or overloaded.