Repository navigation
Conversation
hieblmi
force-pushed
the
hai/loop-tapsdk-legacy
branch
from
November 2, 2026 16:00
cc2d620 to
5866ad6
Compare
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
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.
Superseded by the official tap-sdk v0.1.1 release, which provides the v0.3.0 API and the required fixes on pre-btcd-v2 Bitcoin dependencies.
The local
loop/tapsdkimplementation has been removed from the active swapkit PR #1225. That PR directly requires the release and retains Loop's contracts, policy, recovery helpers and caller-owned gRPC connection adapter inswapkit/tapsdk.This base PR no longer needs to be merged.