Node Management Index: Difference between revisions
From Chainlink Community Wiki
No edit summary Tag: Reverted |
No edit summary Tag: Manual revert |
||
| Line 34: | Line 34: | ||
---- | ---- | ||
=== ''' | === '''Key Managmeent''' === | ||
==== [[Node Key Management|'''Chainlink Node Account Private Keys''']] ==== | ==== [[Node Key Management|'''Chainlink Node Account Private Keys''']] ==== | ||
Revision as of 19:39, 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.
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.
This section will provide example job specs, under which will be an explanation for all of the data in each jobspec.
Example JobSpecs
Direct Request Example
FluxMonitor Example
Off Chain Reporting Example
Bridge Management
What is a Chainlink Bridge?
Adding / Replacing / Removing Bridges
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.