How Does a New Wallet Get Added to a dApp’s List of Support Wallets?
How Does a New Wallet Get Added to a dApp’s List of Support Wallets?
Loading saved threads...
Jackson Kelley · External communityPost link
External question — Ethereum Stack Exchange
Author: Jackson Kelley
Original post: https://ethereum.stackexchange.com/questions/145660
License: CC BY-SA 4.0 — https://creativecommons.org/licenses/by-sa/4.0/
Adaptation: HTML converted to plain text; contact email addresses removed.
Let's say I have a new wallet that I've created and I wanted it to show up next to Metamask whenever a user clicks "Connect Wallet" on a dApp front-end as another wallet option. What is the procedure for doing this?
Quote
Report
Wuzhong - DevEx · External communityPost link
External answer — Ethereum Stack Exchange
Author: Wuzhong - DevEx
Original post: https://ethereum.stackexchange.com/a/147125
License: CC BY-SA 4.0 — https://creativecommons.org/licenses/by-sa/4.0/
Adaptation: HTML converted to plain text; contact email addresses removed.
This is related to
EIP-1193
which allows Dapp to interact with different providers. Essentially, your wallet should follow the standard to be compatible with the Dapp in the market.
Taking
Metamask
as an example, after it is installed, there is a global object available at the front-end named Ethereum.
//Have to check the ethereum binding on the window object to see if it's installed
const { ethereum } = window;
Dapps interact with this object to interact with the blockchain without knowing the users' private keys and other sensitive information. If additional information is required, Webapp can retrieve it through Metamask's APIs.
As others suggest, if you don't own the Dapp, you need to talk to the owner to add your wallet as one of the options.
Hope this helps, happy coding.
Quote
Report
prc · External communityPost link
External answer — Ethereum Stack Exchange
Author: prc
Original post: https://ethereum.stackexchange.com/a/147181
License: CC BY-SA 4.0 — https://creativecommons.org/licenses/by-sa/4.0/
Adaptation: HTML converted to plain text; contact email addresses removed.
The short answer is you can't. The dApp frontend controls the shots there, so the only way is to have them integrating with your wallet, which is not that easy to accomplish.
But the good thing is that maybe there's another way. Maybe you can make your wallet support some standard connection method, that is common to all major dApps, possibly including that one you are targeting.
Maybe
WalletConnect
fits the bill, so you can implement support for it in your wallet and this opens your wallet to all major dApps in web3.
Quote
Report
Post Reply
Quoted from Forex.com.bd-Editorial External answer — Ethereum Stack Exchange Author: Wuzhong - DevEx Source score (net votes, not local likes): 0 Original post: https://ethereum.stackexchange.com/a/147125 License: CC BY-SA 4.0 — https://creativecommons.org/licenses/by-sa/4.0/ Adaptation: HTML converted to plain text; contact email addresses removed. This is related to EIP-1193 which allows Dapp to interact with different providers. Essentially, your wallet should follow the standard to be compatible with the Dapp in the market. Taking Metamask as an example, after it is installed, there is a global object available at the front-end named Ethereum. //Have to check the ethereum binding on the window object to see if it's installed const { ethereum } = window; Dapps interact with this object to interact with the blockchain without knowing the users' private keys and other sensitive information. If additional information is required, Webapp can retrieve it through Metamask's APIs. As others suggest, if you don't own the Dapp, you need to talk to the owner to add your wallet as one of the options. Hope this helps, happy coding.
Checking account access…