On September 2, 2020 we were added to the Chainlink ecosystem as a Node Operator and a Channel Partner — a status that is still live on the official registry at chainlinkecosystem.com/ecosystem/01node. Five years later, the decisions we made in those early weeks have shaped every layer of how we build infrastructure.
Why Chainlink is different
Running a blockchain validator is a consensus game. The protocol tells you what to sign, your job is not to sign twice. Running a Chainlink oracle node is a data integrity game. The protocol does not tell you what price to report — you have to fetch it, reconcile it with other sources, and submit it within a strict window, knowing that billions of dollars of DeFi collateral will move on the result.
This difference has a single operational consequence: latency and availability are the product. A Chainlink node that is 200ms slow or that misses a heartbeat is worse than one that goes offline entirely, because the oracle reports can desynchronise from the rest of the decentralized oracle network (DON).
What we had to build
- Dedicated routes. Public clouds share ingress paths, DNS resolvers and backbone links. For a Chainlink node, we cannot tolerate a 300ms jitter event coming from a neighbour’s traffic spike. This is why we operate AS211396 with direct peering at 20 Gbps+ to tier-1 carriers. - Sub-second monitoring. Standard Prometheus scrapes on a 15-second interval are far too coarse for oracle operations. We run bespoke, sub-second probes that alert on the shape of a single oracle report cycle. - External API diversity. Each data source must be cross-checked against at least two independent providers. Relying on a single API vendor is a latent single point of failure, even if that vendor is reliable 99.99% of the time. - Isolated key material. The oracle node’s signing key signs every on-chain report. We treat this key with the same discipline as a validator’s consensus key: HSM-backed where possible, segregated from the business network, with ceremony-controlled access.
The Channel Partner role
Beyond the technical role of operating a node, the Channel Partner status made us part of Chainlink Labs’ programme of accelerators, launchpads, incubators, and infrastructure providers. This has given us direct access to the institutional wave — Swift, Euroclear, Mastercard, Fidelity International, UBS, and ANZ have all adopted Chainlink standards for tokenised assets, onchain NAV, and cross-chain settlement.
What this means for an operator like us: the bar for Chainlink node performance is being set by the needs of regulated capital markets, not DeFi retail. We have been operating at that bar for five years, which matters when a counterparty starts a vendor review.
What changed in 2024 and 2025
The two biggest shifts we have seen are the Cross-Chain Interoperability Protocol (CCIP) going from a DeFi-focused rails into the default institutional cross-chain settlement layer, and Chainlink’s standards being picked up for tokenised fund NAV. When a €2.3T asset manager launches a UCITS-wrapped tokenised fund with onchain NAV delivered by Chainlink, the oracle layer goes from being a convenience into being a settlement primitive.
What it takes to still be here in year five
- Zero slashing-equivalent events. The oracle-side equivalent of slashing is a submitted report that diverges materially from the DON consensus. We have not caused such an event. - Continuity through ecosystem cycles. We were running nodes through the 2021 euphoria, the 2022 Terra/FTX collapse, the 2023 bear, and the 2024–2026 institutional wave. The node kept going. - Operator discipline over operator growth. We did not scale the number of nodes we operate faster than we could staff the operations. The cap is hand-set, not budget-set.
Where we go from here
Our current priorities on the Chainlink side are (1) deeper CCIP integration for cross-chain settlement flows used by institutional clients, (2) continued publication of our node performance and any incidents in the open, and (3) coordinated rollout of the Data Streams product for low-latency price feeds.
For counterparties evaluating us as an oracle operator, the simplest way to verify our five-year track record is the ecosystem registry itself: chainlinkecosystem.com/ecosystem/01node. Everything else we claim on this site is backed by an equally direct source — see /operator-credentials for the full list.