Magic signer

[Ethella]

Hi Tezart team, this is Jerry from Magic Link. 👋

Per requests from our customers, we are trying to support Tezos on Flutter with our key management infrastructure. And your library has been recommended by our customers.

However, within your implementation, there's been a challenge for us to integrate a remote signer from a third party like us. So I added a RemoteSigner param in Keystore to sign remotely, and I've tested it locally to make sure it works. The example will be documented on our docs.magic.link website

Hope you can adopt this change, and I can guide our clients to use your awesome libraries with our Magic Auth. Please lmk if there's anything that I need to update. I'll make up the tests after you guys are agreeing on the implementation.

[Pierre-Michard]

Hi Ethella,
thanks for your contribution.
I don't see the package blockchain_signer you've added to the project anywhere. Is that a public project?
By the way, would it be possible to avoid adding such a dependency, by using a generic interface, which could fit to other remote signers?

[Ethella]

Hi @Pierre-Michard!

The package blockchain_signer is currently in review right now. We'll publish it once it's consolidated. https://github.com/magiclabs/blockchain-mobile-signer/pull/1/files.

As you can see from the links above, it's a lightweight generic interface and it may support Ledger Signer and InMemeory Signers. Based on our plan, we want to gradually iterate on it to support the rest of the collaborative chains for Flutter.

The reason why we make a it a standalone library is because, from our experience, our customers have requested multiple times about decoupling blockchain libraries and our sdks to make it lightweight and flexible.

Please let me know your thoughts

[Ethella]

Thx for merging this! Can we direct our flutter Tezos customers to you?