neo-go

module
v0.98.5 Latest Latest
Warning

This package is not in the latest version of its module.

Go to latest
Published: May 13, 2022 License: MIT

README

logo

Go Node and SDK for the Neo blockchain.


codecov CircleCI GithubWorkflows Tests GithubWorkflows CodeQL 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.16+ 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 private network use:

./bin/neo-go node

Or specify a different network with 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 (when they'd be available for 3.0 networks):

$ 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 private network. For details on how Go code is translated to Neo VM bytecode and what you can and can not do in 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 the wallet on RPC node to perform various actions (unless your node is providing some service for the network like consensus or oracle nodes).

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 an new issue first, describing the feature/topic you are going to implement.

Contact

License

  • Open-source MIT

Directories

Path Synopsis
cli
options
Package options contains a set of common CLI options and helper functions to use them.
Package options contains a set of common CLI options and helper functions to use them.
vm
examples
engine Module
events Module
iterator Module
nft-nd Module
nft-nd-nns Module
oracle Module
runtime Module
storage Module
timer Module
token Module
token-sale Module
internal
pkg
compiler
Package compiler implements Go to NEF smart contract compiler.
Package compiler implements Go to NEF smart contract compiler.
config
Package config contains NeoGo node configuration definition.
Package config contains NeoGo node configuration definition.
config/netmode
Package netmode contains well-known network magic numbers.
Package netmode contains well-known network magic numbers.
consensus
Package consensus contains Neo consensus node implementation.
Package consensus contains Neo consensus node implementation.
core
Package core implements Neo ledger functionality.
Package core implements Neo ledger functionality.
core/block
Package block contains Neo block definition.
Package block contains Neo block definition.
core/interop
Package interop contains implementations of Neo interop functions.
Package interop contains implementations of Neo interop functions.
core/mpt
Package mpt implements MPT (Merkle-Patricia Tree).
Package mpt implements MPT (Merkle-Patricia Tree).
core/native
Package native contains Neo native contracts.
Package native contains Neo native contracts.
core/statesync
Package statesync implements module for the P2P state synchronisation process.
Package statesync implements module for the P2P state synchronisation process.
core/transaction
Package transaction contains Neo transaction definition.
Package transaction contains Neo transaction definition.
crypto
Package crypto contains implementation of crypto functions used by Neo.
Package crypto contains implementation of crypto functions used by Neo.
crypto/hash
Package hash contains wrappers for Neo hashing algorithms.
Package hash contains wrappers for Neo hashing algorithms.
crypto/keys
Package keys wraps public/private keys and implements NEP-2 and WIF.
Package keys wraps public/private keys and implements NEP-2 and WIF.
encoding/address
Package address implements conversion of script hash to/from Neo address.
Package address implements conversion of script hash to/from Neo address.
encoding/base58
Package base58 wraps generic base58 encoder with NEO-specific checksumming.
Package base58 wraps generic base58 encoder with NEO-specific checksumming.
encoding/bigint
Package bigint implements Neo-specific big.Int (de)serialization to/from []byte.
Package bigint implements Neo-specific big.Int (de)serialization to/from []byte.
encoding/fixedn
Package fixedn implements fixed point integers with arbitrary precision.
Package fixedn implements fixed point integers with arbitrary precision.
io
rpc
rpc/client
Package client implements NEO-specific JSON-RPC 2.0 client.
Package client implements NEO-specific JSON-RPC 2.0 client.
smartcontract/manifest/standard
Package standard contains interfaces for well-defined standards and function for checking if arbitrary manifest complies with them.
Package standard contains interfaces for well-defined standards and function for checking if arbitrary manifest complies with them.
util/bitfield
Package bitfield provides a simple and efficient arbitrary size bit field implementation.
Package bitfield provides a simple and efficient arbitrary size bit field implementation.
util/slice
Package slice contains byte slice helpers.
Package slice contains byte slice helpers.
vm
interop Module
scripts

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL