Official repository for the golang Celo Blockchain
Official golang implementation of the Celo blockchain, based off of the official golang implementation of the Ethereum protocol.
Documentation for Celo more generally can be found at docs.celo.org
Most functionality of this client is similar to
go-ethereum, also known as
geth, from which it was forked. If you do not find your question answered by Celo-specific documentation, try searching the geth wiki.
gethrequires both a Go (version 1.16) and a C compiler. You can install them using your favourite package manager. Once the dependencies are installed, run
or, to build the full suite of utilities:
There are two different commands in the
Makefileto build the
androidcommand it applies a git patch (
patches/mobileLibsForBuild.patch) required to swap some libs from the
go.modfor the client to work, installs those libs, builds the client, and then reverts the patch.
The Celo blockchain client comes with several wrappers/executables found in the
| Command | Description | |:----------:|-------------| |
geth| The main Celo Blockchain client. It is the entry point into the Celo network, capable of running as a full node (default), archive node (retaining all historical state), light node (retrieving data live), or lightest node (retrieving minimum number of block headers to verify existing validator set). It can be used by other processes as a gateway into the Celo network via JSON RPC endpoints exposed on top of HTTP, WebSocket and/or IPC transports.
geth --helpand the Ethereum CLI Wiki page for command line options. | |
abigen| Source code generator to convert Celo contract definitions into easy to use, compile-time type-safe Go packages. It operates on plain Ethereum contract ABIs with expanded functionality if the contract bytecode is also available. However it also accepts Solidity source files, making development much more streamlined. Please see Ethereum's Native DApps wiki page for details. | |
bootnode| Stripped down version of the Celo client implementation that only takes part in the network node discovery protocol, but does not run any of the higher level application protocols. It can be used as a lightweight bootstrap node to aid in finding peers in private networks. | |
evm| Developer utility version of the EVM (Ethereum Virtual Machine) that is capable of running bytecode snippets within a configurable environment and execution mode. Its purpose is to allow isolated, fine-grained debugging of EVM opcodes (e.g.
evm --code 60ff60ff --debug run). | |
gethrpctest| Developer utility tool to support the ethereum/rpc-test test suite which validates baseline conformity to the Ethereum JSON RPC specs. Please see the ethereum test suite's readme for details. | |
rlpdump| Developer utility tool to convert binary RLP (Recursive Length Prefix) dumps (data encoding used by the Celo protocol both network as well as consensus wise) to user friendlier hierarchical representation (e.g.
rlpdump --hex CE0183FFFFFFC4C304050583616263). |
Please see the docs.celo.org/getting-started for instructions on how to run a node connected the Celo network using the prebuilt Docker image.
Going through all the possible command line flags is out of scope here, please consult
geth --helpfor more complete information. We've enumerated a few common parameter combos to get you up to speed quickly on how you can run your own Celo blockchain client instance.
By default, the Celo client will connect to the Mainnet. Running the following command will create a full node that will sync with the Celo network and allow access to all of its functionality.
$ geth console
This command will: * Start
gethin full sync mode which will download and execute all historical block information. * Start up
consolesubcommand) through which you can invoke all official
web3methods as well as
geth's own management APIs. This tool is optional and if you leave it out you can always attach to an already running
Smart contract developers will be most interested in the Alfajores testnet. On Alfajores, you can receive testnet Celo Gold through the Alfajores faucet and deploy smart contracts in an environment very similar to Mainnet. More information about the Alfajores testnet can be found on docs.celo.org.
$ geth --alfajores console
Note: Although there are some internal protective measures to prevent transactions from crossing over between the main network and test network, you should make sure to always use separate accounts for testnet-tokens and real-tokens. Unless you manually move accounts,
gethwill by default correctly separate the two networks and will not make any accounts available between them.
Validators and full node operators will be most interested in the Baklava testnet. On Baklava, you can receive a distribution of testnet Celo Gold to become a validator on the network and test out running a validator for the first time, or try out new infrastructure. More information about the Baklava testnet can be found on docs.celo.org. A full guide to getting started as a validator on Baklava can be found in the Getting Started guides
$ geth --baklava console
As an alternative to passing the numerous flags to the
Celobinary, you can also pass a configuration file via:
$ geth --config /path/to/your_config.toml
To get an idea how the file should look like you can use the
dumpconfigsubcommand to export your existing configuration:
$ geth --your-favourite-flags dumpconfig
As a developer, sooner rather than later you'll want to start interacting with
gethand the Celo network via your own programs and not manually through the console. To aid this,
gethhas built-in support for a JSON-RPC based APIs (standard APIs and
gethspecific APIs). These can be exposed via HTTP, WebSockets and IPC (UNIX sockets on UNIX based platforms, and named pipes on Windows).
The IPC interface is enabled by default and exposes all the APIs supported by
geth, whereas the HTTP and WS interfaces need to manually be enabled and only expose a subset of APIs due to security reasons. These can be turned on/off and configured as you'd expect.
HTTP based JSON-RPC API options:
--rpcEnable the HTTP-RPC server
--rpcaddrHTTP-RPC server listening interface (default:
--rpcportHTTP-RPC server listening port (default:
--rpcapiAPI's offered over the HTTP-RPC interface (default:
--rpccorsdomainComma separated list of domains from which to accept cross origin requests (browser enforced)
--wsEnable the WS-RPC server
--wsaddrWS-RPC server listening interface (default:
--wsportWS-RPC server listening port (default:
--wsapiAPI's offered over the WS-RPC interface (default:
--wsoriginsOrigins from which to accept websockets requests
--ipcdisableDisable the IPC-RPC server
--ipcapiAPI's offered over the IPC-RPC interface (default:
--ipcpathFilename for IPC socket/pipe within the datadir (explicit paths escape it)
You'll need to use your own programming environments' capabilities (libraries, tools, etc) to connect via HTTP, WS or IPC to a
gethnode configured with the above flags and you'll need to speak JSON-RPC on all transports. You can reuse the same connection for multiple requests!
Note: Please understand the security implications of opening up an HTTP/WS based transport before doing so! Hackers on the internet are actively trying to subvert Celo nodes with exposed APIs! Further, all browser tabs can access locally running web servers, so malicious web pages could try to subvert locally available APIs!
Thank you for considering to help out with the source code! We welcome contributions from anyone on the internet, and are grateful for even the smallest of fixes!
If you'd like to contribute to celo-blockchain, please fork, fix, commit and send a pull request for the maintainers to review and merge into the main code base. If you wish to submit more complex changes though, please check up with the core devs first on the official Celo forum to ensure those changes are in line with the general philosophy of the project and/or get some early feedback which can make both your efforts much lighter as well as our review and merge procedures quick and simple.
Please make sure your contributions adhere to our coding guidelines:
If you come across a bug, pleas open a GitHub issue with information about your build and what happened.
We run a circle CI test suite on each PR. The following tests are required to merge a PR. * Unit tests:
./build/env.sh go run build/ci.go test* Lint:
make lint(Fix go format errors with
gofmt -s) * Build:
make* End to end sync and transfer tests * Check imports:
celo-blockchainis based on
go-ethereum, but the import path has been renamed from
github.com/celo-org/celo-blockchain. Developers are encouraged to run
./scripts/setup_git_hooks.shto enable checking that import path has been changed to
git commit. Imports can automatically be renamed with
Individual package tests can be run with
./build/env.sh go test github.com/celo-org/celo-blockchain/$(PATH_TO_GO_PACKAGE)if you don't have
Once a PR is approved, adding on the
automergelabel will keep it up to date and do a squash merge once all the required tests have passed.
Golang has built in support for running benchmarks with go tool
go test -run=ThisIsNotATestName -bench=. ./$PACKAGE_NAMEwill run all benchmarks in a package.
One note around running benchmarks is that
BenchmarkHandlePreprepareis quite takes a while to run, particularly when testing with a larger number of validators. Substituting
-bench=.will specify which tests to run. Adding
-cpuprofile=cpu.outwhich can be visualized with
go tool pprof -html:8080 cpu.outif
The celo-blockchain library (i.e. all code outside of the
cmddirectory) is licensed under the GNU Lesser General Public License v3.0, also included in our repository in the
The celo-blockchain binaries (i.e. all code inside of the
cmddirectory) is licensed under the GNU General Public License v3.0, also included in our repository in the