Chainlink said on November 15 that it had recorded 10 recent integrations spanning five services and seven blockchain networks, with Aave, ApeCoin, Apex Group, b1m.ai, Corda, LlamaRisk, NumPay, OlympusDAO, Ripe DAO and tRex among the users named. The update spans DeFi risk controls, cross-chain transfers, payments, institutional assets and compliance, although the underlying integrations are at different stages of deployment.
The tally is broader than the November 13 Chainlink post, which covered Aave and LlamaRisk, b1m.ai and Corda specifically. Those announcements involve the Chainlink Runtime Environment, or CRE, and Data Streams, while other recent integrations use CCIP, Data Feeds and the Automated Compliance Engine. The November 13 post does not itself support the 10-integration figure.
Chainlink Adoption Update 🔗
Recently, there were 10 integrations of the Chainlink standard integrations across 5 services and 7 chains.
Users include @aave, @apecoin, @ApexGlobalGroup, @b1m_ai, @Cordaxyz, @LlamaRisk, @numpay, @OlympusDAO, @Ripe_dao, and @trex_network.
LINK… pic.twitter.com/rrFv69HVrd
— Chainlink (@chainlink) November 15, 2026
Aave Proposal Differs From Live Deployments
Aave and LlamaRisk provide the clearest example of why deployment status matters. LlamaRisk submitted an Aave Request for Comment on November 11 for LlamaGuard Caps, a proposed rate-limiting system that would dynamically adjust borrow-cap headroom. Raises would be computed through Chainlink CRE and bounded onchain, but the proposal still requires community feedback, a Snapshot vote and an AIP if governance supports it. The dynamic borrow-cap system is not yet live.
Other integrations are further along. Corda said Chainlink will publish pricing for its institutional assets on Solana, giving applications a common onchain reference, while b1m.ai is using CRE for verifiable onchain receipts tied to data transfers. NumPay separately said it integrated Chainlink Data Feeds for currency conversions in its cross-border payment application on Base and Elysium. These deployments extend Chainlink beyond conventional crypto price feeds into operational data and verification workflows, an area also relevant to tokenized assets and onchain lending markets.
Cross-chain migrations account for another part of the update. OlympusDAO said on November 5 that OHM bridging had fully migrated from LayerZero to CCIP across all seven chains supporting OHM following approval of OIP-198. ApeChain, by contrast, announced that it is deprecating its legacy cross-chain setup and migrating APE, USDC and other assets to CCIP, without specifying a completion date. Apex Group, tRex and the ERC-3643 Association also announced a Chainlink-powered framework for onchain bonds using CCIP, ACE and Data Streams, extending the broader push toward compliance and lifecycle infrastructure for tokenized assets. The cross-chain items therefore sit at different implementation stages.
Institutional Work Extends Beyond the Integration Tally
Chainlink’s broader institutional work also includes a separate CRE-based connectivity layer for Swift’s blockchain ledger. Chainlink announced in September that the system is intended to connect banks’ existing systems and signing infrastructure to the ledger while allowing institutions to retain control of transaction-authorizing keys. Swift later said most of its 17 first-mover banks had used the ledger for 24/7 real-time payments involving tokenized value. The 17-bank Swift figure should not be treated as 17 confirmed Chainlink integrations, because Swift’s ledger participation and adoption of Chainlink’s connection layer are separate claims.
The November tally therefore documents a widening technical footprint for Chainlink services, but it is not a single measure of production adoption. Some entries are completed migrations, others are active data integrations, and at least one major item, Aave’s dynamic borrow caps, remains in governance. Chainlink did not attach aggregate transaction volume, users or economic value to the 10-integration update. The evidence supports broader integration activity, not a quantified measure of production adoption.
