The 'previous hash' logic isn't needed.

This commit is contained in:
JoelKatz
2012-05-22 02:35:11 -07:00
parent fbce5dafc5
commit 485a8a709d

View File

@@ -103,12 +103,11 @@ message TMStatusChange {
message TMProposeSet {
required uint32 closingSeq = 1;
required uint32 proposeSeq = 2;
required bytes previousTxHash = 3; // 0 if first proposal, hash we no longer propose
required bytes currentTxHash = 4; // the hash of the ledger we are proposing
required bytes nodePubKey = 5;
required bytes signature = 6; // signature of above fields
repeated bytes addedTransactions = 7; // not required if number is large
repeated bytes removedTransactions = 8; // not required if number is large
required bytes currentTxHash = 3; // the hash of the ledger we are proposing
required bytes nodePubKey = 4;
required bytes signature = 5; // signature of above fields
repeated bytes addedTransactions = 6; // not required if number is large
repeated bytes removedTransactions = 7; // not required if number is large
}
// Announce to a peer that we have fully acquired a transaction set