https://github.com/aviaviavi/legion
Simple blockchain server written in Haskell for educational purposes
https://github.com/aviaviavi/legion
blockchain haskell peer-network
Last synced: about 5 hours ago
JSON representation
Simple blockchain server written in Haskell for educational purposes
- Host: GitHub
- URL: https://github.com/aviaviavi/legion
- Owner: aviaviavi
- License: mit
- Created: 2017-04-12T06:51:49.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2018-03-01T08:19:04.000Z (about 7 years ago)
- Last Synced: 2024-11-12T10:46:49.667Z (6 months ago)
- Topics: blockchain, haskell, peer-network
- Language: Haskell
- Homepage:
- Size: 33.2 KB
- Stars: 601
- Watchers: 14
- Forks: 38
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Legion - a simple blockchain implementation
[](https://travis-ci.org/aviaviavi/legion)
An as-simple-as-possible blockchain server inspired by [naivechain](https://github.com/lhartikk/naivechain), but written in Haskell. Spinning up several
Legion nodes creates a peer to peer network that syncronizes the block chain across the network.
Prereqs: To compile from source, you'll need [stack](https://docs.haskellstack.org/en/stable/README/).
Alternatively, you can get a precompiled [pre-release binary](https://github.com/aviaviavi/legion/releases). Note: if you download the binary
from github, you'll need to mark it executable by running:
```
$ chmod +x legion-exe
```
### Usage:
```
$ stack exec legion-exe [http port] [p2p port] [optional: `seedhost:seedP2PPort`]
```
### Examples:
```
$ stack exec legion-exe 8001 9001
```
By default, legion will log what it's doing to standard out. In another terminal window:
```
$ stack exec legion-exe 8002 9002 localhost:9001
```
Alternatively, you grab the binaries from the github releases, and run that directly rather than via `stack exec`
The 3rd argument tells the node where a seed node can be found to bootstrap the connection to the
peer to peer network. The current state of the (valid) blockchain will be fetched from all servers, and it will automatically
keep itself updated and post its own updated to others.
Now that 2 nodes are now synced, and you can view the current chain from either node at http://localhost:$httpPort/chain, eg http://localhost:8001/chain
Add a new block to the blockchain via a POST request to /block:
```
$ curl -H "Content-Type: application/json" -X POST -d '{"blockBody": "this is the data for the next block"}' http://localhost:8001/block
```