fix: add slashing manager to sample config

[ctrlc03]

Summary by CodeRabbit

• Documentation
  • Updated CipherNode operator running instructions: example configuration files for both CLI and Docker methods now include two additional chain contract entries (slashing_manager and fee_token) with accompanying address and deploy block fields to make sample configs more complete and setup easier.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
enclave-docs	Ready	Preview, Comment	Jun 3, 2026 10:06pm
enclave-enclave-dashboard	Ready	Preview, Comment	Jun 3, 2026 10:06pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
crisp	Skipped		Jun 3, 2026 10:06pm

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 5c8acaed-3fd6-4959-a9a7-f33b6ffa64ec

📥 Commits

Reviewing files that changed from the base of the PR and between 9f48ba6 and 598a0c8.

📒 Files selected for processing (1)

• docs/pages/ciphernode-operators/running.mdx

✅ Files skipped from review due to trivial changes (1)

• docs/pages/ciphernode-operators/running.mdx

---

📝 Walkthrough

Walkthrough

The PR updates the running guide docs by adding slashing_manager and fee_token contract entries (with address and deploy_block) to the example chains -> contracts YAML in both Method 2 (Interfold CLI) and Method 3 (Docker).

Changes

Contract Configuration Example

Layer / File(s)	Summary
Contract configuration example update docs/pages/ciphernode-operators/running.mdx	The chains -> contracts YAML examples for Method 2 (Interfold CLI) and Method 3 (Docker) are extended to include slashing_manager and fee_token entries with address and deploy_block.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• gnosisguild/enclave#1522: Updates the same documentation file with related contract configuration changes.
• gnosisguild/enclave#1341: Also modifies the chains -> contracts example config.yaml entries in the running guide.

Suggested labels

documentation

Suggested reviewers

• hmzakhalid
• 0xjei

Poem

🐰 I hopped through docs with a careful paw,
Two contracts added, neat and law-abiding,
Addresses and blocks tucked in their place,
Operators’ examples now match the trace,
Cheers from the burrow for a tidy config!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title mentions 'slashing manager' but the changes also add 'fee_token' contract entries, making the title incomplete regarding all modifications.	Consider updating the title to reflect all additions, such as 'fix: add slashing manager and fee token to sample config' for complete accuracy.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/ciphernode-guide

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/pages/ciphernode-operators/running.mdx`:
- Around line 108-113: The Docker config.yaml example is missing the required
slashing_manager entry; update the Docker/example config block (the YAML under
the Docker config example starting at the current Method 3 section) to include a
slashing_manager mapping alongside fee_token, providing the same fields (address
and deploy_block) as in the main config snippet; ensure the slashing_manager key
and values are present and valid so runtime validation that expects
slashing_manager (and fee_token) succeeds.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: b1f430d1-cd32-4111-8828-6393b7b94022

📥 Commits

Reviewing files that changed from the base of the PR and between ed36927 and 9f48ba6.

📒 Files selected for processing (1)

• docs/pages/ciphernode-operators/running.mdx