Backend block tip height endpoint #3687
Merged
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
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.
Previously:
Using esplora:
/api/blocks/tip/height-> esplora/api/v1/blocks/tip/height- not implementedUsing bitcoind only.
/api/blocks/tip/height-> asking bitcoind for height/api/v1/blocks/tip/height- asking bitcoind for heightWith this PR.
Using esplora:
/api/blocks/tip/height-> esplora/api/v1/blocks/tip/height- returning current block height from mempool backendUsing bitcoind only.
/api/blocks/tip/height-> returning current block height from mempool backend/api/v1/blocks/tip/height- returning current block height from mempool backendRunning Mempool backend with Esplora and accessing the 2 different /api/ and /api/v1/ blocks/tip/height endpoints now showing different heights during sync