Chainlink is middleware to simplify communication with blockchains. Here you'll find the Chainlink Golang node, currently in alpha. This initial implementation is intended for use and review by developers, and will go on to form the basis for Chainlink's decentralized oracle network. Further development of the Chainlink Node and Chainlink Network will happen here, if you are interested in contributing please see our contribution guidelines. The current node supports:
- easy connectivity of on-chain contracts to any off-chain computation or API
- multiple methods for scheduling both on-chain and off-chain computation for a user's smart contract
- automatic gas price bumping to prevent stuck transactions, assuring your data is delivered in a timely manner
- push notification of smart contract state changes to off-chain systems, by tracking Ethereum logs
- translation of various off-chain data types into EVM consumable types and transactions
- easy to implement smart contract libraries for connecting smart contracts directly to their preferred oracles
- easy to install node, which runs natively across operating systems, blazingly fast, and with a low memory footprint
Examples of how to utilize and integrate Chainlinks can be found in the examples directory.
- Install Go 1.12+, and add your GOPATH's bin directory to your PATH
- Install NodeJS & Yarn
- Download Chainlink:
git clone https://github.com/smartcontractkit/chainlink && cd chainlink
- Build and install Chainlink:
- Run the node:
Ethereum Node Requirements
In order to run the Chainlink node you must have access to a running Ethereum node with an open websocket connection. Any Ethereum based network will work once you've configured the chain ID. Ethereum node versions currently tested and supported:
NOTE: By default, chainlink will run in TLS mode. For local development you can either disable this by setting CHAINLINK_DEV to true, or generate self signed certificates using
tools/bin/self-signed-certs or manually.
To start your Chainlink node, simply run:
$ chainlink local node
By default this will start on port 6688, where it exposes a REST API.
Once your node has started, you can view your current jobs with:
$ chainlink jobspecs
View details of a specific job with:
$ chainlink show $JOB_ID
To find out more about the Chainlink CLI, you can always run
You can configure your node's behavior by setting environment variables which can be, along with default values that get used if no corresponding environment variable is found. The latest information on configuration variables are available in the docs.
This project contains several sub-projects, some with their own documentation.
- evm - smart contract-related resources
- @chainlink/contracts - smart contract-related resources
- examples - collection of example Chainlink integrations
- testnet - guide to creating, deploying and using Chainlinked smart contracts
- explorer - Chainlink Explorer
- integration/forks - integration test for ommers and re-orgs
- sgx - experimental, optional module that can be loaded into Chainlink to do processing within an SGX enclave
- styleguide - Chainlink style guide
- tools - Chainlink tools
External adapters are what make Chainlink easily extensible, providing simple integration of custom computations and specialized APIs. A Chainlink node communicates with external adapters via a simple REST API.
For more information on creating and using external adapters, please see our external adapters page.
For the latest information on setting up a development environment, see the guide here.
Build your current version
$ go build -o chainlink ./core/
- Run the binary:
$ yarn $ yarn setup:contracts
- Ready for testing:
$ go test -parallel=1 ./...
- Install Yarn
- Install the dependencies:
$ cd evm $ yarn install
- Run tests:
$ yarn run test-sol
Use of Go Generate
Go generate is used to generate mocks in this project. Mocks are generate with mockery and live in core/internal/mocks.
For more tips on how to build and test Chainlink, see our development tips page.
Chainlink's source code is licensed under the MIT License, and contributions are welcome.
Please check out our contributing guidelines for more details.