...
Organizations on different blockchains can verify the validity of the private data received by creating the Hash value of the private data and sending a broadcast query to the network to check if the Hash matches the one stored in the blockchain.
The procedure to create the Hash and the data scheme structure will be part of this specification.
For illustration only, a sample Hash structure will look like:
Hash structure for a private data ( for illustration only )
{
“Payload” : {
“Resourceid”: “orgb:asset:kya:doc:id:123456”,
“Timestamp” : 123456789,
“Hash”: <encoded hash value>
},
“Signature” : {
“Identity”: <identity of primary node signing this message>,
“Signature”: <encoded signature of Organization primary node >
}
...
Transaction Confirmation Record
Whenever an asset transaction is executed in a local or remote FInP2P node, a transaction “receipt” “conformation record” is generated and sent to the Node requesting the transaction.
This specification encourages implementers to store the receipt confirmation record in the their own blockchain as proof of the remote transaction. The receipt confirmation record can be used at any time to verify if the transaction was actually performed at the remote Node by sending a broadcast query request.The receipt format and recommendations will be part of this specification.