Re: [Blockchain-interop] Scope of Work

Thomas Hardjono <> Tue, 13 October 2020 20:43 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E44253A08AD for <>; Tue, 13 Oct 2020 13:43:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id TCK2BrcsIY16 for <>; Tue, 13 Oct 2020 13:43:14 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0EF763A08AB for <>; Tue, 13 Oct 2020 13:43:10 -0700 (PDT)
Received: from (W92EXEDGE4.EXCHANGE.MIT.EDU []) by (8.14.7/8.12.4) with ESMTP id 09DKgpBY010389; Tue, 13 Oct 2020 16:43:09 -0400
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1293.2; Tue, 13 Oct 2020 16:42:43 -0400
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1365.1; Tue, 13 Oct 2020 16:42:50 -0400
Received: from ([]) by ([]) with mapi id 15.00.1365.000; Tue, 13 Oct 2020 16:42:50 -0400
From: Thomas Hardjono <>
To: =?iso-8859-1?Q?Rafael_Andr=E9_Pestana_Belchior?= <>
CC: "" <>, "" <>
Thread-Topic: [Blockchain-interop] Scope of Work
Thread-Index: AdahkITafN9dND8YQcKuDjiKcNVmcgAB3LJyAAnTTgD//8JLIQ==
Date: Tue, 13 Oct 2020 20:42:49 +0000
Message-ID: <>
References: <GV0P278MB00204AE517921470AE1057C38B040@GV0P278MB0020.CHEP278.PROD.OUTLOOK.COM> <>, <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [Blockchain-interop] Scope of Work
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Blockchain Gateway Interoperability Protocol <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 13 Oct 2020 20:43:16 -0000

Thanks Rafael.

As I mentioned, maybe there will need to be a kind of "payload profile" that defines the meaning of the component/part of the payload according to the type of asset and policies/conditions. 

This profile (specification) would include links to the resources (off-chain, or on-chain on ledger L1) that must be delivered from G1 to G2 in order to permit G2 to evaluate and accept the payload.

So for example, if the virtual asset was stablecoin X backed by some securities, then the "payload profile for X" specification may mandate inclusion of a URL to the signed securities (i.e. digitized securities). The profile may even include the Jurisdictions where the profile is honored.

Just a thought.

-- thomas --

From: Rafael André Pestana Belchior []
Sent: Tuesday, October 13, 2020 4:16 PM
To: Thomas Hardjono
Subject: Re: [Blockchain-interop] Scope of Work

Hello All,
Great to e-meet you.

The fact that G1 signs the payload using its key-pair is a good start to
ensure accountability. We need to discuss if the protocol should assure
accountability in case of dispute, or if it suffices to coordinate


A 2020-10-13 20:47, Thomas Hardjono escreveu:
> Hi Aetienne,
>>> Regarding the scope: I was wondering whether we
>>> should also include other interoperability issues apart
>>> from asset transfers, such as referencing data
>>> between blockchains (or from a blockchain to a legacy system)?
> Yes, for sure -- the model describes in the architecture draft calls
> these references and data (on-chain and off-chain) generically as
> "blockchain resources".
> For example, if a third party entity is used to "price"  a virtual
> asset (e.g. economic pricing or estimate done by a bank or FI) prior
> to the asset transfer, then the transfer-payload between G1 and G2
> could (must) include a link (e.g. URL or hash) to the claim signed by
> the  third party.
> This means that G1 must sign the payload using its entity public key
> pair (not the transaction public key pair).  Here G1 (i.e. the VASP
> owner of G1) is essentially asserting the truthfulness of the link to
> the resource.
> Best
> -- thomas --
> ________________________________________
> From: Blockchain-interop [] on
> behalf of []
> Sent: Tuesday, October 13, 2020 2:45 PM
> To:
> Subject: [Blockchain-interop] Scope of Work
> Hi all, great meeting you all in today's kickoff call!
> Regarding the scope: I was wondering whether we should also include
> other interoperability issues apart from asset transfers, such as
> referencing data between blockchains (or from a blockchain to a legacy
> system)?
> The reason why I'm asking is because a new DLT law is expected to
> enter into force in Switzerland next year, which will require that for
> all DLT-based financial instruments corresponding investor
> documentation (e.g. prospectus) shall be made available either
> directly on the given ledger or by referring to an outside data
> storage (which could be a legacy system as mentioned on slide 10 point
> 2). The latter case obviously creates an interoperability problem. So
> far the legislator has only outlined that there needs to be a unique
> pointer/identifier (e.g. a hash of the document), to ensure integrity
> of the accompanying external documentation. But apart from that there
> are currently no specific technical guidelines on how an interoperable
> on-/off-ledger pointer mechanism shall work. IMO our IETF working
> group could be a great platform to discuss and provide some guidance.
> What do you think?
> Best regards
> Aetienne

Rafael Belchior
Ph.D. student in Computer Science and Engineering, Blockchain - Técnico