feat: implement Ethereum, Polygon and Bitcoin with phantom

[NeOMakinG]

Issue

• closes https://github.com/shapeshift/hdwallet/issues/675

gomes notes:

• ⚠️ Test me alongside its web fren (https://github.com/shapeshift/web/pull/7766) performing the regular verdaccio business

• Two spotted issues with Phantom:

  • Polygon is drunk, confirmed to be an upstream issue and not an us issue as I could repro with direct window.ethereum.request() calls in console https://github.com/orgs/phantom/discussions/294
  • BTC outputs isn't parsed properly in Phantom confirm screen - seemingly not an us issue (though it may be, we may or may not be doing something wrong with PSBTs, but the Tx itself/advanced view with inputs/outputs is happy) https://github.com/orgs/phantom/discussions/293

neo notes:

First of all, I was thinking that the concept was pretty similar to metamask with snap at some point, so I started from this package.

The EVM part is following the EIP-1193 standard as stated in https://docs.phantom.app/ethereum-and-polygon/getting-started , so the implementation is very similar to any wallets as MetaMask.

Providers

Phantom as multiple providers, this is kinda why I had to store them all in memory, to communicate with the bitcoin part, we need to use the bitcoin provider. We only have a single provider for every EVM supporteds.

BTC TX

Phantom require to build the TX using PSBT, the logic is kinda like Native

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
hdwallet	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 20, 2024 9:59pm