fix: align receipt format in Flashblocks node examples with official schema#2
Open
fix: align receipt format in Flashblocks node examples with official schema#2
Conversation
…schema The Initial Response example used a "Deposit" wrapper key that doesn't exist in the official Receipt Object schema. Updated to match the flat structure defined in the Flashblocks API Reference.
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
1 participant
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.
The example JSON responses in the Run a Flashblocks Node page show inconsistent receipt formats between the Initial Response and Diff Response examples, and neither matches the official Receipt Object schema documented in the API reference.
What changed? Why?
Updated the receipt format in the Initial Response example to match the official Receipt Object schema (type, status, cumulativeGasUsed, logs, logsBloom, transactionIndex). The previous example used a "Deposit" wrapper key that doesn't exist in the official schema, which would confuse developers writing receipt parsing code.
Notes to reviewers
Docs-only change. The fix aligns the example data with the Receipt Object schema defined in the Flashblocks API Reference.
How has it been tested?
Verified against the Receipt Object schema in the Flashblocks API Reference which defines the correct flat structure without any wrapper keys.