update decentralization docs

[hadi-saleh14]

Updated attestor decentralization docs to reflect latest zkFetch changes.

Summary by CodeRabbit

• Documentation
  • Updated the zkFetch example section to clarify its functionality and reflect the current decentralized implementation, removing outdated references and providing a more detailed explanation.

[coderabbitai]

Walkthrough

The documentation for the attestor contracts was updated by renaming a section heading and revising the descriptive text to clarify the purpose and functionality of the zkFetch example, reflecting its use of Reclaim's decentralized zkFetch variant and removing outdated references.

Changes

File(s)	Change Summary
content/docs/attestor-decentralization/attestor-contracts.mdx	Renamed "zkFetch Example - Outdated" to "zkFetch Example" and revised description to clarify its demonstration of the decentralized zkFetch variant, removing outdated labeling.

Possibly related PRs

• Attestor docs #37: Adds the attestor-contracts documentation and related decentralization docs, directly connecting to the section updated in this PR.

Poem

A heading refreshed, a story retold,
zkFetch's new journey, in clarity bold.
Outdated no longer, the docs now align,
Decentralized proof, by Reclaim’s design.
🐇✨

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 8, 2025 8:17am

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

content/docs/attestor-decentralization/attestor-contracts.mdx (1)

85-92: Correct spelling and wording for clarity

Minor language tweaks will improve readability:

-Alternatively, you can try out an e2e [example](https://github.com/reclaimprotocol/attestor-contracts/tree/main/examples/zkfetch) of Reclaim's decentralized zkFetch. In contrast to "classical" zkFetch, this variant performs on-chain task creation and returns mutiple proofs based on the contract-specified `requiredAttestors` limit. 
+Alternatively, you can try out an end-to-end [example](https://github.com/reclaimprotocol/attestor-contracts/tree/main/examples/zkfetch) of Reclaim's decentralized zkFetch. In contrast to the "classical" zkFetch, this variant performs on-chain task creation and returns multiple proofs based on the contract-specified `requiredAttestors` limit.

-2.  **Populate your `.env`, add you private key (without the `0x` prefix):**
+2.  **Populate your `.env`, add your private key (without the `0x` prefix):**

This fixes the “mutiple” typo, replaces the abbreviation “e2e” with “end-to-end”, adjusts articles, and corrects “you” → “your”.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e90f81e and de52d76.

📒 Files selected for processing (1)

• content/docs/attestor-decentralization/attestor-contracts.mdx (1 hunks)

🧰 Additional context used

🪛 LanguageTool

content/docs/attestor-decentralization/attestor-contracts.mdx

[grammar] ~83-~83: Use proper spacing conventions.
Context: ... * node index.js ### zkFetch Example Alternatively, you can try out an e2e [e...

(QB_NEW_EN_OTHER_ERROR_IDS_000007)

---

[grammar] ~85-~85: Ensure spelling is correct.
Context: ...orms on-chain task creation and returns mutiple proofs based on the contract-specified ...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_000051)

---

[grammar] ~85-~85: Use proper spacing conventions.
Context: ...act-specified requiredAttestors limit. 1. **Change directory into /examples/zkfetch ...

(QB_NEW_EN_OTHER_ERROR_IDS_000007)