Skip to content

Bump chainlink-common to daa34bb8 - #118

Merged
DylanTinianov merged 5 commits into
mainfrom
CRE-6919-enclave-execution-duration
Oct 15, 2026
Merged

DylanTinianov merged 5 commits into
mainfrom
CRE-6919-enclave-execution-duration

Conversation

@DylanTinianov

@DylanTinianov DylanTinianov commented Oct 13, 2026 •

Copy link
Copy Markdown
Collaborator

What

Dependency bump only: chainlink-common → daa34bb8 (main, includes #2464 and #2462) in every module that pins it, plus chainlink-protos/cre/go → e622e8b8 / 5868490c (#473 merged).

Why

With that common, the WASM host the enclave runs sets ExecutionResult.compute_duration_ms itself. It travels back to the node inside SdkExecutionResult, so the node meters confidential compute from the enclave-measured run (CRE-6779 / chainlink#23858) with no enclave-side timer and no extra response field.

Notes

  • Modules bumped: capabilities/framework, enclave-client, enclave/config-tracker, enclave/nitro/host, enclave/apps/confidential-workflows (+ capability), enclave/apps/confidential-http/capability, tests.
  • enclave-client, config-tracker and nitro/host move to go 1.27.1 (required by common). Their Dockerfiles build on golang:1.26-alpine, which defaults to GOTOOLCHAIN=local, so they now set GOTOOLCHAIN=auto like enclave/nitro/Dockerfile already does.
  • tests/ also bumps the chainlink monorepo pins bfbfcc34 → e43a194d (develop): common removed EncodeExecutionID after the old pin, so the old chainlink no longer compiles against it.
  • wasm_limiters_test.go expects defaults.UserMetricLabelsPerMetric.DefaultValue instead of the literal 20, which the newer common changed.

Testing

make gomodtidy, go build ./... in all eight bumped modules, and go test ./... in the enclave app, capability, framework, client, config-tracker and host modules (GOTOOLCHAIN=go1.27.1).

🤖 Generated with Claude Code

@DylanTinianov
DylanTinianov requested a review from a team as a code owner October 13, 2026 21:45
@DylanTinianov
DylanTinianov force-pushed the CRE-6919-enclave-execution-duration branch 2 times, most recently from bd0497d to 97bc76b Compare October 13, 2026 21:50
… (CRE-6919)

The WASM host now sets ExecutionResult.compute_duration_ms, which travels
back to the node inside SdkExecutionResult; no enclave-side timer needed.

Co-Authored-By: Claude Fable 5.1 <[email protected]>
@DylanTinianov
DylanTinianov force-pushed the CRE-6919-enclave-execution-duration branch from 97bc76b to 8e4eb2d Compare October 14, 2026 14:38
@DylanTinianov DylanTinianov changed the title confidential-workflows: report the WASM execution duration confidential-workflows: bump chainlink-common for compute_duration_ms Oct 14, 2026
Co-Authored-By: Claude Fable 5.1 <[email protected]>
@DylanTinianov
DylanTinianov enabled auto-merge (squash) October 14, 2026 15:37
patrickhuie19
patrickhuie19 previously approved these changes Oct 14, 2026
Comment thread enclave/apps/confidential-workflows/go.mod Outdated
@DylanTinianov DylanTinianov changed the title confidential-workflows: bump chainlink-common for compute_duration_ms Bump chainlink-common to daa34bb8 across all modules Oct 14, 2026
Also bumps the chainlink monorepo pins in tests/ to develop e43a194d, since
common removed EncodeExecutionID after the old pin, and sets GOTOOLCHAIN=auto
in the config-tracker and host Dockerfiles for the new go 1.27.1 directive.

Co-Authored-By: Claude Fable 5.1 <[email protected]>
@DylanTinianov DylanTinianov changed the title Bump chainlink-common to daa34bb8 across all modules Bump chainlink-common to daa34bb8 Oct 15, 2026
@DylanTinianov DylanTinianov self-assigned this Oct 15, 2026
@DylanTinianov
DylanTinianov merged commit 4693e1d into main Oct 15, 2026
61 checks passed
@DylanTinianov
DylanTinianov deleted the CRE-6919-enclave-execution-duration branch October 15, 2026 14:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants