Here you find some general information about integrations regardless of your service or use case:
There are a myriad of ways through which you can access chain data:
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.
geth will use
/root/.celo as the data dir, if you would like to change that specify the
This is all you should need to connect to a network:
For more command line options, please see https://github.com/ethereum/go-ethereum/wiki/Command-Line-Options
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
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.
Alfajores = 'https://alfajores-forno.celo-testnet.org'Baklava = 'https://baklava-forno.celo-testnet.org'Mainnet = 'https://rc1-forno.celo-testnet.org'
We also expose data on the cLabs run blockscout instance. Blockscout itself exposes an API.
Alfajores = 'https://alfajores-blockscout.celo-testnet.org'Baklava = 'https://baklava-blockscout.celo-testnet.org'Mainnet = 'https://explorer.celo.org/'
Compared to Ethereum transaction, Celo transactions have 3 additional, optional fields:
feeCurrency - Specifies the address of the currency in which fees should be paid. If
null, the native token
CELO is assumed.
gatewayFeeRecipient - As part of Full Node Incentives, light clients will need to specify the address of their gateway for it to forward the transactions onto the network.
gatewayFee - The value of the gateway fee.
To sign transactions, you have the following options: