Chainlink

Chainlink expands the capabilities of smart contracts by enabling access to real-world data and off-chain computation while maintaining the security and reliability guarantees inherent to blockchain technology. This repo contains the Chainlink core node and contracts. The core node is the bundled binary available to be run by node operators participating in a decentralized oracle network. All major release versions have pre-built docker images available for download from the Chainlink dockerhub. If you are interested in contributing please see our contribution guidelines. If you are here to report a bug or request a feature, please check currently open Issues. For more information about how to get started with Chainlink, check our official documentation. Chainlink has an active and ever growing community. Discord is the primary communication channel used for day to day communication, answering development questions, and aggregating Chainlink related content. Take a look at the community docs for more information regarding Chainlink social accounts, news, and networking. For the latest information on setting up a development environment, see the Development Setup Guide. 1. Send a workflow dispatch event from our docker-build workflow. 2. Add the build-publish label to your PR and then either retry the docker-build workflow, or push a new commit. Plugins are defined in yaml files within the plugins/ directory. Each plugin file is a yaml file and has a plugins. prefix name. Plugins are installed with loopinstall. Some plugins (such as those in plugins/plugins.private.yaml ) reference private GitHub repositories. To build these plugins, you must have a GITHUB TOKEN environment variable set, or preferably use the gh GitHub CLI tool to use the GitHub CLI credential helper like: 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: [Supported but broken] These clients are supported by Chainlink, but have bugs that prevent Chainlink from working reliably on these execution clients. Nethermind Blocking issues: ~ Erigon Blocking issues: - We cannot recommend specific version numbers for ethereum nodes since the software is being continually updated, but you should usually try to run the latest version available. NOTE : By default, chainlink will run in TLS mode. For local development you can disable this by using a dev build using make chainlink-dev and setting the TOML fields: To find out more about the Chainlink CLI, you can always run chainlink help . Check out the doc pages on Jobs to learn more about how to create Jobs. Check the official documentation for more information on how to configure your node. 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. We use cosign with OIDC keyless signing during the Build, Sign and Publish Chainlink workflow. It is encourage for any node operator building from the official Chainlink docker image to verify the tagged release version was did indeed built from this workflow. The tests require a postgres database. In turn, the environment variable CL DATABASE URL must be set to value that can connect to test database, and the user must be able to create and drop the given test database. There helper script for initial setup to create an appropriate test user. It requires postgres to be running on localhost at port 5432. You will be prompted for the postgres user password Changes to database require migrations to be run. Similarly, pull 'ing the repo may require migrations to run. After the one-time setup above: Use make test which h