Chainlink Automation
Links:
Dashboard: Chainlink Automation
Doc: https://docs.chain.link/chainlink-automation
Usage in Fury Racing:
As mentioned in the previous paragraph, Chainlink Automation has been introduced to remove the need for traditional Cron jobs. This came with another massive advantage. In the initial setup, a Cron Job triggering an AWS Lambda serverless function via CloudWatch BridgeEvents had been implemented. While working fine, it was necessary to store the private key on AWS to complete the smart contract call from the Lambda function.
However, thanks to Chainlink Automation, this is not needed anymore. So not only the Lambda function can be removed, but since Chainlink Automation is handling the contract call for us, the private key can be removed as well, increasing the overall security of the app. As shown in the chart below, compromised keys are still one of the most common causes of hacks in the web3 space.
History of Chainlink Automation calls:
Last updated
