linkmarketcapIndependent community analytics

Updates

Sources checked ·
NODE RELEASE · OCTOBER 5, 2026

Node v2.67.0 adds ERC-20 gas-token balance monitoring

Operators can now monitor their balances on chains that use an ERC-20 token for transaction fees. The release also adds PostgreSQL 18 support.

These are changes to node operations. Adoption by operators and any effect on service income remain unverified.

Sources & release details

Node v2.67.0 release ↗ · Published . Reviewed .

The released balance-monitor setting ↗ selects an ERC-20 token. The pinned EVM library ↗ reads that token’s balance instead of the native balance in its monitoring code ↗. This tracks funds available to pay blockchain transaction fees; it does not measure customer payments to Chainlink.

The node image adds PostgreSQL client 18 ↗. The normal server minimum remains 15 ↗, as in v2.66.0; this release does not introduce another increase in that minimum.

The bridge observation cache ↗ now retains observations for 90 seconds, up from 60. That is a node-side cache lifetime, not a network-wide oracle freshness limit. It is separate from the CRE restart cache below, whose merge is outside this release ↗.

Sources observed . Reviewed release commit: df15279b3ab71f1e86f5deed72647949e69d3d7f. No live operator configuration or performance benchmark was verified. Earlier reviews retain their own dates.

Integration announcements

Swift ledger connectivity, Coinbase tokenized equities, Wyoming Proof of Reserve and Project Pangea. Announcements and first-party progress reports are separate from verified onchain activity.

View announcements and evidence →
CRE changes awaiting release · 1
CRE · MERGED CODE

Awaiting release

Merged · awaiting releaseReviewed

CRE restart cache merges; still outside v2.67.0

Merged on October 5, the change lets nodes reuse saved workflow trigger subscriptions when restarting. Operators must enable the setting; it is off by default.

The merge is outside v2.67.0. Startup gains and operator rollout remain unmeasured.

Sources & details

Pull request #23774 ↗ · Reviewed code ↗

CRE.CachedTriggerSubscriptionsEnabled gates both saving and reusing subscriptions. Missing or invalid cached data falls back to workflow setup, and cached reuse still checks the subscription-count limit. New cache writes run asynchronously with a ten-second timeout. Separately, the merged code treats a workflow returning zero subscriptions as a permanent initialization error, even with caching disabled. The merge is not an ancestor of the v2.67.0 release; the released configuration and engine also lack the cache setting and reuse path.

A containing release, operator enablement and measured startup time are the remaining checks.

Observed . Reviewed revision: b60fc4218ae7daa6b2638b293e3ba85c95fec01c.

Earlier code reviews & release history
NODE RELEASE · SEPTEMBER 28, 2026

Node v2.66.0 raises the database minimum and removes Cosmos support

Operators on PostgreSQL 12–14 need a database upgrade before adopting this release. The previously tracked Cosmos removal is now included in a published node version.

PostgreSQL 15 minimumStandard startup check
Deprecated Cosmos supportRemoved from core node
CRE shared-library cleanupNow included in the release

The shared-library removal tracked last week is also included. Operator rollout remains unverified. The Cosmos removal applies to this node software; a service-wide shutdown is not established.

Sources & release details

Node v2.66.0 release ↗ · Published . Reviewed .

Both the database change ↗ and Cosmos removal ↗ are ancestors of release commit 16456b34a8db32e0acd36a2468aac8dc7a5c8144. The released version check ↗ sets a minimum of 15 for 2026 and 2027; the released plugin list ↗ omits Cosmos.

The released dependency file ↗ pins v0.11.2-0.20260921174556-538f4bf0cb6f, which resolves to the shared-library cleanup merge ↗. Unlike v2.65.0, this release includes that removal. Dependency inclusion reviewed .

The database check can be bypassed with an unsupported environment override and skips version values it cannot read reliably. Neither exception establishes supported compatibility. No operator rollout, migration completion or effect on fees is measured here. Sources observed . Earlier release reviews retain their original dates below.

RELEASE · SEPTEMBER 21, 2026

CRE cleanup reaches node v2.65.0

The release removes older workflow settings and legacy web API and compute-action connector methods. Operators upgrading to this version inherit those removals. Workflow artifact fetching remains.

Core-node cleanupIncluded in v2.65.0
Shared runtime cleanupMerged · outside this release
Operator rolloutUnverified

The separate shared-library removal merged September 21. This release still pins an earlier library version; application migration and fee effects have not been measured.

Sources & release details

Node v2.65.0 ↗ · Release source comparison ↗

GitHub ancestry includes the workflow cleanup commit ↗ and connector cleanup commit ↗. The source comparison removes the legacy connector method cases and keeps workflow_syncer. The affected workflow files were inspected at release commit 1568d3dfa8f74cbfbcd102cdac2adeeb429829c3.

Shared-library PR #2382 ↗ merged at its previously reviewed code revision. The node dependency file ↗ pins v0.11.2-0.20260914191328-10cc2b41997e; that commit precedes the removal ↗. Source inclusion is separate from deployment across operators.

The Cosmos removal merge is outside this release ↗. This ancestry check does not exhaustively exclude equivalent changes through other commits. Sources observed 2026-09-21; release reviewed 2026-09-21. This review does not advance the older code reviews below.

Closed proposals

Closed without mergeReviewed

CRE event coordinator proposal closed without merging

The proposed separation of event handling from workflow execution was closed on September 25 without a merge.

No release or production rollout was established for this proposal.

Sources & details

Pull request #23780 ↗ · Reviewed code ↗

The PR closed at its previously reviewed revision. Its draft coordinator still lacked wiring into the production execution path. The recorded closure gives no reason or confirmed replacement.

The earlier draft remains available as a dated code review.

Observed . Reviewed revision: 0a025aea520a2e12d602f5534df0852f09aa9f82.

RELEASE · SEPTEMBER 14, 2026 · REVIEWED SEP 15, 2026

Automation retirement reaches node v2.64.0

Node v2.64.0 ↗ · Published release

Node v2.64.0 removes support for the older Automation service, following Chainlink’s announced move to CRE.

How many applications have migrated—and kept paying for execution—remains unknown.

Sources & release details

Removal PR #23605 ↗ · Automation sunset notice ↗ · Migration guide ↗

The official notice gives June 30 for v1.x and July 31, 2026 for v2.1 mainnet. Existing jobs using the removed ocr2automation plugin fail validation in this version. This establishes the software change and documented migration direction, not completion by every application or node operator.

Other release notes include experimental pipeline tasks and durable organization-resolution caching. No performance or revenue effect has been measured here.

GITHUB · REVIEWED SEP 15, 2026

CRE workflow cleanup merges

Pull request #23727 ↗ · Merged 2026-09-14

CRE coordinates workflows that connect offchain data and onchain actions, running them across Chainlink oracle networks.

The merged change removes older workflow-engine options. It is consistent with simplifying the execution layer; no improvement in speed, adoption or fees has been measured.

Release check 2026-09-21: this cleanup is included in v2.65.0. The earlier v2.64.0 comparison below remains the historical record.

Related connector cleanup #23728 ↗ merged September 15. Deployment has not been verified.

Sources & technical details

The related connector patch removes legacy web API and compute-action methods while retaining workflow artifact fetching. Its merge commit is outside v2.64.0 ↗. Reviewed 2026-09-15.

CRE documentation ↗ · Linked chainlink-common PR #2382 ↗

Dependency rechecked 2026-09-21: PR #2382 merged 2026-09-21. Its revised patch removes legacy host interfaces; v2.65.0 still pins an earlier dependency. Reviewed dependency patch ↗ · 22538eb48389bc13b6ce8a3a70ab669e48723041.

The original PR prepares for removal of the legacy DAG WASM host. The core-node changes are included in v2.65.0, while the shared-library removal remains outside its pinned dependency. Runtime consolidation is our interpretation. The patch does not establish faster execution, increased adoption or fee income.

Code observation: Sep 15, 2026. Head: a04e49eb1d6070e9d6c147df3fd9556d050908e1. The merge commit is eddf5109401b34c0d3bb62c61ae5bc7a705af49a. GitHub ancestry comparison ↗ shows this merge is not included in v2.64.0; equivalent changes by another route were not exhaustively checked. A reversal or different dependency plan requires another review. CRE background was checked separately on 2026-09-14.

MERGED CHANGE · REVIEWED 2026-09-16

Cosmos support removal merges into the core node

Pull request #23734 ↗ · Merged 2026-09-16 · Deployment unverified

The merged patch removes the Cosmos plugin from the node image, along with Cosmos configuration, key management and transaction controls. Its release note describes that support as deprecated.

Operators using those interfaces would need to account for the removal when adopting a release that includes it. Which operators have done so remains unknown.

Sources & scope

Reviewed head: b29bd60801fae94196ef861f920580332f6179a5. Selected patches remove the plugin entry, relayer construction, command-line and HTTP routes, and the Cosmos key branch in the CCIP delegate. This change is specific to core-node software; it does not establish that every Cosmos-related Chainlink service has ended. The earlier check placed the merge outside v2.65.0 ↗. The October 1 review confirms it is included in v2.66.0 ↗. The original code review date is unchanged. No live deployment is claimed. Merge commit: fa897c3d55f584de6ece6255c061b8ef6904d0d5.

CORE NODE · RELEASES CHECKED 2026-10-05

Published versions

v2.67.0Release notes ↗v2.66.0Release notes ↗v2.65.0Release notes ↗v2.64.0Release notes ↗v2.63.0Release notes ↗v2.62.0Release notes ↗
Release coverage

These are captured core-node releases. v2.67.0 adds ERC-20 gas-token balance monitoring and PostgreSQL 18 support. v2.66.0 includes the tracked Cosmos removal and database minimum change; v2.65.0 included the tracked core CRE cleanup commits. v2.64.0 removed the older Automation plugin as a separate change; deployment of the release across operators is not verified here.

GITHUB · REVIEWED SEP 15, 2026

Code activity

Browse 12 GitHub changes
Pull requestUpdated / merged (UTC)Status at review
#23742 · (feat): HTTP outbound concurrency limiters2026-09-15Open
#23728 · CRE-6535: remove unused web-api-trigger/target gateway handler code2026-09-15Merged
#19790 · chore: update locally replaced module paths in go.mod files2026-09-15Open
#23684 · dependabump2026-09-15Open
#22889 · feat(oidc): CLI login via device authorization grant + PKCE2026-09-15Open
#23734 · remove cosmos support2026-09-16Merged
#23729 · CRE-6402: Metrics for duplicate capabilities2026-09-14Open
#23737 · fix(pg): version checks and bumps2026-09-14Open
#23741 · Classify vault errors as user errors2026-09-14Open
#23499 · Lint Roller 7: core/services2026-09-14Open
#23458 · CRE Gate and Limit Handling Improvements2026-09-14Open
#23504 · Lint Roller 12: deployment (keystone), devenv2026-09-14Open
Sources & limitations

Twelve PRs from the original open-list snapshot, with #23728’s merge verified separately on September 15 and #23734’s on September 16. The date column shows merge times for those two PRs and captured update times for other rows. Updates can be comments or housekeeping. Other repositories and private work are outside this sample; counts do not measure developer productivity or customer demand.

Sources & coverage

Source checks and analysis reviews have separate dates. Individual observations may predate a successful check.

Analysis reviewed: . Individual stories and charts carry their own dates. Transaction samples may be incomplete, and address names may be unverified. Code changes do not confirm that a service is live. Full methodology →