-
-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(wallet): add Liquid Auth provider #215
feat(wallet): add Liquid Auth provider #215
Conversation
As mentioned privately, the BaseWallet's signTransaction method has an _indexesToSign argument. Because there are no examples I have not been sure how to best implement this. The current implementation simply maps through the tx:s: |
The It exists as an optional "filter" only if you want to tell the wallet which specific transactions you want the user to sign. Each transaction in the group is inspected and only marked for signature if:
If any of those conditions are false then it will not be presented for signature. |
Hi @drichar, as we spoke on Discord it is optional and it's handled internally within the use-wallet-client repo so I believe it can be left to the side for now. |
Adds Liquid-Auth-Js (abstracted behind Liquid-Auth-Use-Wallet-Client, name open to change!), to allow for the demo Liquid Auth Android app to be used for demonstrative purposes. Similar to the Wallet Connect example wallet/provider.
Liquid Auth requires a backend-api which is included in this PR. Namely, the liquid-auth-backend examples folder. It comes with a docker compose yaml file with instructions on how to set things up using Ngrok to host the Liquid Auth backend and tunnel through to a URL accessible publicly provided by Ngrok.
The docker-compose also includes an Nginx container that, besides doing reverse proxy stuff, also hosts the static files generated the example frontends. By default it is the vanilla-ts that is hosted.
Examples: