We'll explain how to connect your Chainlink node to our EaaS
Running a Chainlink node with our Ethereum-as-a-Service (EaaS) is probably the easiest way to run a chainlink node on your own. It combines the security of having full control over your funds while giving you reliable access to the Ethereum blockchain. Essentially, you can run your Chainlink node on the Amazon AWS free tier or use free credits from Google Cloud Platform – your only expense would be our service!
1. Create an API key
Getting started is really easy. Head over to dashboard.fiews.io and sign up for an account. It will require you to verify your email before you can proceed, but you should receive the email within minutes. Once verified, create a new subscription. While we offer our free trial, an API key will be provided instantly. It will look something like this: 8q8Hv7NfZGxh4yc9JiiRAoCdvKwzSz5TUexkku0Rql. This is all you need to do on the website.
For the next step, head over to your server/machine that's running your Chainlink node. In the .env file, you need to change some values. We will explain what each value is. Feel free to change between tabs to select the network you want to use. Do note that all values change based on which network you are connecting to.
ETH_URL tells your Chainlink node how to communicate with your Ethereum node. Since you are using our EaaS, we'll set this to our relevant URL. Remember to change yourapikey to the API key you generated earlier.
ETH_CHAIN_ID lets your Chainlink node which chain you are connecting to.
LINK_CONTRACT_ADDRESS defines the LINK token address for the chain you are using. Please refer to the official documentation for details.
3. Run your node!
If you have completed the above steps, all you have to do is run your node! Check your logs and make sure there are no errors. You should soon new headers coming in. If everything seems to be working, you are done! Though, there are usually something that didn't go as planned when setting it up, and an error could show up. But don't worry, they are usually easy to fix! Head over to troubleshooting to see the most common mistakes.