Sawtooth PirateTalk

An example Hyperledger Sawtooth application, built to be a companion to blockchain presentations given at Open Source North, MidwestJS, and ConFoo. This simple app nonetheless showcases a number of components commonly function in a full stack Sawtooth app:

• Javascript client transaction submission
• REST API state delta subscriptions
• A docker-compose based deployment of core validator components
• Javascript, Python, and Rust transaction processors
• Seth Solidity smart contracts (WIP)
• Sabre WASM smart contracts (WIP)

Contents

• Usage
  • Docker Cheatsheet
    • Building/Destroying
    • Starting/Stopping
    • Running commands from within a container
• Slides
• License

Usage

This entire app can be run just using only Docker. Simply follow the install instructions specific to your OS, and then run:

git clone https://github.com/delventhalz/pirate-talk.git
cd pirate-talk/
docker-compose up

This will take a long time to build and install the first time, 30 minutes or more. In the future it will be much faster, 30 seconds or less.

Once running, you can navigate to localhost:8080 to use the client and submit transactions. Submitted transactions should then appear in your console as the transaction processors handle them.

Docker Cheatsheet

Here is a list of useful docker commands you might use when working with this project. Note that most of these can be entered from a separate terminal while docker-compose up is still running.

Building/Destroying

Build and start all components:

docker-compose up

Stop with ctrl-C, and/or stop and destroy all components:

docker-compose down -v

Starting/Stopping

Restart a particular component (e.g. "pirate-tp", other components listed in docker-compose.yaml):

docker restart pirate-tp

Stop a component:

docker stop pirate-tp

Start a stopped component:

docker start pirate-tp

Running commands from within a container

It is possible to enter a Docker container to use bash. This is sometimes useful for various development tasks, especially if you do not have dependencies installed locally. Note that within a Docker container URLs are now based on the name of the service in docker-compose.yaml. For example, the Sawtooth REST API would go from http://localhost:8008 to http://rest-api:8008.

Entering a container with bash:

docker exec -it pirate-tp bash

Exiting a container

exit

Slides

The slides from the latest version of the talk are available on Google Slides.

License

The source code of this project is licensed for reuse under the Apache License Version 2.0.

Slides and original written material are licensed under Creative Commons Attribution 4.0.