Repository navigation
Ingest rich blocks and retire production input enrichment joins - #687
Open
startupcompliancekit wants to merge 2 commits into
Open
startupcompliancekit wants to merge 2 commits into
startupcompliancekit wants to merge 2 commits into
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.
Closes #569.
Use rich block endpoints for ingestion and preserve block-specific input amounts, addresses, tokens and references. Create sender/token indexes transactionally and retire InputUpdateQueries from production. Before synchronization starts, repair incomplete legacy inputs in bounded, resumable batches while preserving complete rows and finalized state. Also relates to #584.
Validation: 52 tests passed, including complete writer/read-only explorer integration, rich HTTP endpoints, fork-specific inputs, backfill recovery and finalization. Focused tests passed again after fixture/style cleanup; formatting and lint passed. All seven backend changes also passed 134 tests together. A populated node transaction-output-reference index is required: rich responses can omit unavailable asset references, so payload completeness cannot be certified here. Already-populated historical errors are not guessed or rewritten.