Prototype Hydra provider #218
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Piefayth
force-pushed
the
hydra-provider
branch
from
366e7cc
to
c09dd5d
Compare
Piefayth
force-pushed
the
hydra-provider
branch
from
c09dd5d
to
1f423e4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I wanted this, so I took a stab at it.
Calling from the browser requires that the Hydra node is proxied through something that can provide CORS support.
All
utxorelated functions must retrieve the entire utxo set from Hydra each time, unless we want the provider to be stateful. I think this is fine, though, the set should be reasonably sized in Hydra.