update ResponseCheckTx (#306)

proto/abci/types.proto

@@ -195,9 +195,10 @@ message ResponseCheckTx {
   string         info       = 4;  // nondeterministic
   int64          gas_wanted = 5 [json_name = "gas_wanted"];
   int64          gas_used   = 6 [json_name = "gas_used"];
-  repeated Event events     = 7
-      [(gogoproto.nullable) = false, (gogoproto.jsontag) = "events,omitempty"];
-  string codespace = 8;
+  repeated Event events     = 7 [(gogoproto.nullable) = false, (gogoproto.jsontag) = "events,omitempty"];
+  string         codespace  = 8;
+  string         sender     = 9;
+  int64          priority   = 10;
 }
 
 message ResponseDeliverTx {

spec/abci/abci.md

@@ -377,8 +377,11 @@ via light client.
     | gas_used   | int64                     | Amount of gas consumed by transaction.                                | 6            |
     | events     | repeated [Event](#events) | Type & Key-Value events for indexing transactions (eg. by account).   | 7            |
     | codespace  | string                    | Namespace for the `code`.                                             | 8            |
+    | sender     | string                    | The transaction's sender (e.g. the signer)                            | 9            |
+    | priority   | int64                     | The transaction's priority (for mempool ordering)                     | 10           |
 
 - **Usage**:
+
     - Technically optional - not involved in processing blocks.
     - Guardian of the mempool: every node runs CheckTx before letting a
     transaction into its local mempool.

spec/abci/apps.md

@@ -167,8 +167,6 @@ and/or restore state sync snapshots to a local node being bootstrapped.
 
 ## Transaction Results
 
-`ResponseCheckTx` and `ResponseDeliverTx` contain the same fields.
-
 The `Info` and `Log` fields are non-deterministic values for debugging/convenience purposes
 that are otherwise ignored.