Go Node and SDK for the NEO blockchain
Find a file
2022-12-06 13:15:10 +03:00
.circleci circleci: update golangci-lint to current version 2022-09-02 18:36:26 +03:00
.docker wallet: fix wallet version to conform to NEP-6 2022-08-07 22:41:40 +03:00
.github .github: fix condition for adding latest tag to buider job 2022-11-15 16:16:02 +03:00
cli cli/vm: use tx system fee by default 2022-11-20 16:02:50 +03:00
config config: move NeoFS mainnet Aspidochelone fork again 2022-11-07 10:40:30 +03:00
docs rpcsrv: make websocket client limit configurable 2022-11-23 12:19:49 +03:00
examples nft-nd-nns: update neo-go dependency to drop btcec 2022-11-08 18:10:01 +03:00
internal rpcclient: fix WS-client unsubscription process 2022-11-16 23:44:30 +03:00
pkg compiler: Contract type is in the management package 2022-12-06 13:15:10 +03:00
scripts scripts: ignore go 1.16 compat for dependency updator script 2022-09-23 09:05:08 +03:00
.dockerignore Fix build node and docker-image 2019-08-26 19:32:09 +03:00
.gitignore rpc/server: move to services/rpcsrv 2022-07-21 22:14:12 +03:00
.gitmodules vm: update json tests to neo3 branch 2020-04-17 11:46:31 +03:00
.golangci.yml golangci: enable some more linters 2022-09-02 18:36:26 +03:00
CHANGELOG.md CHANGELOG: release 0.99.7 2022-11-23 16:21:51 +03:00
codecov.yml codecov: adjust codecov config and remove CircleCI coverage job 2022-02-03 16:21:15 +03:00
CONTRIBUTING.md [#2442] English Check 2022-05-04 19:48:27 +03:00
Dockerfile Dockerfile: honor VERSION and REPO during make build 2022-07-21 18:20:46 +03:00
Dockerfile.wsc ci: update workflows' go version 2022-08-09 15:37:59 +03:00
go.mod keys: move from btcd/btcec to decred/secp256k1 package 2022-11-08 17:59:59 +03:00
go.sum keys: move from btcd/btcec to decred/secp256k1 package 2022-11-08 17:59:59 +03:00
LICENSE.md LICENSE.md: add NSPCC copyright 2022-04-04 12:34:18 +03:00
Makefile .github: update deprecated workflows 2022-11-15 16:16:01 +03:00
neo-go.service.template service file templating 2019-11-13 15:05:13 +03:00
README.md README: drop stale Go 1.16 reference 2022-09-08 21:18:02 +03:00
ROADMAP.md ROADMAP: add deprecated code removal schedule 2022-11-10 17:57:03 +03:00

logo

Go Node and SDK for the Neo blockchain.


codecov CircleCI GithubWorkflows Tests Report GoDoc GitHub release (latest SemVer) License

Overview

This project aims to be a full port of the original C# Neo project. A complete toolkit for the NEO blockchain, including:

This branch (master) is Neo N3-compatible. For the current Legacy-compatible version please refer to the master-2.x branch and releases before 0.80.0 (0.7X.Y track).

Getting started

Installation

NeoGo is distributed as a single binary that includes all the functionality provided (but smart contract compiler requires Go compiler to operate). You can grab it from releases page, use a Docker image (see Docker Hub for various releases of NeoGo, :latest points to the latest release) or build yourself.

Building

To build NeoGo you need Go 1.17+ and make:

make build

The resulting binary is bin/neo-go.

Building on Windows

To build NeoGo on Windows platform we recommend you to install make from MinGW package. Then, you can build NeoGo with:

make build

The resulting binary is bin/neo-go.exe.

We also recommend you to switch the Windows Firewall off for further NeoGo node run.

Running a node

A node needs to connect to some network, either local one (usually referred to as privnet) or public (like mainnet or testnet). Network configuration is stored in a file and NeoGo allows you to store multiple files in one directory (./config by default) and easily switch between them using network flags.

To start Neo node on a private network, use:

./bin/neo-go node

Or specify a different network with an appropriate flag like this:

./bin/neo-go node --mainnet

Available network flags:

  • --mainnet, -m
  • --privnet, -p
  • --testnet, -t

To run a consensus/committee node, refer to consensus documentation.

Docker

By default, the CMD is set to run a node on privnet. So, to do this, simply run:

docker run -d --name neo-go -p 20332:20332 -p 20331:20331 nspccdev/neo-go

Which will start a node on privnet and expose node's ports 20332 (P2P protocol) and 20331 (JSON-RPC server).

Importing mainnet/testnet dump files

If you want to jump-start your mainnet or testnet node with chain archives provided by NGD, follow these instructions:

$ wget .../chain.acc.zip # chain dump file
$ unzip chain.acc.zip
$ ./bin/neo-go db restore -m -i chain.acc # for testnet use '-t' flag instead of '-m'

The process differs from the C# node in that block importing is a separate mode. After it ends, the node can be started normally.

Running a private network

Refer to consensus node documentation.

Smart contract development

Please refer to neo-go smart contract development workshop that shows some simple contracts that can be compiled/deployed/run using neo-go compiler, SDK and a private network. For details on how Go code is translated to Neo VM bytecode and what you can and can not do in a smart contract, please refer to the compiler documentation.

Refer to examples for more NEO smart contract examples written in Go.

Wallets

NeoGo differs substantially from C# implementation in its approach to wallets. NeoGo wallet is just a NEP-6 file that is used by CLI commands to sign various things. There is no database behind it, the blockchain is the database and CLI commands use RPC to query data from it. At the same time, it's not required to open a wallet on an RPC node to perform various actions (unless your node provides some service for the network like consensus or oracle nodes do).

Developer notes

Nodes have such features as Prometheus and Pprof in order to have additional information about them for debugging.

How to configure Prometheus or Pprof: In config/protocol.*.yml there is

  Prometheus:
    Enabled: true
    Port: 2112

where you can switch on/off and define port. Prometheus is enabled and Pprof is disabled by default.

Contributing

Feel free to contribute to this project after reading the contributing guidelines.

Before starting to work on a certain topic, create a new issue first describing the feature/topic you are going to implement.

Contact

License

  • Open-source MIT