Official golang implementation of the Bytom classic protocol.
Automated builds are available for stable releases and the unstable master branch. Binary archives are published at https://github.com/Bytom/bytom-classic/releases.
Bytom classic is software designed to operate and connect to highly scalable blockchain networks confirming to the Bytom classic Blockchain Protocol, which allows partipicants to define, issue and transfer digitial assets on a multi-asset shared ledger. Please refer to the White Paper for more details.
In the current state bytom classic is able to:
- Manage key, account as well as asset
- Send transactions, i.e., issue, spend and retire asset
brew tap bytom/bytom-classic && brew install bytom-classic
- Go version 1.8 or higher, with
$GOPATHset to your preferred directory
Ensure Go with the supported version is installed properly:
$ go version
$ go env GOROOT GOPATH- Get the source code
$ git clone https://github.com/Bytom/bytom-classic.git $GOPATH/src/github.com/bytom/bytom-classic- Build source code
$ cd $GOPATH/src/github.com/bytom/bytom-classic
$ GO111MODULE=off make bytomcd # build bytom-classic daemon
$ GO111MODULE=off make bytomccli # build bytom-classic command lineWhen successfully building the project, the bytomd and bytomcli binary should be present in cmd/bytomcd and cmd/bytomccli directory, respectively.
The Bytom project comes with several executables found in the cmd directory.
| Command | Description |
|---|---|
| bytomcd | bytomd command can help to initialize and launch bytom domain by custom parameters. bytomcd --help for command line options. |
| bytomccli | Our main Bytom CLI client. It is the entry point into the Bytom network (main-, test- or private net), capable of running as a full node archive node (retaining all historical state). It can be used by other processes as a gateway into the Bytom network via JSON RPC endpoints exposed on top of HTTP, WebSocket and/or IPC transports. bytomccli --help and the bytomccli Wiki page for command line options. |
Currently, bytom classic is still in active development and a ton of work needs to be done, but we also provide the following content for these eager to do something with bytom classic. This section won't cover all the commands of bytomcd and bytomccli at length, for more information, please the help of every command, e.g., bytomccli help.
First of all, initialize the node:
$ cd ./cmd/bytomcd
$ ./bytomcd init --chain_id mainnetThere are three options for the flag --chain_id:
mainnet: connect to the mainnet.testnet: connect to the testnet wisdom.solonet: standalone mode.
After that, you'll see config.toml generated, then launch the node.
$ ./bytomcd nodeavailable flags for bytomcd node:
Flags:
--auth.disable Disable rpc access authenticate
--chain_id string Select network type
-h, --help help for node
--log_file string Log output file (default "log")
--log_level string Select log level(debug, info, warn, error or fatal)
--mining Enable mining
--p2p.dial_timeout int Set dial timeout (default 3)
--p2p.handshake_timeout int Set handshake timeout (default 30)
--p2p.keep_dial string Peers addresses try keeping connecting to, separated by ',' (for example "1.1.1.1:46657;2.2.2.2:46658")
--p2p.laddr string Node listen address. (0.0.0.0:0 means any interface, any port) (default "tcp://0.0.0.0:46656")
--p2p.lan_discoverable Whether the node can be discovered by nodes in the LAN (default true)
--p2p.max_num_peers int Set max num peers (default 50)
--p2p.node_key string Node key for p2p communication
--p2p.proxy_address string Connect via SOCKS5 proxy (eg. 127.0.0.1:1086)
--p2p.proxy_password string Password for proxy server
--p2p.proxy_username string Username for proxy server
--p2p.seeds string Comma delimited host:port seed nodes
--p2p.skip_upnp Skip UPNP configuration
--prof_laddr string Use http to profile bytomd programs
--simd.enable Enable SIMD mechan for tensority
--vault_mode Run in the offline enviroment
--wallet.disable Disable wallet
--wallet.rescan Rescan wallet
--wallet.txindex Save global tx index
--web.closed Lanch web browser or not
--ws.max_num_concurrent_reqs int Max number of concurrent websocket requests that may be processed concurrently (default 20)
--ws.max_num_websockets int Max number of websocket connections (default 25)
Global Flags:
--home string root directory for config and data
-r, --root string DEPRECATED. Use --home (default "/Users/zcc/Library/Application Support/Bytomclassic")
--trace print out full stack trace on errors
Given the bytomcd node is running, the general workflow is as follows:
- create key, then you can create account and asset.
- send transaction, i.e., build, sign and submit transaction.
- query all kinds of information, let's say, avaliable key, account, key, balances, transactions, etc.
simd feature:
You could enable the simd feature to speed up the PoW verification (e.g., during mining and block verification) by simply:
bytomcd node --simd.enable
To enable this feature you will need to compile from the source code by yourself, and make bytomcd-simd.
What is more,
- if you are using Mac, please make sure llvm is installed by
brew install llvm. - if you are using Windows, please make sure mingw-w64 is installed and set up the PATH environment variable accordingly.
For more details about using bytomcli command please refer to API Reference
Access the dashboard:
$ open http://localhost:9888/
Ensure your Docker version is 17.05 or higher.
$ docker build -t bytom-classic .For the usage please refer to running-in-docker-wiki.
Thank you for considering helping out with the source code! Any contributions are highly appreciated, and we are grateful for even the smallest of fixes!
If you run into an issue, feel free to bytom classic issues in this repository. We are glad to help!