Node Management Index: Difference between revisions
From Chainlink Community Wiki
No edit summary |
No edit summary |
||
Line 29: | Line 29: | ||
Below you will find example jobspecs for each job type that the Chainlink Node Supports | Below you will find example jobspecs for each job type that the Chainlink Node Supports | ||
==== '''Direct Request Example''' ==== | ===== '''Direct Request Example''' ===== | ||
Please click above to navigate to Direct Request (DR) / RunLog (RL) example spec | Please click above to navigate to Direct Request (DR) / RunLog (RL) example spec | ||
Revision as of 20:10, 23 May 2022
Node Management Index
The purpose of this page is to provide an index of content made available to you on this wiki.
This content is either not indexed elsewhere, or does not exist at all elsewhere.
Environment Variable Details
When you deploy a Chainlink Node, you need to create a .env file to include in your container's instantiation.
When you deploy a Chainlink Node, you need to create a .env file to include in your container's instantiation.
The purpose of this file is to override the default configuration your Chainlink node would set without it.
Job Management
Chainlink Nodes require jobs in order for them to know what is expected of them.
Chainlink Nodes require jobs in order for them to know what is expected of them.
Example JobSpecs
Below you will find example jobspecs for each job type that the Chainlink Node Supports
Direct Request Example
Please click above to navigate to Direct Request (DR) / RunLog (RL) example spec
FluxMonitor Example
Please click above to navigate to FluxMonitor (FM) example spec
Off Chain Reporting Example
Please click above to navigate to Off Chain Reporting (OCR) example spec
Bridge Management
What is a Chainlink Bridge?
Adding / Replacing / Removing Bridges
This page will provide directions on managing your bridges and all potential "gotchas" that you may run into
Key Managmeent
Chainlink Node Account Private Keys
The Chainlink Node manages its own wallet's private keys keys for each network type it supports. At the time of this writing, that includes Layer One and Layer Two EVM chains, Solana, and Terra.
These wallets are responsible for paying the transaction fees associated with writing data on-chain for each network.