From a86d4cb22a349e34df038acbf33ac57cf768d226 Mon Sep 17 00:00:00 2001 From: Stephen Buttolph Date: Thu, 5 Oct 2023 16:57:45 -0400 Subject: [PATCH 1/2] Add additional payload.Hash examples --- vms/platformvm/warp/payload/README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/vms/platformvm/warp/payload/README.md b/vms/platformvm/warp/payload/README.md index d82a59831be1..45b1415354f1 100644 --- a/vms/platformvm/warp/payload/README.md +++ b/vms/platformvm/warp/payload/README.md @@ -19,7 +19,10 @@ Hash: - `codecID` is the codec version used to serialize the payload and is hardcoded to `0x0000` - `typeID` is the payload type identifier and is `0x00000000` for `Hash` -- `hash` is a hash from the `sourceChainID`. As an example, this may be the hash of a block that was accepted on the source chain +- `hash` is a hash from the `sourceChainID`. The format of the expected preimage is chain specific. Some examples for valid uses of the hash are: + - Hash is the root of a merkle tree + - Hash of a block that was accepted on the source chain + - Hash of a transaction that was included on the source chain ## AddressedCall From d4570dec2ffc32d85ccc67ea9267b934738c92a4 Mon Sep 17 00:00:00 2001 From: Stephen Buttolph Date: Thu, 5 Oct 2023 17:24:52 -0400 Subject: [PATCH 2/2] Update vms/platformvm/warp/payload/README.md Co-authored-by: Dhruba Basu <7675102+dhrubabasu@users.noreply.github.com> Signed-off-by: Stephen Buttolph --- vms/platformvm/warp/payload/README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/vms/platformvm/warp/payload/README.md b/vms/platformvm/warp/payload/README.md index 45b1415354f1..2da32ee56f4f 100644 --- a/vms/platformvm/warp/payload/README.md +++ b/vms/platformvm/warp/payload/README.md @@ -19,10 +19,10 @@ Hash: - `codecID` is the codec version used to serialize the payload and is hardcoded to `0x0000` - `typeID` is the payload type identifier and is `0x00000000` for `Hash` -- `hash` is a hash from the `sourceChainID`. The format of the expected preimage is chain specific. Some examples for valid uses of the hash are: - - Hash is the root of a merkle tree - - Hash of a block that was accepted on the source chain - - Hash of a transaction that was included on the source chain +- `hash` is a hash from the `sourceChainID`. The format of the expected preimage is chain specific. Some examples for valid hash values are: + - root of a merkle tree + - accepted block hash on the source chain + - accepted transaction hash on the source chain ## AddressedCall