Issue transaction receipts in machine and human readable format

[MBadea17]

For every successful consume flow (either download or C2D), a receipt will be generated for each party involved: data publisher, algorithm publisher, C2D provider, OE node provider, and market operator.

• the receipt will include:
  • an identifier of the party;
  • the identifier of the consumer that receives the invoice
  • the transaction number;
  • the fee associated with it;
• the receipt must be available in machine-readable formats (JSON).
• using the TX ID, the invoice will be generated on the fly.
• the receipt must be stored in a location set for each party.
• Form: function on the client side to get the JSON file based on the TX id.

[MBadea17]

@alexcos20 , please add the technical specifications on the implementation of the feature.

@Abrom8 , please add any missing detail to the requirement.

Thanks.

[MarianButucel]

Invoices

1st Case: Asset Type Dataset:

Data Publisher = Seller:

• Publishes a dataset type asset on the marketplace.
• Interacts with the network to publish the asset:
• Pays gas fee for creating the Data Token.
• Pays gas fee for publishing the DDO.
• Pays Publish Fee to Publish Market -> Invoice from Publish Market to Seller.
• In the invoice, we will create an additional field where the fees of the two transactions for publishing will be displayed.
• The total price on the invoice will be just the price paid by the Seller to the Market for Publish.

Consumer = Buyer:

• Buys a dataset type asset (initiates an ORDER):
• Buyer signs the transaction to Approve the tokens to be paid - pays gas fee.
• Buyer pays the Seller for the asset: Invoice between Seller and Buyer -> Seller issues invoice -> Seller and Buyer see the invoice.
• Buyer pays gas fee to the network at the Buy transaction.
• In the invoice between Seller and Buyer, we will create 2 additional fields where the fees paid to the network will be specified.
• The total price on the invoice will be just the price paid by the Buyer to the Seller.
• Buyer pays fee to the Consume Market for the Order -> Invoice from Consume Market to Buyer.
• Buyer pays fee to Provider -> Invoice from Provider to Buyer.
• Buyer pays fee to OEC -> Invoice between OEC and Buyer (OEC fee is the one that the Marketplace currently charges - Community Swap Fee)

For Dataset Type Asset (for Publish and Order) the following invoices are issued:

• Invoice from Publish Market to Seller (upon publishing the asset).
• Invoice between Seller and Buyer -> upon buying the asset - Both see it in their Profile.
• Invoice between Consume Market Operator and Buyer -> Both see the invoice.
• Invoice from Provider to Buyer -> Both see the invoice.
• Invoice from OEC to Buyer

For payment of the gas fee:

• Gas fee paid by Buyer or Seller will be found in invoices, as detailed above. The Gas Fee will be displayed in an extra field in the invoices, and we will display the value of the Gas and for which action it was paid.

[MarianButucel]

2nd Case, C2D:

Algorithm Publisher = Seller:

• Publishes a C2D type asset on the marketplace, interacts with the network for publishing the asset:
• Pays gas fee for creating the Data Token.
• Pays gas fee for publishing the DDO.
• Pays Publish Fee to Publish Market -> Invoice from Publish Market to Seller.
• In the invoice, we will create an additional field where the fees of the two transactions for publish will be displayed.
• The total price on the invoice will be just the price paid by the Seller to the Market for Publish.

Consumer = Buyer:

• Buys a C2D type asset: Buys Dataset from Dataset Seller and Algorithm from Algorithm Seller.

• Buyer selects the algorithm they want to run on the DATASET type asset.

• Buyer Buys DATASET:

  • Buyer signs the transaction to Approve payment for Dataset -> Pays Gas Fee for APPROVE.
  • Buyer pays the Seller for Dataset: Invoice between Dataset Seller and Buyer -> Dataset Seller issues invoice -> Dataset Seller and Buyer see the invoice.
  • Buyer pays gas fee to the network for ORDER.

• In the invoice between Seller and Buyer, we will create 2 additional fields where the fees paid to the network will be specified.

• The total price on the invoice will be just the price paid by Buyer to Seller.

• Buyer pays fee to Consume Market for buy -> Invoice from Consume Market to Buyer.

• Buyer pays fee to Provider -> Invoice from Provider to Buyer.

• Buyer pays fee to OEC -> Invoice between OEC and Buyer

• Buyer Buys ALGORITHM:

• Buyer signs the transaction to Approve payment for Algorithm -> Pays Gas Fee for APPROVE.

• Buyer pays the Seller for Algorithm: Invoice between Algorithm Seller and Buyer -> Algorithm Seller issues invoice -> Algorithm Seller and Buyer see the invoice.

• Buyer pays gas fee to the network for ORDER.

• In the invoice between Seller and Buyer, we will create 2 additional fields where the fees paid to the network will be specified.

• The total price on the invoice will be just the price paid by Buyer to Seller.

For the C2D type asset, the following invoices are issued:

• Invoice from Publish Market to Seller (upon publishing the asset).
• Invoice between Dataset Seller and Buyer -> upon buying the Dataset - Both should see it in their Profile.
• Invoice between Consume Market and Buyer -> Both see the invoice.
• Invoice from Provider to Buyer -> Both see the invoice.
• Invoice from OEC to Buyer