216 lines
11 KiB
Plaintext
216 lines
11 KiB
Plaintext
Ethereum application : Common Technical Specifications
|
|
=======================================================
|
|
Ledger Firmware Team <hello@ledger.fr>
|
|
Application version 1.0 - 28th of May 2016
|
|
|
|
== 1.0
|
|
- Initial release
|
|
|
|
== About
|
|
|
|
This application describes the APDU messages interface to communicate with the Ethereum application.
|
|
|
|
The application covers the following functionalities :
|
|
|
|
- Retrieve a public Ethereum address given a BIP 32 path
|
|
- Sign a basic Ethereum transaction given a BIP 32 path
|
|
- Provide callbacks to validate the data associated to an Ethereum transaction
|
|
|
|
The application interface can be accessed over HID or BLE
|
|
|
|
== General purpose APDUs
|
|
|
|
=== GET ETH PUBLIC ADDRESS
|
|
|
|
==== Description
|
|
|
|
This command returns the public key and Ethereum address for the given BIP 32 path.
|
|
|
|
The address can be optionally checked on the device before being returned.
|
|
|
|
==== Coding
|
|
|
|
'Command'
|
|
|
|
[width="80%"]
|
|
|==============================================================================================================================
|
|
| *CLA* | *INS* | *P1* | *P2* | *Lc* | *Le*
|
|
| E0 | 02 | 00 : return address
|
|
|
|
01 : display address and confirm before returning
|
|
| 00 | variable | variable
|
|
|==============================================================================================================================
|
|
|
|
'Input data'
|
|
|
|
[width="80%"]
|
|
|==============================================================================================================================
|
|
| *Description* | *Length*
|
|
| Number of BIP 32 derivations to perform (max 10) | 1
|
|
| First derivation index (big endian) | 4
|
|
| ... | 4
|
|
| Last derivation index (big endian) | 4
|
|
|==============================================================================================================================
|
|
|
|
'Output data'
|
|
|
|
[width="80%"]
|
|
|==============================================================================================================================
|
|
| *Description* | *Length*
|
|
| Public Key length | 1
|
|
| Uncompressed Public Key | var
|
|
| Ethereum address length | 1
|
|
| Ethereum address | var
|
|
|==============================================================================================================================
|
|
|
|
|
|
=== SIGN ETH TRANSACTION
|
|
|
|
==== Description
|
|
|
|
This command signs an Ethereum transaction after having the user validate the following parameters
|
|
|
|
- Gas price
|
|
- Gas limit
|
|
- Recipient address
|
|
- Value
|
|
|
|
The input data is the RLP encoded transaction (as per https://github.com/ethereum/pyethereum/blob/develop/ethereum/transactions.py#L22), without v/r/s present, streamed to the device in 255 bytes maximum data chunks.
|
|
|
|
==== Coding
|
|
|
|
'Command'
|
|
|
|
[width="80%"]
|
|
|==============================================================================================================================
|
|
| *CLA* | *INS* | *P1* | *P2* | *Lc* | *Le*
|
|
| E0 | 04 | 00 : first transaction data block
|
|
|
|
80 : subsequent transaction data block
|
|
| 00 | variable | variable
|
|
|==============================================================================================================================
|
|
|
|
'Input data (first transaction data block)'
|
|
|
|
[width="80%"]
|
|
|==============================================================================================================================
|
|
| *Description* | *Length*
|
|
| Number of BIP 32 derivations to perform (max 10) | 1
|
|
| First derivation index (big endian) | 4
|
|
| ... | 4
|
|
| Last derivation index (big endian) | 4
|
|
| RLP transaction chunk | variable
|
|
|==============================================================================================================================
|
|
|
|
'Input data (other transaction data block)'
|
|
|
|
[width="80%"]
|
|
|==============================================================================================================================
|
|
| *Description* | *Length*
|
|
| RLP transaction chunk | variable
|
|
|==============================================================================================================================
|
|
|
|
|
|
'Output data'
|
|
|
|
[width="80%"]
|
|
|==============================================================================================================================
|
|
| *Description* | *Length*
|
|
| v | 1
|
|
| r | 32
|
|
| s | 32
|
|
|======================================================================================================
|
|
|
|
|
|
== Transport protocol
|
|
|
|
=== General transport description
|
|
|
|
Ledger APDUs requests and responses are encapsulated using a flexible protocol allowing to fragment large payloads over different underlying transport mechanisms.
|
|
|
|
The common transport header is defined as follows :
|
|
|
|
[width="80%"]
|
|
|==============================================================================================================================
|
|
| *Description* | *Length*
|
|
| Communication channel ID (big endian) | 2
|
|
| Command tag | 1
|
|
| Packet sequence index (big endian) | 2
|
|
| Payload | var
|
|
|==============================================================================================================================
|
|
|
|
The Communication channel ID allows commands multiplexing over the same physical link. It is not used for the time being, and should be set to 0101 to avoid compatibility issues with implementations ignoring a leading 00 byte.
|
|
|
|
The Command tag describes the message content. Use TAG_APDU (0x05) for standard APDU payloads, or TAG_PING (0x02) for a simple link test.
|
|
|
|
The Packet sequence index describes the current sequence for fragmented payloads. The first fragment index is 0x00.
|
|
|
|
=== APDU Command payload encoding
|
|
|
|
APDU Command payloads are encoded as follows :
|
|
|
|
[width="80%"]
|
|
|==============================================================================================================================
|
|
| *Description* | *Length*
|
|
| APDU length (big endian) | 2
|
|
| APDU CLA | 1
|
|
| APDU INS | 1
|
|
| APDU P1 | 1
|
|
| APDU P2 | 1
|
|
| APDU length | 1
|
|
| Optional APDU data | var
|
|
|==============================================================================================================================
|
|
|
|
APDU payload is encoded according to the APDU case
|
|
|
|
[width="80%"]
|
|
|=======================================================================================
|
|
| Case Number | *Lc* | *Le* | Case description
|
|
| 1 | 0 | 0 | No data in either direction - L is set to 00
|
|
| 2 | 0 | !0 | Input Data present, no Output Data - L is set to Lc
|
|
| 3 | !0 | 0 | Output Data present, no Input Data - L is set to Le
|
|
| 4 | !0 | !0 | Both Input and Output Data are present - L is set to Lc
|
|
|=======================================================================================
|
|
|
|
=== APDU Response payload encoding
|
|
|
|
APDU Response payloads are encoded as follows :
|
|
|
|
[width="80%"]
|
|
|==============================================================================================================================
|
|
| *Description* | *Length*
|
|
| APDU response length (big endian) | 2
|
|
| APDU response data and Status Word | var
|
|
|==============================================================================================================================
|
|
|
|
=== USB mapping
|
|
|
|
Messages are exchanged with the dongle over HID endpoints over interrupt transfers, with each chunk being 64 bytes long. The HID Report ID is ignored.
|
|
|
|
=== BLE mapping
|
|
|
|
A similar encoding is used over BLE, without the Communication channel ID.
|
|
|
|
The application acts as a GATT server defining service UUID D973F2E0-B19E-11E2-9E96-0800200C9A66
|
|
|
|
When using this service, the client sends requests to the characteristic D973F2E2-B19E-11E2-9E96-0800200C9A66, and gets notified on the characteristic D973F2E1-B19E-11E2-9E96-0800200C9A66 after registering for it.
|
|
|
|
Requests are encoded using the standard BLE 20 bytes MTU size
|
|
|
|
== Status Words
|
|
|
|
The following standard Status Words are returned for all APDUs - some specific Status Words can be used for specific commands and are mentioned in the command description.
|
|
|
|
'Status Words'
|
|
|
|
[width="80%"]
|
|
|===============================================================================================
|
|
| *SW* | *Description*
|
|
| 6700 | Incorrect length
|
|
| 6982 | Security status not satisfied (Canceled by user)
|
|
| 6A80 | Invalid data
|
|
| 6B00 | Incorrect parameter P1 or P2
|
|
| 6Fxx | Technical problem (Internal error, please report)
|
|
| 9000 | Normal ending of the command
|
|
|================================================================================================
|