Gravity, Reflect, Solana and Theorem are among the users in Chainlink’s latest integration list. Their applications range from moving tokens between networks and supplying prices to automating workflows and checking transaction policies.
Chainlink reported 19 integrations across five services and seven blockchains in its October 25 adoption update. The accompanying graphic covers September 28–October 25, 2026. The graphic names 15 users; some, such as Gravity, use more than one service.
The named users are Archax, Gravity, Overcall, HODL, LG CNS, Open Standard, OpenZeppelin, Pacific Meta, Reflect, Stellar, Solana, Stax, Tapir, Theorem and T-RIZE. Chainlink groups them into areas including real-world assets, blockchains, wallets and payments, AI services, DeFi, stablecoins, consulting and smart-contract security.
Transfers, pricing and transaction rules use different services
Chainlink described four users’ integrations in a separate October 23 announcement. Gravity is adopting CCIP for cross-chain WETH and USDC transfers and Data Streams for high-speed market data. Reflect uses Data Streams to obtain verifiable prices for PRIME and ReUSD.
| User | Service and stated use |
|---|---|
| Gravity | CCIP for WETH/USDC transfers; Data Streams for market data. |
| Reflect | Data Streams for verifiable PRIME and ReUSD pricing. |
| Solana | CRE to automate workflows across blockchains and existing systems. |
| Theorem | ACE to enforce compliance policies on exchange infrastructure. |
CCIP lets a smart contract on one network send a message to another. For token transfers, pools can lock or burn an asset on the source chain and release or mint its counterpart on the destination chain, depending on the token’s configuration. CCIP 2.0 waits for full source-chain finality before destination execution by default. Issuers can separately enable faster confirmation or additional verifiers.
Data Streams supplies applications with signed market reports. Developers can fetch a report and verify it onchain within the transaction that uses it. The reports carry price information; CCIP handles the movement of tokens between networks.
Solana support adds reads and event triggers
Chainlink added Solana reads and event triggers to CRE in its October 19 update. Workflows that could already write onchain can now also read Solana account and program state. A matching program event can start a workflow, with optional filters on specified event fields. Full support requires version 1.33.0 or later of the CRE command-line tool.
Chainlink Runtime Environment (CRE) lets developers combine tasks such as fetching data from an external API, reading blockchain data, performing calculations and writing a result onchain in one workflow. Nodes in decentralized oracle networks run workflows written in Go or TypeScript and verify their results through consensus.
Deployment to the oracle network requires approval. Developers can build and simulate CRE workflows locally. They must obtain Chainlink’s approval before deploying the workflows for live execution on an oracle network. Local simulations can still make real calls to APIs and networks.
The first-workflow section of Chainlink’s January 23, 2026 CRE tutorial starts at 4:23.
Theorem applies investor and transaction rules
Chainlink says Theorem uses ACE to apply compliance policies to its exchange infrastructure. The Automated Compliance Engine (ACE) can enforce identity checks, transfer limits and sanctions screening when a smart-contract transaction executes on a network compatible with the Ethereum Virtual Machine (EVM). A transaction that fails a policy reverts, and policies can change without redeploying the application’s main contract.
Chainlink currently offers ACE in private beta. Checks at transaction time require a contract integrated with ACE. A separate continuous-monitoring feature screens selected addresses periodically and can call existing token functions, such as a freeze, when risk changes. A new risk can be addressed only when the next screening run takes place.
Integration counts do not measure usage or revenue
Chainlink did not disclose transaction counts, transferred value, fee revenue or demand for LINK attributable to each integration. The post’s text also does not provide a complete list of the five services or seven chains.
“5 services and 7 different chains”
Chainlink’s September 28–October 25 adoption update
The post loads from X when you open it.
The official post published on October 25 includes a graphic showing the four-week period and the named users.
