Chainlink CRE Connect
Chainlink CRE Connect (CREC) is a managed API and Go SDK for applications that need verified on-chain observations and gas-less on-chain execution. Your application calls one API; Chainlink runs the oracle network and on-chain execution infrastructure behind it.
CRE Connect uses the Chainlink Runtime Environment and Chainlink Decentralized Oracle Networks (DONs), which are groups of independent Chainlink nodes that observe chains, produce signed reports, and submit transactions. CRE Connect packages those capabilities into one developer interface.
Use CRE Connect when your application needs to:
- Watch on-chain events: subscribe to contract logs and verify that a Chainlink DON observed them.
- Execute gas-less operations: submit an Operation, which is an EIP-712-signed batch of EVM transactions that a Smart Account, your on-chain execution account, runs atomically.
- Run one-shot chain queries: request a read-only EVM call and receive a DON-backed result.
You sign operations with keys you already use: local ECDSA, AWS KMS, HashiCorp Vault, Fireblocks, Privy, or a custom signer. CRE Connect delivers verifiable events and results, and the SDK gives you helpers to verify them locally before acting on them.
What you can build
Capability | What it gives you | Where to start |
|---|---|---|
| Verifiable events | DON-signed on-chain events delivered through one channel event stream. | Quickstart: Watch Events |
| Gas-less operations | One EIP-712-signed payload becomes one or more EVM transactions executed atomically by your Smart Account. | Quickstart: Send an Operation |
| Chain queries | One-shot, DON-backed reads for EVM eth_call requests against a selected block. | Execute a Chain Query |
| Protocol extensions | Pre-packaged typed builders and watcher provisioning for supported partner protocols. The first available extension is DTA. | Extensions |
Core model
Most integrations use the same small set of resources:
| Resource | What it does | Start here |
|---|---|---|
| Channel | Scopes watchers, wallets, operations, queries, and the ordered event stream for one application or environment. | Channels |
| Watcher | Monitors a contract on a supported chain and emits watcher.event records when matching logs appear. | Watchers |
| Event | Carries watcher data, lifecycle updates, or query results through one poll/search API. Verifiable events include OCR proofs. | Verifiable Events |
| Wallet / Smart Account | Represents the on-chain account that executes operations and the signer set allowed to authorize them. | Smart Accounts |
| Operation | Packages one or more EVM transactions into an atomic, EIP-712-authorized write. | Operations |
| Query | Requests a one-shot, read-only EVM call and returns a signed result. | Chain Queries |
Pick your path
Choose the entry point that matches what you're trying to do right now.
I'm new: get me to a working integration
Read these in order.
- Prerequisites: request access, install Go, gather your API key, pick a signer.
- SDK Installation:
go getthe core SDK and optionally the DTA extension. - Authentication: initialize the client and run a
ListNetworkssmoke test. - Quickstart: Watch On-Chain Events: your first verifiable event.
- Quickstart: Send Your First Operation: your first gas-less write.
I want to understand the model
Start with the Architecture overview, then follow the path that matches your integration:
- For event monitoring: Channels, Watchers, Verifiable Events, and Confidence Levels.
- For on-chain execution: Smart Accounts, Operations, EIP-712 Signing, Draft Operations, and Multi-Event Finality.
- For on-chain reads: Chain Queries.
I'm integrating now: show me the code
Jump straight to the relevant guide:
- Channels: Create and manage channels
- Watchers: Predefined service · Custom ABI · Lifecycle
- Events: Poll and search · Verify signatures · Decode data
- Operations: Build and sign · Draft operations · Submit and track · Batch · Signing transparency
- Queries: Execute a query
- Wallets: Create and manage · Manage signers
- Signers: Local · AWS KMS · HashiCorp Vault · Fireblocks · Privy · Custom
I just need to look up a fact
- REST API Reference: narrative companion to the interactive Swagger explorer.
- Go SDK Reference: every public sub-package with links to
pkg.go.dev. - SDK Configuration Options: every functional option on
crec.NewClient. - Lifecycles: every status enum and state transition.
- Event Types and Payloads: the five
Event_Payloadshapes. - Error Handling: sentinel errors, REST envelope, retry policy.
- Service Limits: hard limits and quotas.
- Supported Networks: discoverable at runtime via
ListNetworks.
Where to go next?
- Getting Started: follow the recommended onboarding sequence.
- Architecture: understand how the SDK, REST API, DON workflows, and Smart Accounts fit together.
- REST API Reference · Go SDK Reference: look up endpoint and SDK details.
- Release Notes: see current versions and changes.