-
Notifications
You must be signed in to change notification settings - Fork 302
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fetch and store transactions from pd
storage
#3473
Conversation
40ba5d5
to
ac14d17
Compare
// An authorization hash for a Penumbra transaction. | ||
message EffectHash { | ||
bytes inner = 1; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Side note: I think we might want to split the effect hash code into its own crate, rather than putting it in the transaction crate. The reason is that all of the components need to be able to define their effecting data, but the overarching transaction
crate depends on all the components.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This LGTM, thanks for getting it done.
This removes
pcli
's reliance on theget_block_by_height
method since it can't persist data after a chain upgrade occurs. Since it was only using this to fetch transaction data during sync, the transaction data is all that we need to record.All block transactions will be recorded in nonverifiable storage in a new
cometbft-data
substore.Closes #3451