-
Notifications
You must be signed in to change notification settings - Fork 31
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
Add optional 3rd party endpoints for tx broadcasting and reading the chain #521
Comments
Crucial for this issue is the case: boltz backend down and make uncooperative claims and refunds work via third party endpoints. Since cooperative path is always preferred we want to handle these similarly to boltz-client: |
This is currently blocked by lack of DiscountCT on Liquid mainnet, which we expect to be available in the next months. Then we can implement this. |
DiscountCT is available now. |
We want to enable users to broadcast and read the chain via 3rd party endpoints. But @michael1011 brought up a valid point as where some users might not want their transaction info to be sent to a third party and prefer to still broadcast via Boltz, so we probably want to allow changing endpoints via settings menu but stick with ours by default.
Options in settings menu:
CORS might be an issue as always. And we can't really do that before we have DiscountCT is available as our endpoints need to be used for lowball for now.
The text was updated successfully, but these errors were encountered: