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.
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
Nomination prototype #3856
Nomination prototype #3856
Changes from 36 commits
83c46a8
4c11fd0
e29bb86
5ac20c0
0e6cf73
3478fba
5883118
da136a7
541f632
1db7bc2
46236b5
cee418e
b8222e2
efee75d
4d5c13d
96b12f7
e10a556
c6757f4
5ff851a
b85bc45
f904642
3cbb29f
13c4874
1d69e90
d8e0005
b94fa8b
63303c2
d8e25a6
aaeba33
92435b9
f6d58c0
41308d3
4d67a45
ce080d3
99a9a63
ba04c15
9f534db
2acba40
1651120
5e43b7a
1d71931
254fc6f
5e5445d
555b9e0
86cd20b
da29888
a94237d
fe80739
cf90561
5da884e
101e0ae
73dba79
a7ca10e
122363e
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
hmm, this doesn't seem right: if we are running protocol 20, then all transaction sets must be generalized. If this isn't the case, it points to a bug. If you do need to create a non-generalized transaction set, then we need to ensure that application is on protocol 19, and
TxPhases
contains only only one "phase" (just a bit of background, generalized transaction sets allow multiple transaction "phases")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.
We shouldn't need to remove this assert in tests.
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.
I think the issue is in the test, which is creating tx sets rather than generalized tx sets, so feel free to revert this change.
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.
Sorry I thought we're meant to create tx sets rather than generalized tx sets, as the node is meant to receive the tx set? My recollection is that generalized tx set basically just contains the hash?
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.
generalized transaction sets are also transactions sets, but with a slightly different structure to accommodate protocol 20. See definition here: https://github.com/stellar/stellar-xdr/blob/curr/Stellar-ledger.x#L234.