celo-org / celo-blockchain

Official repository for the golang Celo Blockchain

Celo Blockchain

Official golang implementation of the Celo blockchain, based off of the official golang implementation of the Ethereum protocol.

Prebuilt Docker images are available for immediate use: us.gcr.io/celo-org/geth. See docs.celo.org/getting-started for a guide to the Celo networks and how to get started.

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.

Building the source

Building geth requires both Go (min version 1.19) and a C compiler. You can install them using your favourite package manager. Once the dependencies are installed, run

make geth

or, to build the full suite of utilities:

make all

Mobile Clients

There are two different commands in the Makefile to build the ios and the android clients.

make ios

and

make android

Note: The android command it applies a git patch (patches/mobileLibsForBuild.patch) required to swap some libs from the go.mod for the client to work, installs those libs, builds the client, and then reverts the patch.

Executables

The Celo blockchain client comes with several wrappers/executables found in the cmd directory.

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 --help and 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).

Running tests

Prior to running tests you will need to run make prepare, this will run two sub rules.

Without first running this make prepare, certain tests will fail.

prepare-system-contracts

This will shallow checkout the celo-monorepo under ../.celo-blockchain-monorepo-checkout relative to this project's root at the commit defined in the file monorepo_commit. Then it will compile the system contracts for use in full network tests. The rule will copy the compiled contracts from celo-monorepo to compiled-system-contracts. If you subsequently edit the system contracts source or monorepo_commit, running the make rule again will re-checkout the monorepo, re-compile the contracts and copy them into place.

monorepo_commit may contain a commit hash or a tag, branch names are forbidden.

In the case that you would like to change the default monorepo checkout location, or that you would like to have multiple checkouts of the monorepo (at different versions) you can set the MONOREPO_PATH variable in the make command, for example:

make prepare-system-contracts MONOREPO_PATH=../alt-monorepo

Note that MONOREPO_PATH should not be set to point at checkouts other than those checked out by the prepare-system-contracts rule, and the checkouts created by the prepare-system-contracts rule should not be manually modified, aside from changing the contract source.

prepare-ethersjs-project

This will install dependencies for the ethersjs-api-check typescript project.

Running Celo

Please see the docs.celo.org/getting-started for instructions on how to run a node connected to the Celo network using the prebuilt Docker image.

Going through all the possible command line flags is out of scope here, please consult geth --help for 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.

Full node on the main Celo network

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 geth in full sync mode which will download and execute all historical block information.
• Start up geth's built-in interactive JavaScript console, (via the trailing console subcommand) through which you can invoke all official web3 methods 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 geth instance with geth attach.

A Full node on the Alfajores test network

Smart contract developers will be most interested in the Alfajores testnet. On Alfajores, you can receive testnet Celo 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, geth will by default correctly separate the two networks and will not make any accounts available between them.

Full node on the Baklava test network

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

Configuration

As an alternative to passing the numerous flags to the Celo binary, you can also pass a configuration file via:

$ geth --config /path/to/your_config.toml

To get an idea of how the file should look like you can use the dumpconfig subcommand to export your existing configuration:

$ geth --your-favourite-flags dumpconfig

Programmatically interfacing geth nodes

As a developer, sooner rather than later you'll want to start interacting with geth and the Celo network via your own programs and not manually through the console. To aid this, geth has built-in support for a JSON-RPC based APIs (standard APIs and geth specific 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:

• --http Enable the HTTP-RPC server
• --http.addr HTTP-RPC server listening interface (default: localhost)
• --http.port HTTP-RPC server listening port (default: 8545)
• --http.api API's offered over the HTTP-RPC interface (default: eth,net,web3)
• --http.corsdomain Comma separated list of domains from which to accept cross origin requests (browser enforced)
• --ws Enable the WS-RPC server
• --ws.addr WS-RPC server listening interface (default: localhost)
• --ws.port WS-RPC server listening port (default: 8546)
• --ws.api API's offered over the WS-RPC interface (default: eth,net,web3)
• --ws.origins value Origins from which to accept websockets requests
• --graphql Enable GraphQL on the HTTP-RPC server. Note that GraphQL can only be started if an HTTP server is started as well.
• --graphql.corsdomain value Comma separated list of domains from which to accept cross origin requests (browser enforced)
• --graphql.vhosts value Comma separated list of virtual hostnames from which to accept requests (server enforced). Accepts '*' wildcard. (default: "localhost")
• --ipcdisable Disable the IPC-RPC server
• --ipcapi API's offered over the IPC-RPC interface (default: admin,debug,eth,miner,net,personal,shh,txpool,web3)
• --ipcpath Filename 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 geth node 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!

Contribution

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:

• Code must adhere to the official Go formatting guidelines (i.e. uses gofmt).
• Code must be documented adhering to the official Go commentary guidelines.
• Pull requests need to be based on and opened against the master branch.
• Commit messages should be prefixed with the package(s) they modify.
  • E.g. "eth, rpc: make trace configs optional"

Submitting an issue

If you come across a bug, please open a GitHub issue with information about your build and what happened.

CI Testing and automerge

We run a circle CI test suite on each PR. The following tests are required to merge a PR.

• Unit tests: make test or ./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: ./scripts/check_imports.sh

celo-blockchain is based on go-ethereum, but the import path has been renamed from github.com/ethereum/go-ethereum to github.com/celo-org/celo-blockchain. Developers are encouraged to run ./scripts/setup_git_hooks.sh to enable checking that import path has been changed to celo-org on git merge and git commit. Imports can automatically be renamed with ./scripts/rename_imports.sh.

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 GOPATH set-up.

Once a PR is approved, adding on the automerge label will keep it up to date and do a squash merge once all the required tests have passed.

Benchmarking

Golang has built-in support for running benchmarks with go tool go test -run=ThisIsNotATestName -bench=. ./$PACKAGE_NAME will run all benchmarks in a package.

One note around running benchmarks is that BenchmarkHandlePreprepare is quite takes a while to run, particularly when testing with a larger number of validators. Substituting -bench=REGEX for -bench=. will specify which tests to run. Adding -cpuprofile=cpu.out which can be visualized with go tool pprof -html:8080 cpu.out if graphviz is installed.

See the go testing flags and go docs for more information on benchmarking.

License

The celo-blockchain library (i.e. all code outside of the cmd directory) is licensed under the GNU Lesser General Public License v3.0, also included in our repository in the COPYING.LESSER file.

The celo-blockchain binaries (i.e. all code inside of the cmd directory) is licensed under the GNU General Public License v3.0, also included in our repository in the COPYING file.

celo-blockchain's Issues

Mobile pilot users SBAT pay no transaction fees during the pilot

Expected Behavior

Please describe the behavior you are expecting

Current Behavior

What is the current behavior?

Developers SBAT to reference geth docker images automatically

Expected Behavior

We should CI/CD docker images, possibly on GCP

Current Behavior

Developers have to build docker images manually

Developers SBAT run a script with instructions to deploy Geth

Expected Behavior

Please describe the behavior you are expecting

Current Behavior

What is the current behavior?

[geth] Tests should pass

Expected Behavior

Tests should pass

Current Behavior

Tests don't pass

MIT challenge users SBAT run a Celo node

Expected Behavior

Users will need access to the Celo binary

Current Behavior

Private repo

Developers SBAT use testnets that are as representative as possible of the mainnet

Understand how Ethereum and ZCash launched their mainnet, e.g. what did they do to build mining power? community? how did they stage the roll-out? what would they do differently today? etc. to better define our path to mainnet launch.

Developers SBAT test ABE functions

Expected Behavior

Tests should exist for abe/abe.go

Current Behavior

No tests exist for abe/abe.go

Developers SBAT unit test ABE module

Expected Behavior

Please describe the behavior you are expecting

Current Behavior

What is the current behavior?

[geth] Set up CircleCI

Expected Behavior

CircleCI should be set up and prevent us from checking in commits that break the tests.

Current Behavior

CircleCI is not set up.

Users SBAT interact with gold via the ERC20 interface

Expected Behavior

Users should be able to call all ERC20 contract functions on Gold. One way to do this would be to implement "transfer" and "lookup" precompiled contracts, callable only by the GoldToken contract.

Current Behavior

In order to get ERC20 functionality we wrap gold

Developers SBAT know who to ask for code reviews

Expected Behavior

Subdirectories are owned by certain users, who are required to approve PRs touching that code.

Current Behavior

Things are done ad-hoc.

Developers SBAT always keep mobile geth updated

Expected Behavior

We should never have to think about rebuilding mobile geth

Current Behavior

We have to rebuild on every merge to master and update mobile package.json

