You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Basically, right now, a block does not contain enough info to figure out what happened in a given transaction. This is not something that is critical for building blocks, but it would be nice to have this info to show to the user. #919 (comment)
These should be created from a ProvenTransaction after they were verified in LocalBatchProver::prove.
We then probably should include VerifiedTransaction in a ProvenBatch.
One open question to me is whether ProvenBatch will end up in a Block or not. Then the block would actually contain all the interesting data for the explorer to show I believe.
When is this task done?
Presumably when the block contains enough information so that it's possible (in the explorer, for example)
[...] to show which nullifiers were consumed in the transaction and which output notes were created. #919 (comment)
Additional context
No response
The text was updated successfully, but these errors were encountered:
What should be done?
Add
VerifiedTransaction
struct toProvenBatch
.How should it be done?
Add the struct (roughly) as defined in #919 (comment).
These should be created from a
ProvenTransaction
after they were verified inLocalBatchProver::prove
.We then probably should include
VerifiedTransaction
in aProvenBatch
.One open question to me is whether
ProvenBatch
will end up in aBlock
or not. Then the block would actually contain all the interesting data for the explorer to show I believe.When is this task done?
Presumably when the block contains enough information so that it's possible (in the explorer, for example)
Additional context
No response
The text was updated successfully, but these errors were encountered: