Skip to content
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

[fastx distsys] derive TransactionDigest with a hash function instead of using a tuple #65

Closed
sblackshear opened this issue Dec 16, 2021 · 0 comments · Fixed by #117
Closed
Assignees

Comments

@sblackshear
Copy link
Collaborator

Currently, we use an (ObjectID, SequenceNumber) pair to represent a TransactionDigest, but we should instead use the hash of the transaction contents.

@gdanezis gdanezis self-assigned this Jan 4, 2022
@gdanezis gdanezis linked a pull request Jan 4, 2022 that will close this issue
mwtian pushed a commit that referenced this issue Sep 12, 2022
This commit adds functionality to handle the PrimaryWorkerMessage::RequestBatch command on the worker and send back to the primary the requested batch.
mwtian pushed a commit to mwtian/sui that referenced this issue Sep 29, 2022
This commit adds functionality to handle the PrimaryWorkerMessage::RequestBatch command on the worker and send back to the primary the requested batch.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants