Buying LINK and using CRE are two separate things. The entry requirement for CRE (Chainlink Runtime Environment) is not "holding LINK." It is getting deployment permission approved. Even if you have a large amount of LINK in your OKX account, without Early Access approval, you cannot deploy workflows to production.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
What stage is CRE currently in
CRE is currently in the Early Access stage. This means you can register an account for free, install the CLI, write workflows in Go or TypeScript, and run them locally in simulation. None of these steps require approval.
But once you want to deploy a workflow to a Chainlink DON (decentralized oracle network) for production use, you need to submit a deployment permission request and wait for the Chainlink team to approve it.
How to apply for deployment permission
The entry point for applying for deployment permission is in the CRE CLI. You need to complete the following preparation steps first:
Create a CRE account: Register at app.chain.link/cre/discover
Install the CRE CLI: Install the command-line tool on your local machine
Log in: Run cre login to complete authentication
Apply for deployment permission: Run cre account access. The CLI will prompt you to submit an application and briefly describe your use case.
After submission, the Chainlink team will follow up by email. Once approved, cre whoami will show Deploy Access: Enabled.
LINK does not play any role in this process. Deployment permission approval is based on your use case, not on how much LINK you hold.
Where you actually need to spend money during deployment
When deploying workflows to a DON, there are two registry paths with different cost structures:
Private Registry is a Chainlink-hosted offchain registry. Lifecycle operations such as deploy, activate, pause, delete, and update are authorized by your CRE login session. It does not require a wallet, does not require gas, and does not require an Ethereum mainnet RPC. The official documentation clearly states: "no transaction hash, no gas cost."
Onchain Registry records workflows on the Workflow Registry contract on Ethereum mainnet. This path requires: a linked wallet key, ETH in the wallet to pay for gas, and an Ethereum mainnet RPC configured in project.yaml.
The official recommendation is: Private Registry is suitable for testing and team workflow management. Onchain Registry is suitable for production scenarios that require multisig ownership or onchain verifiable records.
Therefore, the direct onchain cost of CRE depends on which registry path you choose. The private path currently has no gas fees. The onchain path only has gas for one registration transaction, and the amount depends on the gas price on Ethereum mainnet at that time.
Where OKX fits in this process
OKX is not directly integrated with the CRE deployment process. You buy LINK on the OKX spot market, but LINK itself is not a "pass" or "fuel" for CRE.
The actual uses of LINK in the Chainlink ecosystem are paying for oracle services and serving as collateral to strengthen network security. Chainlink is advancing Payment Abstraction, which will allow enterprises to pay using their preferred payment method, including fiat or stablecoins, and then the system automatically converts it to LINK on a DEX. This mechanism is still under development and is not a step you must go through when using CRE right now.
If your goal is to build workflows with CRE, the more practical path is: go directly to the Chainlink website, register an account, install the CLI, write code, and run simulations. You do not need to buy LINK on OKX first. LINK only becomes practically useful when your workflow needs to call paid onchain services, or when you want to participate in staking.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