Users SBAT to reveal their phone number without sending a transaction

Expected Behavior

Users SBAT send their encrypted phone number to the target verifier node without sending a transaction, via whisper or the gossip protocol.

Current Behavior

Users send their encrypted phone number via a transaction, which is then run by the verifier node when the block is mined.

Reset clique consensus around future blocks

Expected Behavior

We don't have to allow future blocks

Current Behavior

We need future blocks for PoA

Miners SBAT decrypt revealed phone numbers always

Expected Behavior

Verification always works.

Current Behavior

We saw an issue where the miner wasn't able to decrypt the phone number.

Light Clients SBAT to connect to nodes on the same network

Expected Behavior

When multiple light clients are on the same network, they should still be able to connect to the same node.

Current Behavior,

Due to ethereum/go-ethereum#16899 (comment), currently light clients cannot have the same IP address

Current workaround

We made a modification in #41 to change the identification of a peer by IP address to their enode address. This loosens our ability to actually identify badly behaving clients but allows us to continue to use our Kubernetes setup as well as have multiple light clients on the same network.

Get errors and crash info from mobile geth

regular logs -> stdout, actual errors -> stderr -> Sentry ?

Developers SBAT reference a demo branch

Expected Behavior

We should have a branch for the current demo

Current Behavior

No demo branch

Developers SBAT deploy Geth and retain state

Expected Behavior

Redeploy and retain state

Current Behavior

State is nuked on helm upgrade

Anyone SNBAT call the testmsg precompiled contract

Expected Behavior

This contract should only be able to be called by the AddressBasedEncryption contract

Current Behavior

Anyone can call it

Miners SBAT verify that the previous block header was signed correctly

Expected Behavior

As part of validating a block miners should extract the public key from the previous block header and verify that it matches the block coinbase.

Current Behavior

No validation is done on the signature.

Devs SBAT get successful or pending transactions metrics in geth

Expected Behavior

We get successful or pending transactions metrics in geth

Current Behavior

We can't get successful or pending transactions metrics in geth

Developers SBAT reference staging and prod builds in geth

• staging
• production

Users SBAT pay for transactions in the same currency as transaction

Expected Behavior

A user shouldn't have to worry about having a balance of Celo Gold just to make Celo Dollar transactions.

Current Behavior

Right now you need Celo Gold to pay for gas, even if you are just sending Celo Dollars.

Test failure in types.DecodeVerificationRequest

panic: runtime error: slice bounds out of range [recovered]
	panic: runtime error: slice bounds out of range

goroutine 21199 [running]:
testing.tRunner.func1(0xc052ac8800)
	/usr/local/Cellar/go/1.11/libexec/src/testing/testing.go:792 +0x387
panic(0x444b0a0, 0x48777d0)
	/usr/local/Cellar/go/1.11/libexec/src/runtime/panic.go:513 +0x1b9
