Table of Contents
Beam, the data-movement network operating on Bittensor subnet 105, has brought Chainlink-attested transfer receipts to Base mainnet, giving smart contracts an onchain record of data transfers completed outside the blockchain. Beam said its first receipt covered a 100 GB transfer.
The integration uses Chainlink Runtime Environment (CRE), which runs workflows across a decentralized oracle network, or DON, to read Beam's transfer reports and record their metadata onchain. Applications can then check delivery status without putting the files themselves on a blockchain.
The live Base deployment records Beam's own transfers. Beam plans to add the next part of the process: a smart-contract request that starts a Beam Studio transfer and receives a receipt back onchain for the application to act on. Other organizations cannot yet have their transfers recorded through Beam's Base deployment.
What Is Running on Base
Beam's transfer-receipts workflow uses a read-only key for its organization to retrieve transfer information and write receipts. It does not initiate transfers. The CRE integration documentation identifies Base mainnet, chain ID 8453, as the live deployment and limits receipt requests to accounts Beam authorizes.
The receiving contract, BeamTransferReceipts, has verified source code on BaseScan. It accepts reports through a designated Chainlink forwarder and checks the expected workflow owner and workflow ID, restricting which workflow can submit records.
Chainlink listed Beam among its new integrations on November 13, alongside Aave and LlamaRisk's work on dynamic borrowing caps and Corda's use of Data Streams. Chainlink described Beam's integration as using CRE to deliver verifiable onchain receipts for data transfers.

A standard Beam receipt records the transfer's status, total size, bytes transferred, completion time, plan fingerprint, and coordinate checksum, along with its request ID and attestation level. Applications retrieve it by passing the transfer ID to getReceipt.
The workflow records terminal outcomes, including completed, failed, and canceled transfers, rather than treating every recorded receipt as a successful delivery. Once recorded, a receipt is not overwritten. For applications that depend on a successful handoff, checking the status is part of using the record.