First identify which balance your application needs
Chainlink’s VRF v2.5 subscription model distinguishes the owner wallet, subscription account and approved consumer contracts. The subscription can hold LINK and native-token balances. Do not read a wallet token holding as proof that a particular subscription already has the funds or consumer configuration it needs.
Before exchanging USDT, ask the person responsible for the application to identify the network, subscription and intended billing asset. VRF v2.5 supports both LINK and native-token billing; do not assume every request necessarily requires buying LINK. This page explains how to separate the records when LINK is the selected plan, not how to choose the application’s funding policy.
Four records that should not share one “done” label
| Record | Question it answers | What remains separate |
|---|---|---|
| USDT exchange request | Which purchase is being funded? | The application subscription identity |
| LINK wallet receipt | Did the bought token reach the intended account? | Any later subscription funding action |
| Subscription funding record | Did the intended subscription receive the chosen funds? | Whether the consumer and request are configured correctly |
| Application request result | Did this specific VRF request complete? | The outcome of an unrelated token purchase |
Prepare a handover between the buyer and application owner
- Agree on the receiving wallet and chain
The buyer needs a verified receiving instruction, not an unexplained subscription number pasted into an exchange address field. Resolve who controls the intended wallet and which network the planned workflow uses before paying USDT. Do not assume a deployment on one chain can spend a token holding on another.
- Verify the purchased LINK separately
After payout, inspect the intended account and token details. Retain the exchange reference and payout reference for the purchase. If the token has not arrived, investigate that event rather than changing application settings to hide the discrepancy.
- Keep subsequent application actions outside the exchange task
The application owner should follow the current official subscription workflow and verify its result independently. Do not send funds directly to a coordinator or other contract merely because its address appears in documentation. The exchange purchase does not authorize a separate transaction or prove that it is the right method.
A purchased amount is not a universal request budget
Chainlink’s billing documentation describes the costs of VRF requests and distinguishes the required subscription balance from the final consumed cost. Do not turn a worked example from a guide into a permanent amount of LINK to purchase. Review the actual network, application settings and current subscription requirements for the workflow being used.
For a shared task list, record three separate observations: the exchange purchase result, the later subscription funding result and the application check. If only the first is complete, say that clearly. This prevents an operator from buying repeatedly because the application still shows a different balance. Assign the application work to its responsible owner and record its actual outcome separately from the token payout.
Questions about buying LINK for VRF
- Does receiving LINK automatically fund my VRF subscription?
- Treat the wallet receipt and the subscription funding as distinct results. Verify the appropriate account record for each task instead of using the purchase as proof of application readiness.
- Is LINK the only billing option in VRF v2.5?
- The documentation describes LINK and native-token billing. Confirm the plan for the actual application rather than buying an asset solely because a tutorial mentions it.
- Can a subscription number replace the exchange payout address?
- It identifies a different object. Obtain a verified receiving instruction for the exchange payout and leave application funding to the appropriate separate workflow.
Chainlink application documentation
Reviewed: