Skip to content

docs(active-evm): add README and task-origin signing guide - #776

Open
0xth4nh wants to merge 1 commit into
mainfrom
mux/active-evm-docs
Open

docs(active-evm): add README and task-origin signing guide#776
0xth4nh wants to merge 1 commit into
mainfrom
mux/active-evm-docs

Conversation

@0xth4nh

@0xth4nh 0xth4nh commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

What changed?

Adds generic documentation for the shared active/evm model:

  • active/evm/README.md: shared-project layout, how tasks run against the shared Foundry setup, pointer to script/common.
  • active/evm/TASK_ORIGIN.md: task-origin signing flow (sign-as-task-creator / -base-facilitator / -sc-facilitator), including the skipTaskOriginValidation opt-out.

Both written generically (placeholder <YYYY-MM-DD-task-name> / <network>, no task-specific references). Stacked on #775 (CI).

Why?

Documents the new structure so contributors can add tasks and sign without reverse-engineering the Makefiles.

How to test?

Docs only — no build impact. Review renders on the PR; verify layout matches the actual active/evm tree and the make targets referenced exist in the root Makefile (sign-as-*, gen-validation-*).

@0xth4nh
0xth4nh force-pushed the mux/ci-validate-common branch from ce69c3a to 5367a22 Compare July 29, 2026 22:16
@0xth4nh
0xth4nh force-pushed the mux/active-evm-docs branch from 3cddd0b to ff4f9b4 Compare July 29, 2026 22:17
@0xth4nh
0xth4nh force-pushed the mux/ci-validate-common branch from 5367a22 to 035093b Compare July 29, 2026 22:19
@0xth4nh
0xth4nh force-pushed the mux/active-evm-docs branch from ff4f9b4 to 92134fa Compare July 29, 2026 22:20
Base automatically changed from mux/ci-validate-common to main July 29, 2026 22:55
@cb-heimdall

cb-heimdall commented Jul 29, 2026

Copy link
Copy Markdown
Collaborator

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/2
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 2
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 2
2
1 if commit is unverified 0
Sum 2

@0xth4nh
0xth4nh force-pushed the mux/active-evm-docs branch from 92134fa to 632ea21 Compare July 29, 2026 22:59
jackchuma
jackchuma previously approved these changes Jul 29, 2026
@0xth4nh
0xth4nh force-pushed the mux/active-evm-docs branch from 632ea21 to d687b3c Compare July 29, 2026 23:05
@cb-heimdall
cb-heimdall dismissed jackchuma’s stale review July 29, 2026 23:05

Approved review 4813619797 from jackchuma is now dismissed due to new commit. Re-request for approval.

Documents the shared active/evm layout (script/common + per-task config),
the shared-project deps invocation, and active/evm task-origin signature
handling in the root README, alongside the existing legacy-task docs. Also
updates the CI section to describe the validate-common-scripts workflow.

No separate active/evm README/TASK_ORIGIN files: the root README is the
single source of truth for structure and signing, matching how tasks (which
carry only a per-task README + FACILITATOR) are documented.

Generated with Claude Code

Co-Authored-By: Claude <noreply@anthropic.com>
@0xth4nh
0xth4nh force-pushed the mux/active-evm-docs branch from d687b3c to b6be58b Compare July 29, 2026 23:12
Comment thread README.md

All three targets depend on `deps-signer-tool`, which checks out and installs the [task-signing-tool](https://github.com/base/task-signing-tool) automatically.

For `active/evm` tasks, the task Makefile overrides `TASK_ORIGIN_DIR` and `SIGNATURE_DIR` so signatures are written under `active/evm/tasks/<task-id>/config/<network>/signatures/`. The signer tool excludes that nested `signatures/` directory from the task-origin tarball, so generating signatures does not change the signed payload. A task may opt out of task-origin validation entirely by setting `skipTaskOriginValidation: true` at the root of each validation file (e.g. non-production networks such as zeronet).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The pinned signer tool expects task-origin bundles at tasks/<task-id>/signatures/<network>/ and recursively includes everything under config/<network>, so this nested path is neither excluded nor verifiable; please document and use the external signature path.

Comment thread README.md
│ └── <category>/ # bridge, funding, gas, ownership, safe, superchain, verifier-update
└── tasks/
└── <YYYY-MM-DD-task-name>/
├── Makefile # selects the task/network, wires a script/common script

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The layout puts the Makefile under each task, but commands run from active/evm and stacked PR #755 adds active/evm/Makefile; please align the documented location and invocation with the intended implementation.

Comment thread README.md
## Directory structure

Each task will have a directory structure similar to the following:
Active EVM tasks live under `active/evm/`, which is a single shared Foundry

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR description says this documentation is added in active/evm/README.md and active/evm/TASK_ORIGIN.md, but the diff only changes the root README.md; please update the description to match.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants