Supply chain Infinity War: could be Scrypta the alternative ?

From Hyperledger to Scrypta: a new model of “privatization”?

Some time ago, during the call for ideas organized by CoopItalia and IBM for the rewriting of the egg supply chain that introduced the use of blockchain into the process, we had produced the white paper at the following link summarized later by this post (only Italian version)

On the occasion of this specific project we had analyzed the entire production chain and revised the process by introducing the use of Hyperledger Fabric, a permissioned or privateblockchain, which introduce built-in features specific to the “modeling” of a customer / supplier relationship , supplier / supplier and / or customer / customer:

  • Private channels
  • Smart Contract for business logic and complete dematerialization of the process
  • Governance

These three aspects, summarizing the results of our analysis, were the key issue to make the supply chain truly transparent, both for consumer and for suppliers, traceable and collaborative.

This until our attention has been subsequently attracted by the ScryptaChain post

which introduced an alternative solution for tracing supply chains through the adoption of the Scrypta blockchain.

Inside the post we read:

“Scrypta’s blockchain allows to build open supply chains in which all actors …can provide data and information and verify all supply chain participants data with maximum transparency.

….

Scrypta guarantees a clear information flow free from irregularities.

….

Through the automatic recording of information in the network it is possible to create a permanent product history and track its production chain. Each information acquired is validated by the network of companies that form a consensus. After each “block” (registration of each transaction) has been validated, it is added to a “chain” of transactions, becoming a permanent record of the whole process.

Therefore, it is possible to record continuously all the data on the quality of a production batch. The data will remain indelibly recorded and it will not be possible to manipulate and / or alter it”.

At this point it is mandatory to ask what happened to the three pillars highlighted as a result of our previous analysis. And that is:

How does Scrypta think about dealing with aspects related to private communications, the realization of business logic, dApps, and the governance of processes?

For private communications, those that we had previously referred to as private channels, Scrypta provides natively a system of obfuscation that allows you to encrypt the information exchanged and therefore permit reading only to those in possession of the key.

it’s could be necessary to clarified the other two arguments and to do so we have asked the Scrypta Team for support through their Discord channel. Below is the excerpt of the conversation in the question / answer form.

How to implement the business logic related to the process on Scrypta? Do we have to translate all the steps into a logic L2 (Scrypta has no Smart Contract), and ask dApps to manage them?

It depends on the target. If you need to hide information, you can simply encrypt everything and provide the key to only one part of the chain. If the result is to be public, you can simply write the information on the blockchain … or both.

dApps run on a logic L2, L1 is only for blocks, transactions and addresses. Smart Contract are only “API callers” through the blockchain, activated by external oracles.

This result can also be achieved on Scrypta, but the code, unlike what happens on Ethereum and Tron, does not “natively” run on the blockchain. But the logic is the same: there is some code — maybe really decentralized and running on an Arduino or similar — that provides an endpoint API — like our idA-Nodes — and that writes on the blockchain. Then there is another code, such as a website, that reads this information.

With the same logic I can implement a layer that manages the roles and permissions. Is that it?

Of course, different keys “unlock” different layers. Or you can use different addresses: one can read and see everything -ndr Admin- and others only certain information.

Using idA-Nodes you have three fields to use:

  1. date: here you can enter plain or encrypted text
  2. collection: useful for identifying certain contents. This field is always clear and can be used for queries before decrypting the contents.
  3. refID: is the reference ID of a specific object. This field is always clear as well.

In this way you can call the writing endpoint without the flag to encrypt the data and then encrypt / decrypt it on the dApp.

So let’s recap the differences between the key aspects of Hyperledger and Scrypta:

  • Private channels vs obfuscation
  • Smart Contract vs L2 logic (dApp level)
  • Built-in governance vs. L2 access layer

And if at this point we introduced the Scrypta Trustlines? Let’s play here a little about the role of spoilers … Certain sources and very close to the world of Scrypta have informed us that in a few days will be released a very interesting feature that takes the name of Trustline(-s).

With “Trustline” Scrypta defines that system of voluntary trust lines, established by two or more users, which allow them to exchange information and write data blockchain. The trustlines are in fact the addresses of the Scrypta network that are generated by the voluntary consent of two or more legacy addresses. The creation of an account called “multi-signature” will enable the creation of transactions of a common type, whose transmission and validity takes place only if both parties voluntarily affix their digital signature.

A Trustline will therefore constitute a real digital contract.

One of the main uses of this feature will be the supply chain world: using a customer and supplier Trustline will establish a real certified commercial channel. In this way they could immediately regulate the relationship by signing a contract, accepted by both parties, and from here to “digitally” establish all the exchanges of the process that once transited and written on blockchain would be immutable and would in effect be legal.