d4d1c79546
This is a nice VM, it has an interesting stack items model, better separation of elements from stack implementation, simpler stack implementation and a bit nicer opcode implementation mechanism. At the same time it lacks so many features and is so differing from our current VM (that is closely tied to the compiler) that it makes its code very hard to reuse for master's VM improvement. Also, some differences are non-obvious to judge in terms of better or worse. Stack item model seems to be more extensible, but at the same time we know very well what kind of stack items we have and this doesn't change a lot. Slice-based stack is simple but it's hard to say which one would perform better for real-world smart contracts (it has different tradeoffs in operations complexity). Based on that, I'm dropping it. Some ideas will be reused during VM refactoring, but no more than that. Refs. #307. |
||
---|---|---|
.circleci | ||
.github | ||
_pkg.dev | ||
cli | ||
config | ||
docs | ||
examples | ||
pkg | ||
.dockerignore | ||
.gitignore | ||
.travis.yml | ||
CONTRIBUTING.md | ||
docker-compose.yml | ||
Dockerfile | ||
go.mod | ||
go.sum | ||
LICENSE.md | ||
Makefile | ||
README.md | ||
ROADMAP.md |
Go Node and SDK for the NEO blockchain.
Overview
This project aims to be a full port of the original C# NEO project. A complete toolkit for the NEO blockchain, including:
- Consensus node (WIP)
- RPC node & client
- RPC client
- CLI tool
- Smart contract compiler
- NEO virtual machine
Getting started
Installation
Go: 1.11+
Install dependencies.
neo-go
uses GoModules as dependency manager:
make deps
How to setup a node
Docker
Each tagged build is built to docker hub and the :latest
tag pointing at the latest tagged build.
By default the CMD
is set to run a node on testnet
, so to do this simply run:
docker run -d --name neo-go -p 20332:20332 -p 20333:20333 cityofzion/neo-go
Which will start a node on testnet
and expose the nodes port 20333
and 20332
for the JSON-RPC
server.
Building
Build the neo-go CLI:
make build
Quick start a NEO node on the private network. This requires the neo-privatenet Docker image running on your machine.
make run
To run the binary directly:
./bin/neo-go node
By default the node will run on the private network
, to change his:
./bin/neo-go node --mainnet
Available network flags:
--mainnet, -m
--privnet, -p
--testnet, -t
Contributing
Feel free to contribute to this project after reading the contributing guidelines.
Before starting to work on a certain topic, create an new issue first, describing the feature/topic you are going to implement.
Contact
- @roman-khimov on GitHub
- @volekerb on Github
- Reach out to us on the NEO Discord channel
License
- Open-source MIT