Update doc

Author: Lbqds

docs/apdu.md

@@ -41,6 +41,7 @@ The general structure of a request and response is as followed:
 | 0xE005      | Failed to derive pub key  |
 | 0xE006      | Invalid token size        |
 | 0xE007      | Invalid metadata version  |
+| 0xE008      | Invalid token proof size  |
 | 0xEF00      | Internal error            |
 
 ## Commands definitions
@@ -131,11 +132,42 @@ This command returns a signature of the passed transaction
 |-------|----------|-----------------------------|-------------------|
 | CLA   | byte (1) | Application Identifier      | 0x80              |
 | INS   | byte (1) | Instruction ID              | 0x03              |
-| P1    | byte (1) | Payload desc                | 0x00: first transaction data block <br> 0x01: subsequent transaction data block |
-| P2    | byte (1) | ignored                     |                   |
+| P1    | byte (1) | Payload desc                | 0x00, 0x01, 0x02  |
+| P2    | byte (1) | ignored                     | 0x00, 0x01        |
 | L     | byte (1) | Bytes in payload            | (depends)         |
 
-Input data (first transaction data block):
+We use `P1` and `P2` to distinguish between different data frames:
+
+* `P1` = 0 and `P2` = 0 indicates the first token metadata data frame
+* `P1` = 1 and `P2` = 1 indicates a token proof data frame
+* `P1` = 1 and `P2` = 0 indicates subsequent metadata data frames
+* `P1` = 2 and `P2` = 0 indicates the first tx data frame
+* `P1` = 2 and `P2` = 1 indicates subsequent tx data frames
+
+Input data (first token metadata frame):
+
+| Field          | Type                   | Content              | Expected          |
+|----------------|------------------------|----------------------|-------------------|
+| Token Size     | byte (1)               | Token Size           | Any value between 0 and 5, inclusive |
+| Token Metadata | 46                     | Token Metadata       | ?                 |
+| Token Proof Size |  2                   | Token Proof Size     | ?                 |
+| Token Proof    | byte (?)               | Token Proof          | ?                 |
+
+Input data (token proof frame):
+
+| Field          | Type                   | Content              | Expected          |
+|----------------|------------------------|----------------------|-------------------|
+| Token Proof    | byte (?)               | Token Proof          | ?                 |
+
+Input data (subsequent token metadata frame):
+
+| Field          | Type                   | Content              | Expected          |
+|----------------|------------------------|----------------------|-------------------|
+| Token Metadata | 46                     | Token Metadata       | ?                 |
+| Token Proof Size |  2                   | Token Proof Size     | ?                 |
+| Token Proof    | byte (?)               | Token Proof          | ?                 |
+
+Input data (first transaction data frame):
 
 | Field          | Type                   | Content              | Expected          |
 |----------------|------------------------|----------------------|-------------------|
@@ -144,11 +176,9 @@ Input data (first transaction data block):
 | Path[2]        | byte (4)               | Derivation Path Data | ?                 |
 | Path[3]        | byte (4)               | Derivation Path Data | ?                 |
 | Path[4]        | byte (4)               | Derivation Path Data | ?                 |
-| Token Size     | byte (1)               | Token Size           | Any value between 0 and 5, inclusive |
-| Token Metadata | byte (Token Size * 46) | Token Metadata       | ?                 |
 | Payload        | byte (?)               | Transaction Payload  | ?                 |
 
-Input data (subsequent transaction data block):
+Input data (subsequent transaction data frame):
 
 | Field   | Type     | Content                   | Expected          |
 |---------|----------|---------------------------|-------------------|