This repository has been archived by the owner on Apr 25, 2024. It is now read-only.
chore: s/blockstream.info/mempool.space/g #347
Merged
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
humanumbrella
previously approved these changes
Nov 8, 2023
waldenraines
force-pushed
the
mempool.space
branch
from
fad031d to
964376a
Compare
|
@humanumbrella rebased and fixed conflicts, please re-approve |
humanumbrella
previously approved these changes
Nov 18, 2023
|
New conflict to resolve then we should be good to go. |
waldenraines
force-pushed
the
mempool.space
branch
from
964376a to
6fd0c5f
Compare
|
@bucko13 updated! |
bucko13
approved these changes
Nov 20, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Replace a couple of usages of blockstream.info with mempool.space. Should be merged after unchained-capital/unchained-bitcoin#99.
Also remove delay hack added in d9774c1 as it's not needed now that we're using mempool.space.
Does this PR introduce a breaking change?
Does this PR fix an open issue?