Difference between revisions of "IT-SDK-Hyperledger-Sawtooth"
Jump to navigation
Jump to search
Samerhijazi (talk | contribs) (→Source) |
Samerhijazi (talk | contribs) (→Key-Words) |
||
| Line 5: | Line 5: | ||
* https://www.blockchain-council.org/hyperledger/architecture-of-hyperledger-sawtooth-a-comprehensive-overview/ | * https://www.blockchain-council.org/hyperledger/architecture-of-hyperledger-sawtooth-a-comprehensive-overview/ | ||
| + | =Architektur= | ||
| + | * Clients | ||
| + | * REST-API | ||
| + | * Transaction processors: they handle the business logic. | ||
| + | * Consensus engine: is responsible for determining who can publish a block. | ||
| + | * Validator: verify the entity who is allowed to issue blocks and batches. | ||
=Key-Words= | =Key-Words= | ||
* Commands: sawtooth keygen, sawset | * Commands: sawtooth keygen, sawset | ||
Revision as of 12:33, 11 April 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
- Clients
- REST-API
- Transaction processors: they handle the business logic.
- Consensus engine: is responsible for determining who can publish a block.
- Validator: verify the entity who is allowed to issue blocks and batches.
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”
