Skip to main content


General information about integrations regardless of your service or use case.

Accessing the chain

There are a myriad of ways through which you can access chain data:

Running your own node

To be completely independent and have a reliable view into the latest chain data, you will likely want to run your own node(s).

You can just clone celo-blockchain and then run make geth to receive the binary.

By default, geth will use /root/.celo as the data dir, if you would like to change that specify the --datadir argument.

This is all you should need to connect to a network:

For Mainnet:


For Alfajores:

geth --alfajores

For Baklava:

geth --baklava

For more command line options, please see


Forno is a hosted node service for interacting with the Celo network. This allow the user to get connected to the Celo Blockchain without having to run its own node.

Can be used as an Http Provider with ContractKit

As Forno is a public node you will have to sign transactions locally because with your own private key, because Forno doesn't store them. But don't worry, the ContractKit will handle this for you.

Forno networks:

Alfajores = ''

Baklava = ''

Mainnet = ''


We also expose data on the cLabs run blockscout instance. Blockscout itself exposes an API.

Alfajores = ''

Baklava = ''

Mainnet = ''

Signing Transactions

Compared to Ethereum transactions, Celo transactions have an additional optional field:

  • feeCurrency - Specifies the address of the currency in which fees should be paid. If null, the native token CELO is assumed.

To sign transactions, you have the following options:

  • Use the JSON-RPC sendTransaction method to your node which would have the account in question unlocked. (Either manually or via a library such as web3)
  • Use ContractKit's local signing feature.