Allow servers to explcitly vouch for correct signatures on

transactions, proposals, and validations. This will allow cluster
members to more safely distribute crypto work.
This commit is contained in:
JoelKatz
2013-05-15 20:26:12 -07:00
parent afbaa46924
commit 9c55b3b92a

View File

@@ -94,6 +94,7 @@ message TMTransaction {
required bytes rawTransaction = 1; required bytes rawTransaction = 1;
required TransactionStatus status = 2; required TransactionStatus status = 2;
optional uint64 receiveTimestamp = 3; optional uint64 receiveTimestamp = 3;
optional bool checkedSignature = 4; // no vouches for signature being correct
} }
@@ -132,6 +133,7 @@ message TMProposeSet {
required uint32 closeTime = 4; required uint32 closeTime = 4;
required bytes signature = 5; // signature of above fields required bytes signature = 5; // signature of above fields
optional bytes previousledger = 6; optional bytes previousledger = 6;
optional bool checkedSignature = 7; // node vouches signature is correct
repeated bytes addedTransactions = 10; // not required if number is large repeated bytes addedTransactions = 10; // not required if number is large
repeated bytes removedTransactions = 11; // not required if number is large repeated bytes removedTransactions = 11; // not required if number is large
} }
@@ -151,6 +153,7 @@ message TMHaveTransactionSet {
// Used to sign a final closed ledger after reprocessing // Used to sign a final closed ledger after reprocessing
message TMValidation { message TMValidation {
required bytes validation = 1; // in SerializedValidation signed form required bytes validation = 1; // in SerializedValidation signed form
optional bool checkedSignature = 2; // node vouches signature is correct
} }