From 3a1804aa75a806e77ab3cd3c75220e336e147193 Mon Sep 17 00:00:00 2001 From: Yoichi Hirai Date: Tue, 3 Sep 2019 19:33:59 +0200 Subject: [PATCH] Reflect Message IDs for closing and updating This follows the implementation change in https://github.com/raiden-network/raiden-contracts/pull/1150 Since Balance Proof Update message is used both for closeChnanel() and updateNonClosingBalanceProof() call, the signature must be differentiated using different message IDs. --- smart_contracts.rst | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/smart_contracts.rst b/smart_contracts.rst index 90271d3..62222a7 100644 --- a/smart_contracts.rst +++ b/smart_contracts.rst @@ -147,7 +147,7 @@ Fields +-----------------------+------------+--------------------------------------------------------------------------------------------+ | chain_id | uint256 | Chain identifier as defined in EIP155 | +-----------------------+------------+--------------------------------------------------------------------------------------------+ -| message_type_id | uint256 | ``2`` = message type identifier | +| message_type_id | uint256 | ``1`` (if closing) or ``2`` (if updating) | +-----------------------+------------+--------------------------------------------------------------------------------------------+ | channel_identifier | uint256 | Channel identifier inside the TokenNetwork contract | +-----------------------+------------+--------------------------------------------------------------------------------------------+ @@ -163,6 +163,9 @@ Fields | signature | bytes | Elliptic Curve 256k1 signature on the above data from the non-closing participant | +-----------------------+------------+--------------------------------------------------------------------------------------------+ +The same message ID ``1`` is used for Balance Proof Update and Balance Proof messages. This is not a problem because these messages have different lengths. + + .. _withdraw-proof: Withdraw Proof