From 2d2584899f197a03bdae4583cbec8748992ee3f6 Mon Sep 17 00:00:00 2001 From: Bumblefudge Date: Wed, 14 Dec 2022 08:49:53 -0800 Subject: [PATCH] Update eip155/caip168.md Co-authored-by: Zach Ferland --- eip155/caip168.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/eip155/caip168.md b/eip155/caip168.md index ae41a467..72e670b5 100644 --- a/eip155/caip168.md +++ b/eip155/caip168.md @@ -97,11 +97,11 @@ implementation. Use of a root CID encoded in [DAG-CBOR][] is recommended. work?](https://github.com/multiformats/cid#how-does-it-work) in the [Multiformats CID][] specification for context). It does not include the multibase, the CID version or the IPLD codec segments. It is assumed that the - IPLD codec is dag-cbor. Verify that the first 32bytes of the `root` CID of - the timestamp anchor proof is equivalent to the 32-byte partial CID extracted + IPLD codec is dag-cbor. Verify that the multihash portion of the `root` CID of + the timestamp proof is equivalent to the multihash extracted from the transaction data. Equivalence should be checked using a CIDs - library, which can compare oprtions of multihashes encoded in bytes. If the - two partial multihashes are not equivalent, verification MUST fail. + library, which can compare multihash portions encoded in bytes. If the + two multihashes are not equivalent, verification MUST fail. 5) Determine that the transaction has been included in a valid block on the blockchain referenced by the `chainId`. Number of block confirmations for acceptance is up to an implementation.