To create ELI5 graphs (Explain Like I'm Five) for different Blockchain and DLTs projects. I designed all the graphs using agile-architecture own project and approach using graphviz and dot language.
Status: WIP
ILP is an intermediary layer to interoperate between different Blockchain or DLTs. Interoperatibility
The purpose of the interledger protocol is to enable hosts to route payments through an interconnected set of ledgers. This is done by passing the payments from one interledger module to another until the destination is reached. The interledger modules reside in hosts and connectors in the interledger system. The payments are routed from one interledger module to another through individual ledgers based on the interpretation of an interledger address. Thus, a central component of the interledger protocol is the interledger address.
Graph above show Interledger Protocol Architecture (ILP). There are 4 options path for a payment from Sender to Receiver:
- a) Blue path: Using only 1 connector + 1 ledger (Apparently Cheaper). Blue path failed because Sender didn't accept the Quote in step 3.
- b) Green path: Using more than a connector + ledger (Apparently Expensive)
- c) Red path: Timeout expire or Receiver hasn't the right private key. So the asset roll back through all the connector and ledgers involved.
- d) Black path: N/A, It is not used, just to an example to show how ILP routing features works, so the black workflow is not used: Connector_D, ledger_D asset_D asset_H asset_I asset_J asset_X asset_Y asset_Z
"Apparently", Blue path seems the cheapest because less Ledger involved less fees involved, but ILP is about multi-hop payments and it could be possible than multiple chain connectors is cheaper than 1 connector due the fees and another ledger performance factors because connectors could agreed and interchange assets with another transactions in transit to reduce costs.
-
Ledger: Store Records. Ledger in ILP could be decentralized(1 entity) or decentralized(n entities) blockchain or DLTs. 1 Ledger track 1 Asset. An important Ledger feature in ILP it can support positive or negative balances, so it could maintain assets or liabilities. Architecture above show multiple assets and liability_R.
-
Connector: Normally ILP manage it as a Plugin, as it is a program to speak with different ledgers. It gets revenue when transfer from one connector to another. It creates a smart contract inside the blockchain/ledger with a timeout and a transaction agreed by 2 parties: sender and receiver. Connectors also generate quotes.
-
Asset: It represents any abstract/logical value, the balance is saved in the blockchain/ledger. As usually in blockchains, assets could be used only when provide the private key. Asset and liabilities are the same but asset is unlock with owner private key and liability is unlock with counter party owner private key.
### Workflow explanation by Arrows number
- Sender init the payment choosing asset_A as mutual asset between Sender and Receiver
- Connector_A prepare a quote and offer to Sender
- Sender reject the Connector_A quote
- Connector_B confirm than Receiver hasn't Asset_B through the Ledger_B and the Receiver Public key and prepare another quote(Ledger_B) to send to another Connector in the network.
- Connector_B request Connector_C to check the same and transfer the operation and his quote to Connector_C
- Connector_C confirm Receiver has Asset_C checking in ledger_C by Receiver public key and send the quote for Connector_B and Connector_C to Sender
- Sender accept the quote so the payment start
- Connector_B write in ledger_B the info and fee
- Connector_C write in ledger_C the info and fee
- If receiver has the right private key and accept the payment within the time agreed, then Receiver get the Asset. Otherwise rollback operation start and the Asset return to the Sender automatically through all the red path.
- asset_C balance is saved into Ledger_C and Receiver have access to asset_C.
Sender choose the Asset to do the payment and accept a quote for the connector chain, once quote(and connector chain) is accepted payment start. Receiver could get the payment through asset_A or asset_C.
- Could the receiver choose the asset to get the payment? I understood no, because if receiver could choose which asset to receive it could unfair due the fee is payed by the sender only.
Status: WIP
Status: WIP
Hyperledger is a strategic umbrella under the Linux Foundation which incubates and promotes a range of business blockchain technologies, framework, libraries, interfaces and applications.
- Multi-purpose blockchain
- IBM flavour
- Permissioned blockchain: Permissions setup in System level, User level, Contract level. Through certificates.
- Pluggable consensus: Practical Byzantine Fault Tolerance (PBFT) Sieve.
- Operations required, you must build and maintain your own Blockchain Infrastructure and integrate with your Architecture base.
- DApps development with smart contracts. DApps and Smart Contracts in Hyperledger Fabric is called Chaincodes.
- Strong granular Permission system. First, There are channels to isolate and build sub-blockchains. Second, It is possible to deploy Chaincodes to the channels and add users to the channels. Third, you can restrict the input data to chaincode. Fourth, you can hash or encrypt the data before calling the chaincode. Fifth, you can restrict data access to certain roles in your organization, setting access control in the Chaincode level. And finally, you can encrypt ledger data via filesystem encryption in the Node, and data in-transit is encrypted via TLS.
- Chaincode support Golang, but you could use any programming language supported by Hyperledger Fabric, there are another language options to be fully supported Javascript. You can develop Chaincode applications with Hyperledger Composer
- It hasn´t a native cryptocurrency due it is a private blockchain and consensus mechanism is via a sub-set peer nodes. But you could develop your own digital asset(aka token or crypto) through a Chaincode itself if it is required in your Use Case or integrate with some public blockchain with a cryptocurrency.
- IoT blockchain purpose
- Intel flavour
- Mobile blockchain
- Soramitsu Flavour
Hyperledger Fabric Framework and Package managment
Blockchain benchamark tool
###Hyperledger Cello Deployment tooling
###Hyperledger Explorer Analytics tooling
###Hyperledger Indy Supporting independent identity
Status: WIP
- Permissionless blockchain to access and operate in the network, thats mean Public, all is broadcast to all nodes.
- Operation-less, you don't need build and maintain infrastructure
- Consensus: PoW (Homestead version) with CPU and Memory (ASIC-proof) + PoS (Serenity version)
- Private key to lock Addresses and Smart Contracts
- Dapps development with smart contracts.
- Crypto-fuel (aka Gas) to use the blockchain to compute, transfer and storage. You use cryptocurrency Ether(ETH) to pay for gas.
- Miners are the validators, running on commodity hardware
- Smart Contracts coded with Solidity
Basically:
- Green arrows represent sync workflow for all the public ethereum network
- Black arrows represent components whichever node has and actions could run
I wont't draw again the cpp-ethereum architecture as it is already designed with graphviz also here:
Status: WIP
- Permissioned blockchain to access and operate in the network, thats mean Private. You build the network between all the parties you want involve, nobody else.
- With Infrastructure, you need build your node and maintain your infrastructure
- Consensus: Multi Consensus algorithm: RAFT, BFT or whichever. You can have multiple notaries with different consensus algorithms.
- Private key to lock Addresses and Smart Contracts
- CordaDapps development with smart contracts
- Cryptocurrency is not required to use the network, so nobody pays for any transaction.
- There aren't miners, there are notaries
- Contracts are written in Java or Kotlin and running in JVM
Basically:
- Green arrows represent the PKI and Corda Doorman Admission Infrastructure
- Blue arrows represent a permissioned private Corda network with their isolated Facts subset
- Orange arrows represent another permissioned private Corda and facts subset
- Brown arrows represent another permissioned private Corda and facts subset
- rest of Workflow... TO-DO...