question: How it will look like in production for the user

[hBulldozer]

I got the metamask Flask api and the snaps will work for developer mode and testing, but I didn't understand how it would go for production and for users.

I read that some snaps can go for the Metamask official extension, is this the way? So users can add Hathor Network as a custom chain on the usual web extension?

Or the idea is to build a custom wallet extension for Hathor using this api and metamask flask as base? I read that metamask flask may not work if the user has metamask installed so I was confused, can someone explain how this planned to arrive for the users?

[andreabadesso]

Hey @hBulldozer,

We're still evaluating some options for our web wallet, Snaps are one of them and this repo is a proof-of-concept that is still in progress

You're indeed correct, it's only available on the Flask version of MetaMask (which is only available for developer preview), so it's not yet deployed to the production MetaMask extension

I read that some snaps can go for the Metamask official extension, is this the way?

When the Snaps feature is released, users can choose which Snap to install, Snaps are packages published in npm (and in the future other sources)

So users can add Hathor Network as a custom chain on the usual web extension?

No, snaps are basically javascript programs that run inside of MetaMask, in an isolated environment, you can read more about it here, so it's not the same process as adding a new EVM network like BSC for instance, you would have to install the hathor snap so the dApps can communicate with it

[hBulldozer]

Thanks for the clarification Andre!
We are building our dApp on Hathor, so we are eager to see the solution for this connection.
As soon as you need beta testers, you can count on us, thanks!