To note, the hardware requirements depend upon the oracle services your node provides and the blockchain networks you support
The hardware needed for a Chainlink node delivering data to Ethereum is lower than a node delivering to higher throughput chain like BSC or Polygon
It's also dependent on how many jobs you're running
If you're doing one job an hour, the minimum is probably fine, if you're doing 100 jobs/minute, you'll need a bit more
This is all a part of Chainlink's heterogeneous design and is very different than a monolithic blockchain
Running a Chainlink node is not like running a blockchain node, because it's not a monolithic network
Data requesters select which nodes they want in their own oracle network, choosen based on each node's individual historical performance, reputation, and eventually stake
Therefore running a Chainlink node is like running a business
You have to convince data requesters to choose your node over others, creating inter-node competition due to Chainlink's free market economy (capitalism) design blog.chain.link/how-chainlink-…
• • •
Missing some Tweet in this thread? You can try to
force a refresh
"Developers will soon be able to call the @dxFeedSolutions Chainlink node to access $BTC and $ETH options analytics data, including implied volatilities for options markets"
"We’re excited to announce that @FarmHeroIO — a cross chain #DEFI protocol that combines yield farming, #NFT and gaming — has integrated #Chainlink Verifiable Random Function (VRF) on the @0xPolygon mainnet"
"We’re excited to announce that @bunicornswap — the all-in-one BSC-powered DEX — will integrate #Chainlink Verifiable Random Function (VRF) on the #BinanceSmartChain blockchain"
"Our developer bootcamp will give developers across the globe a hands-on, guided experience to begin building with #Solidity smart contracts and @Chainlink oracles to create the next generation of hybrid smart contracts"
"[@SynapseNetwork_ has integrated] #Chainlink VRF to fairly select participants in IDO launches, #Chainlink Price Feeds to determine exchange rates on our native SNP token, and #Chainlink Keepers to automate our staking and vesting contracts"
2/ Data provider run nodes (e.g. Kaiko, Nomics, etc) leverage their own server infrastructure to operate their Chainlink nodes
This indeed requires operational expertise in oracle & blockchain infrastructure, because this is mission critical infrastructure with billions at stake
3/ Data provider approved nodes leverage infrastructure from service providers to bootstrap their Chainlink node (like how firms use AWS, GCP, Azure as their infrastructure)
Data providers publicly signal their official Chainlink node, which only provides access to their data
"We are excited to announce integrated support for the @Chainlink Keepers Open Beta directly within the @OpenZeppelin Defender platform—the leading security operations suite for #Ethereum and EVM-based chains"
"In order for the contract to be serviced by the network, it needs to be funded with $LINK tokens which can be done directly inside of the @OpenZeppelin Defender console"
Adoption of #Chainlink services like Keepers -> Increase demand for $LINK tokens from users
1/ After yesterday's discussion with the author of the recent @Delphi_Digital oracle report, who attempted to provide justifications as to why the report had inaccurate information regarding #Chainlink, it appears the doubling down is simply continuing
2/ DONs are not standalone ledgers (like was claimed), but are explicitly anchored to a mainchain, that is a fact that is backed up by numerous statement in the 2.0 whitepaper
DONs use layer 2 syncing mechanisms, a mainchain is required for this to work
Unfortunately, the report is quite biased and contains many factually incorrect points about #Chainlink
🧵👇 Thread
2/ First, I think it's good that they disclosed they are financially invested in API3 and Pyth as disclaimers, but I don't think that forgives the inaccurate information presented in the report
The issues: 1. Data provider run nodes 2. LinkPool BSC node 3. Chainlink 2.0 staking
3/ 1. The report repeatedly frames Chainlink as just being a "third party" oracle solution that doesn't support "first party oracles"
This is factually incorrect
There are already over a dozen data provider run #Chainlink nodes live on mainnet today