feat: bitgo #76
Open
feat: bitgo #76
Conversation
This file contains hidden or 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
Polybius93
force-pushed
the
feat/bitgo-dlc-handler
branch
from
aefe4d3 to
3741416
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.
This PR adds the BitGo DLC Handler, which enables handling of Vault transactions using BitGo’s 2-of-3 multisig scheme nested within a 2-of-2 multisignature setup. It integrates with the BitGo API for signature orchestration.
At this stage, the implementation is limited to Bitcoin-related operations only.
BitGo packages during development were local, with the latest commit of:
758777c94dbcc6d1008ecc36c11c2d45b2457d1bSo API might be out of date since then.