TECH-631: Atomic C-Chain txs on the cblocks query#31
Draft
charalarg wants to merge 1 commit into
Draft
Conversation
charalarg
force-pushed
the
feature/TECH-631-cbocks-atomic-txs
branch
from
88860af to
889d43d
Compare
charalarg
force-pushed
the
feature/TECH-631-cbocks-atomic-txs
branch
from
889d43d to
1f0ebaa
Compare
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.
Description
This PR adds the atomic c-chain txs on the c-blocks query response in order to be visible in the block explorer's c-chain view.
These txs are also taken into account by the aggregation calculations.
Changes
cvm_transactions_atomictable, in order to be consistent with thecvm_transactions_txdatatable.Example
Block explorer showing an import tx:
Remarks
By clicking the txID or the avax address (
FromorToaddress, depends on if the tx is an import or an export ones) of this tx,we reach empty tables. For the time being these fields could become unclickable from the block explorer because this functionality is out of scope for this PR and needs further refinement.