API server refactor & fee features #26
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
Avoid sending large block data messages over websocket, which block transaction updates, especially on lower bandwidth connections. Instead, only send the block id over websocket, and then fetch over http with good caching
Fetch prevouts for solo and block transactions, and calculate input values & tx fees. Naive initial implementation with no caching, so block processing is sloooooooooooooow.
API: - Better RPC handling (cache credentials) - Process transaction prevouts in dedicated Tasks - Consume ZMQ sequence msgs - Track mempool count precisely - Cache prevouts for mempool transactions - Send mempool count with every client msg, instead of reconstructing client-side - Only send block ids over websocket, let clients fetch the full block data via http Client: - Simplify transaction queue to avoid setTimeouts - improves experience in background tabs - no longer need to hold back txs, as duplicates are now handled API-side - Use API-supplied mempool count, instead of tracking it client-side - Make mempoolCount a Svelte spring store, so updates transition smoothly
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.
Big refactor of the backend API server to enable extension of transactions with prevout data and calculation of transaction fees, as well as:
Front end display of fees and feerates in the TxInfo and BlockInfo views.
Ccolor-by-feerate feature, with a new color scheme.
resolves #8, resolves #9, and progress towards #10