github.com/ethereum/go-ethereum/core/types.DecodeVerificationRequest(0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
	/Users/tim/Celo/geth/build/_workspace/src/github.com/ethereum/go-ethereum/core/types/receipt.go:123 +0x670
github.com/ethereum/go-ethereum/core/vm.opCall(0xc051a96478, 0xc029c9f500, 0xc01634d440, 0xc00c11cd00, 0xc00c11cd20, 0x2bc, 0x1388, 0x32, 0x61a8, 0xc029c9ca80)
	/Users/tim/Celo/geth/build/_workspace/src/github.com/ethereum/go-ethereum/core/vm/instructions.go:754 +0x81b
github.com/ethereum/go-ethereum/core/vm.(*EVMInterpreter).Run(0xc029c9f500, 0xc01634d440, 0xc00022c1b0, 0x44, 0x90, 0x441a800, 0x0, 0x0, 0x0, 0x0, ...)
	/Users/tim/Celo/geth/build/_workspace/src/github.com/ethereum/go-ethereum/core/vm/interpreter.go:257 +0x5fa
github.com/ethereum/go-ethereum/core/vm.run(0xc029c9ca80, 0xc01634d440, 0xc00022c1b0, 0x44, 0x90, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
	/Users/tim/Celo/geth/build/_workspace/src/github.com/ethereum/go-ethereum/core/vm/evm.go:68 +0x230
github.com/ethereum/go-ethereum/core/vm.(*EVM).Call(0xc029c9ca80, 0x4579e80, 0xc001dd24c0, 0xb3dedd8ce29a870e, 0x5a5054b39d5a401a, 0xbdb06055, 0xc00022c1b0, 0x44, 0x90, 0x94858, ...)
	/Users/tim/Celo/geth/build/_workspace/src/github.com/ethereum/go-ethereum/core/vm/evm.go:240 +0x4f7
github.com/ethereum/go-ethereum/core.(*StateTransition).TransitionDb(0xc0542498f0, 0x457efe0, 0xc0037577a0, 0xc051a96420, 0xc0542498f0, 0x10, 0xc00c11cb01, 0xc051a96430)
	/Users/tim/Celo/geth/build/_workspace/src/github.com/ethereum/go-ethereum/core/state_transition.go:213 +0x3c3
github.com/ethereum/go-ethereum/core.ApplyMessage(0xc029c9ca80, 0x457efe0, 0xc0037577a0, 0xc051a96420, 0x1, 0xc051a96430, 0x0, 0x1, 0x4e6f9da04a5c7968, 0x30adc2f8dddee5d3, ...)
	/Users/tim/Celo/geth/build/_workspace/src/github.com/ethereum/go-ethereum/core/state_transition.go:132 +0x5b
github.com/ethereum/go-ethereum/tests.(*StateTest).Run(0xc0522be000, 0xc0524e7050, 0x6, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
	/Users/tim/Celo/geth/build/_workspace/src/github.com/ethereum/go-ethereum/tests/state_test_util.go:143 +0x4de
github.com/ethereum/go-ethereum/tests.TestState.func1.1.1(0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
	/Users/tim/Celo/geth/build/_workspace/src/github.com/ethereum/go-ethereum/tests/state_test.go:60 +0xb5
github.com/ethereum/go-ethereum/tests.withTrace(0xc052ac8800, 0x99cf0, 0xc053dbdf50)
	/Users/tim/Celo/geth/build/_workspace/src/github.com/ethereum/go-ethereum/tests/state_test.go:72 +0x67
github.com/ethereum/go-ethereum/tests.TestState.func1.1(0xc052ac8800)
	/Users/tim/Celo/geth/build/_workspace/src/github.com/ethereum/go-ethereum/tests/state_test.go:59 +0x175
testing.tRunner(0xc052ac8800, 0xc05230f140)
	/usr/local/Cellar/go/1.11/libexec/src/testing/testing.go:827 +0xbf
created by testing.(*T).Run
	/usr/local/Cellar/go/1.11/libexec/src/testing/testing.go:878 +0x353
FAIL	github.com/ethereum/go-ethereum/tests	49.366s

Developers SBAT know if mobile can use V5 discovery

We turned off V5 discovery and not sure if this is necessary

[geth] Users/contracts SBAT call v0.2 of the requestVerification instruction

Expected Behavior

Contracts SBAT send encrypted phone numbers, the geth node should then decrypt the phone number and send a text with the verification code.

Current Behavior

Phone numbers are sent in plain text.

Developers SBAT use fixes in geth 1.8.16

Merge and test upstream changes in
https://github.com/ethereum/go-ethereum/releases/tag/v1.8.16

Devs SBAT reference requirements doc for consensus

Developers SBAT unit test PoA changes

Expected Behavior

Please describe the behavior you are expecting

Current Behavior

What is the current behavior?

Adapt ethereum foundation tests for Celo

Go Ethereum uses a test suite that is shared on other clients to assert its compliance with the ethereum protocol. It doesn't work for celo since our protocol is different, hence we don't use it.

We want to adapt it and use it for our blockchain.

Check
https://github.com/ethereum/tests/tree/ad2184adca367c0b68c65b44519dba16e1d0b9e2

Developers SBAT to use the same geth version for the bootnode and normal nodes

Expected Behavior

It should connect to the bootnode

Current Behavior

@asaj in his attempted deploy of a network set the bootnode tag to be 9568b4a305e6a51b4f4b48dfd3e8bee505ee83cc as they are currently set for all the other geth nodes. However, that resulted in all the geth nodes being unable to connect to the bootnode with the following error:

Bootstrap URL invalid enode=enode://d576d9d033023258a24cf55cd391e32fd4e2bf6bc5bff13d364e30bad2101e6a@10.20.6.43:30301 err="invalid node ID (wrong length, want 128 hex chars)" "

I found the following SO answer https://stackoverflow.com/questions/52835449/the-output-length-of-bootnode-writeaddress-command-is-64-bytes-not-128-bytes-a that leads to ethereum/go-ethereum#17643

What I don't quite get is why verificationrewards, the tag that predates our merge of upstream geth is the one bootnode version that is compatible with the rest of the geth nodes, vs. 9568b4a305e6a51b4f4b48dfd3e8bee505ee83cc which includes upstream is seemingly not compatible. My guess its somewhere around defaults of which p2p protocol we are using, but haven't dug deeper

Developers SBAT write unit tests

Expected Behavior

We should decide on a unit testing method, be that choosing a testing framework or conventions for our own tests. I've used Ginkgo with Gomega before, a typical unit testing framework with a DSL similar to mocha's.

Current Behavior

From a quick browse through the repo, looks like there's a bunch of different approaches to testing being used.

Developers SBAT know that the network is resilient to attacks

Network testing / penetration testiing

Developers SBAT permission precompiled contracts

Expected Behavior

Some precompiled contracts should only be called by certain contracts, we have no way of enforcing this.

Current Behavior

We don't do this

Users SBAT verify international phone numbers

Expected Behavior

International phone numbers should be able to be verified. E164

Current Behavior

Our regex currently checks the decrypted phone number against a regex which will only match for US phone numbers.

Developers SBAT unit test Celo precompiled contracts

Expected Behavior

Please describe the behavior you are expecting

Current Behavior

What is the current behavior?

Celo core RPC users SBAT pay for transactions in CG or C$

Implement https://docs.google.com/document/d/1p2W9Efrgy0BCe39WipVjXUqnlgip_G1KdX_9Va5BxTY/edit#

[geth] Developers SBAT access block.coinbase in solidity on a PoA testnet

Expected Behavior

block.coinbase should return the address of the current block miner when running on a proof of authority testnet.

Current Behavior

block.coinbase is always set to 0x0 when using PoA

Nodes SBAT run a custom opcode that sends a text

https://ethereum.stackexchange.com/questions/51580/how-can-we-implement-a-new-opcode-in-the-ethereum-virtual-machine

Miners SBAT to run a Celo node and earn Celo Gold

Plan to build mining power

Users SBAT pay transaction fees in any first-class currency

Expected Behavior

https://docs.google.com/document/d/1p2W9Efrgy0BCe39WipVjXUqnlgip_G1KdX_9Va5BxTY/edit

Current Behavior

Fees are paid exclusively in gold

[geth] Up script should add miner 1 as peer to miner 0

Expected Behavior

Up script should automatically connect the two miners

Current Behavior

Miners need to be made aware of each other manually

dialHistoryExpiration should be set to 30s

Expected Behavior

Nodes should wait 30s between redialing another node

Current Behavior

Set to 10s as a hack because the nodes in our PoA testnet continually disconnect

Developers SBAT delete docker script

Expected Behavior

Should be able to use original geth dockerfile.

Current Behavior

Added an extra dockerfile.

Users SBAT have usually free transactions in first month of pilot

Expected Behavior

When load is not high, miners will accept transactions with gasprice=0

Miners SBAT select the verification service they use

Expected Behavior

We will allow miners to set their own URL for their verification service.

Current Behavior

All miners use the same verification service. It is a URL that is hardcoded into Geth.

Light clients SBAT not get kicked by "too many peers" from the network

Users SBAT re-map their phone number to a new address

I can't map my phone number my new address, which is why when I'm sent funds they don't appear in my balance.

To repro:

1. Compute the address at which your actual address is stored:
   const hash = web3.utils.sha3('8579988722').slice(26)
   console.log(0x${hash})

2. Check the balance at that address to confirm that it's mapped to your current address:
   yarn run get-balances VALUE_LOGGED_IN_1
   Convert the gold balance amount to hex to get the address

3. Clear Celo app storage, reload, faucet your new address some money, and reverify

4. Rerun step 2, see that the balance did not change

Miners SBAT specify the verification reward recipient

Expected Behavior

Miners can specify who will receive the reward for completed verifications. In the short term, this can be the verification pool's wallet address, longer term, a Terms of Service contract published by the verification pool that splits rewards between the miner and the pool.

This is the geth compliment to celo-org/celo-monorepo#738

Current Behavior

Verification rewards are always credited to the miner.