Difference between revisions of "IT-SDK-Hyperledger-Sawtooth"
Jump to navigation
Jump to search
Samerhijazi (talk | contribs) (→Architektur) |
Samerhijazi (talk | contribs) (→Architektur) |
||
| Line 6: | Line 6: | ||
=Architektur= | =Architektur= | ||
| + | * Source: https://github.com/samerhijazi/studying/blob/main/sawtooth/sawtooth-start.yml | ||
| + | ==Key-Words== | ||
* Validator: checks and ensures that a transaction has a valid signature and directs it to the appropriate transaction processor | * Validator: checks and ensures that a transaction has a valid signature and directs it to the appropriate transaction processor | ||
* REST-API: | * REST-API: | ||
| Line 11: | Line 13: | ||
* TransactionProcessors: Applications that initiates smart contracts. | * TransactionProcessors: Applications that initiates smart contracts. | ||
* Consensus: Each network participant waits a randomly-assigned amount of time. The first one to finish waiting becomes the producer of the next block. | * Consensus: Each network participant waits a randomly-assigned amount of time. The first one to finish waiting becomes the producer of the next block. | ||
| + | ==Components== | ||
| + | * Validator: @validator | ||
| + | * REST-API: @rest-api | ||
| + | * CLI: @cli | ||
| + | * TransactionProcessors: @settingTP, @intkeyTP | ||
| + | * Consensus: @devEngine (Devmode consensus engine); @engineA (PoET: Proof-of-Elapsed-Time) | ||
=Key-Words= | =Key-Words= | ||
Revision as of 00:36, 28 December 2020
Contents
Source
- https://www.hyperledger.org/projects/sawtooth
- https://sawtooth.hyperledger.org/faq/
- https://sawtooth.hyperledger.org/docs/core/releases/latest/
- https://www.blockchain-council.org/hyperledger/architecture-of-hyperledger-sawtooth-a-comprehensive-overview/
Architektur
Key-Words
- Validator: checks and ensures that a transaction has a valid signature and directs it to the appropriate transaction processor
- REST-API:
- CLI: Command-Line-Interface
- TransactionProcessors: Applications that initiates smart contracts.
- Consensus: Each network participant waits a randomly-assigned amount of time. The first one to finish waiting becomes the producer of the next block.
Components
- Validator: @validator
- REST-API: @rest-api
- CLI: @cli
- TransactionProcessors: @settingTP, @intkeyTP
- Consensus: @devEngine (Devmode consensus engine); @engineA (PoET: Proof-of-Elapsed-Time)
Key-Words
- Commands: sawtooth keygen, sawset
- Genesis Block, Genesis Batch, Validators Genesis Block
- Keys: Public-Key, Private-Key, Validator-Key, Transactor-Key
- Validator, Transactor, Validator network, Validator key generation, User key generation
- Sawtooth Validator, Sawtooth IntegerKey, Sawtooth PoET, Sawtooth XO,
Explory
Contrary to how we start other blockchains, we do not start bootstrapping Hyperledger Sawtooth with the genesis block creation. We must begin by generating public and private keys for both our user and validator.
Commands
sawtooth-validator -v \ --bind “component:tcp://eth0:8000” \ --bind “network:tcp://eth0:8080” \ --bind “consensus:tcp://eth0:7070” --endpoint “tcp://validatorOne:8080”
System-Setup
sudo apt update sudo apt install curl git apt-transport-https ca-certificates gnupg-agent software-properties-common ... curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" sudo apt update sudo apt install docker-ce docker-ce-cli containerd.io sudo groupadd docker sudo usermod -aG docker $USER
