add blob fields to transactions #190
Merged
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.

TL;DR
Added support for EIP-4844 blob transaction fields in the transaction data model.
What changed?
Added two new fields to the
Transactionstruct:MaxFeePerBlobGas- to store the maximum fee per blob gasBlobVersionedHashes- to store the versioned hashes of the blobsUpdated the
TransactionModelstruct to include these new fieldsModified the transaction serialization logic to handle the new blob-related fields
Updated the ClickHouse database schema and insertion logic to store the new fields
How to test?
MaxFeePerBlobGasandBlobVersionedHashesvaluesWhy make this change?
This change adds support for EIP-4844 (blob transactions) introduced in the Ethereum Dencun upgrade. Blob transactions include additional fields that need to be captured and stored in our system to maintain complete transaction data. Without these fields, we would be missing critical information about blob transactions, which are important for layer 2 rollups and other scaling solutions.