feat(docs): update docs branding for The Interfold rename#1402
Merged
Conversation
Updated the description of Encrypted Execution Environment (E3) and its components for clarity. Revised use cases and developer interaction steps to enhance understanding.
Revised the section on when to use E3s for clarity.
This one may need a closer eye.
Updated terminology from 'Enclave' to 'Interfold' and improved clarity in several sections.
Updated references from 'Enclave' to 'Interfold' and made minor text adjustments for consistency and clarity.
Updated references from 'Enclave' to 'Interfold' throughout the document, including setup instructions and key takeaways.
Updated references from 'Enclave' to 'Interfold' and adjusted related terms for clarity.
Updated ticket price terminology and clarified fee token units.
Updated references from 'Enclave' to 'Interfold' in the introduction and project structure sections, clarifying the technology used in the CRISP protocol documentation.
Updated text for clarity and corrected formatting for RISC Zero and Node.js.
Updated the title of the whitepaper to 'Enclave Whitepaper' and added a description for clarity.
Added a note about the previous name 'Enclave' and the ongoing transition.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis PR systematically rebrands the project and documentation from "Enclave" to "The Interfold", updating terminology, imagery, domain links, metadata, banners, and minor wording across the README, docs site, theme config, and many documentation pages. Changes
Sequence Diagram(s)(omitted) Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 14
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
docs/pages/project-template.mdx (2)
16-20:⚠️ Potential issue | 🟠 MajorAvoid rebranding the actual template identifiers here.
This page still documents concrete names users must use today:
enclavecommands/config,@enclave-e3/sdk,EnclaveSDK, anduseEnclaveSDK. Calling those the “Interfold CLI/SDK/adapters” makes it sound like the identifiers changed too, which conflicts with the no-breaking-change goal and can mislead onboarding.✏️ Suggested wording
-├── contracts/ # Hardhat workspace with Interfold adapters + your E3 program contracts +├── contracts/ # Hardhat workspace with the current Enclave adapters + your E3 program contracts ... -| `pnpm dev:ciphernodes` | Calls the Interfold CLI to launch the nodes defined in `enclave.config.yaml`. | +| `pnpm dev:ciphernodes` | Calls the `enclave` CLI to launch the nodes defined in `enclave.config.yaml`. | ... -The template already wires the [Interfold SDK](/sdk): +The template already wires the current [`@enclave-e3/sdk`](/sdk) package:Also applies to: 39-39, 57-61
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/pages/project-template.mdx` around lines 16 - 20, The docs text mistakenly rebrands concrete identifiers—restore the real names in prose and examples so users see the exact identifiers to use: keep "enclave" commands/config, the package name "@enclave-e3/sdk" and the exported identifiers "EnclaveSDK" and "useEnclaveSDK" (do not replace them with “Interfold” variants); reword any sentence that implies the identifiers changed to instead say that Interfold is the organization/branding while the CLI/SDK identifiers remain unchanged, and update the three affected sections that reference these names accordingly.
20-25:⚠️ Potential issue | 🟠 MajorUpdate docs/pages/project-template.mdx to include the full project structure generated by
enclave init.The documented layout is incomplete. According to the official Enclave documentation, the actual template includes four additional top-level directories that are missing from the current docs:
contracts/– Hardhat workspace with Enclave adapters + your E3 program contractsprogram/– RISC Zero guest codeserver/– TypeScript coordination serverclient/– React + Vite frontend wired to@enclave-e3/sdkThese should appear at the beginning of the directory tree, before
deploy/. Update both sections (lines 20–25 and 32–38) to match the actual project structure that users will receive when runningenclave init.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/pages/project-template.mdx` around lines 20 - 25, Update the project template tree in docs/pages/project-template.mdx to include the four missing top-level directories created by `enclave init`: add `contracts/`, `program/`, `server/`, and `client/` at the top of the directory listing (before the existing `deploy/` entry) and make the exact same change in the second occurrence of the tree later in the file so both sections (the one around lines 20–25 and the one around lines 32–38) reflect the real scaffold produced by `enclave init`.
🧹 Nitpick comments (2)
docs/pages/CRISP/setup.mdx (1)
44-44: Minor capitalization inconsistency with "Ciphernodes".Line 44 capitalizes "Ciphernodes", but Line 35 uses lowercase "ciphernodes" in the comment, and Line 88 refers to the "ciphernode network". Consider aligning to a consistent style throughout.
✏️ Suggested fix for consistency (if treating as proper noun)
-# Start all services (Hardhat, contracts, ciphernodes, program server, coordination server, and UI) +# Start all services (Hardhat, contracts, Ciphernodes, program server, coordination server, and UI)at Line 35, and:
-The `enclave.config.yaml` file in the CRISP root directory configures the ciphernode network. +The `enclave.config.yaml` file in the CRISP root directory configures the Ciphernode network.at Line 88.
Alternatively, revert Line 44 to lowercase if "ciphernode" is intended as a generic term.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/pages/CRISP/setup.mdx` at line 44, The doc uses inconsistent capitalization for the term "ciphernode" — update occurrences so the term is consistent (either always lowercase "ciphernode"/"ciphernodes" or always capitalized "Ciphernode"/"Ciphernodes"); specifically change the instance "Ciphernodes" on the line currently reading "Starts Ciphernodes using `enclave.config.yaml` via `scripts/dev_cipher.sh`" to match the chosen style and ensure the other mentions ("ciphernodes" and "ciphernode network") are adjusted accordingly throughout the CRISP setup page.docs/theme.config.jsx (1)
91-91: Consider using absolute URL for Twitter image.The OG image (line 78) uses a full URL (
https://docs.theinterfold.com/interfold-meta.jpg), but the Twitter image uses a relative path. Twitter's crawler may not resolve relative paths correctly, potentially causing missing card images.📝 Proposed fix
- <meta property='twitter:image' content='/interfold-meta.jpg' /> + <meta property='twitter:image' content='https://docs.theinterfold.com/interfold-meta.jpg' />🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/theme.config.jsx` at line 91, The Twitter image meta tag currently uses a relative path in the tag meta property='twitter:image' with content='/interfold-meta.jpg'; replace that value with the same absolute URL used by the OG image (e.g. https://docs.theinterfold.com/interfold-meta.jpg) so Twitter's crawler can resolve the image; update the content attribute of the meta element named twitter:image to the absolute URL to match the og:image entry.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/pages/_meta.json`:
- Around line 100-101: The sidebar entry "whitepaper" currently sets "title":
"Whitepaper" which removes the archived document's specific name; update the
"whitepaper" object's title value in docs/pages/_meta.json to exactly match the
archived document name (e.g., the Enclave-specific title used on the page) so
the nav label stays aligned with the page title.
In `@docs/pages/architecture-overview.mdx`:
- Line 58: Update the typo in the documentation string "Reports computation
reults of the E3P to the Interfold contract" by changing "reults" to "results"
so the sentence reads "Reports computation results of the E3P to the Interfold
contract"; edit the text in docs/pages/architecture-overview.mdx where that
sentence appears.
- Around line 64-66: Update the typo in the "Verifiable systems" list: replace
the text label "Succint SP1" with "Succinct SP1" so the company name is spelled
correctly; locate the list item line containing "Succint SP1" (next to the
Succinct docs link) in the architecture-overview content and correct the string.
In `@docs/pages/building-with-enclave.mdx`:
- Around line 106-107: Update the misspelled hash primitive name in the
documentation: replace the occurrence of "PoseidenT3" with the correct
"PoseidonT3" in the sentence describing the Lean Merkle Tree (the phrase
"PoseidenT3 Hash" should be corrected to "PoseidonT3 Hash") so the primitive is
searchable and accurate.
In `@docs/pages/ciphernode-operators/index.mdx`:
- Around line 8-10: Fix the typo in the paragraph that reads "Ciphernodes are
the distributed workers..." by replacing "exeuction" with "execution" in the
phrase "exeuction environments (E3s)"; update the string "exeuction environments
(E3s)" to "execution environments (E3s)" to correct the spelling.
In `@docs/pages/ciphernode-operators/registration.mdx`:
- Line 42: The documentation has inconsistent token symbols: the
header/requirements use "ETK" but the status example uses "EKT"; update the
status output example in the "Step 5: Verify Active Status" section so that any
occurrences of "EKT" are replaced with "ETK" to match the rest of the page
(ensure the token symbol in the example output and any related mentions are
uniformly "ETK").
In `@docs/pages/hello-world-tutorial.mdx`:
- Line 26: The install prerequisite link text is misleading—replace the link
text "[Interfold CLI installed](/installation)" so it matches the actual
executable used later (e.g., "enclave" or "enclave CLI") to avoid confusion with
the command `enclave init`; update the display text to something like "enclave
CLI installed" while keeping the same target URL so readers can map the
prerequisite to the `enclave init` command used in the tutorial.
In `@docs/pages/installation.mdx`:
- Around line 54-59: Update the installation instructions to point to the
correct GitHub releases URL and archive names: replace the releases link
"https://github.com/gnosisguild/Interfold/releases" with
"https://github.com/gnosisguild/enclave/releases" and change the archive names
"Interfold-linux-x86_64.tar.gz" and "Interfold-macos-aarch64.tar.gz" to
"enclave-linux-x86_64.tar.gz" and "enclave-macos-aarch64.tar.gz" respectively,
keeping the rest of the steps (extract, move to PATH, chmod +x enclave)
unchanged so users can download the correct files.
In `@docs/pages/sdk.mdx`:
- Around line 164-167: Update the prose that lists SDK submodules to match the
actual exports: change the third submodule name from "encryption" to "crypto" so
the sentence reads that the SDK has `contracts`, `events`, and `crypto`
submodules; ensure the example import and any other occurrences refer to
`crypto` (matching the `@enclave-e3/sdk` export) instead of `encryption`.
In `@docs/pages/what-is-e3.mdx`:
- Line 27: The heading "How E3s Works for Developers" has incorrect subject-verb
agreement; update the heading text in docs/pages/what-is-e3.mdx from "How E3s
Works for Developers" to "How E3s Work for Developers" so the plural noun "E3s"
correctly pairs with the verb "Work".
- Line 7: Fix the missing space after the colon in the sentence starting with
"Distributed Threshold Cryptography (DTC):Distributes" by inserting a single
space so it reads "Distributed Threshold Cryptography (DTC): Distributes" to
match normal punctuation spacing and the surrounding prose.
In `@docs/pages/write-e3-contract.mdx`:
- Line 71: There's a typo in the bullet label "ZKP Vvrification" — update that
label to "ZKP Verification" in the docs bullet (search for the exact string "ZKP
Vvrification" in the write-e3-contract content) so the heading reads "ZKP
Verification: Verify any associated ZKPs to ensure input correctness."
- Around line 65-66: The doc currently misstates where input validation belongs;
change the sentence that tells readers to implement validateInput on the "E3
Program contract" so it correctly says validateInput is implemented on the
separate "Input Validator contract" (and update or cross-reference the existing
e3ProgramParams note on Line 39 to reflect this ownership) to remove the
contradiction with the component split described earlier. Ensure you reference
the function name validateInput, the "Input Validator contract" and the existing
e3ProgramParams note so readers know where to implement and configure
validation.
In `@docs/README.md`:
- Around line 13-14: Replace the inconsistent branding string "Enclave protocol"
with "Interfold protocol" in the README content so it matches the earlier
reference to "the Interfold"; specifically search for the literal text "Enclave
protocol" and update it to "Interfold protocol" to keep terminology consistent
with "the Interfold".
---
Outside diff comments:
In `@docs/pages/project-template.mdx`:
- Around line 16-20: The docs text mistakenly rebrands concrete
identifiers—restore the real names in prose and examples so users see the exact
identifiers to use: keep "enclave" commands/config, the package name
"@enclave-e3/sdk" and the exported identifiers "EnclaveSDK" and "useEnclaveSDK"
(do not replace them with “Interfold” variants); reword any sentence that
implies the identifiers changed to instead say that Interfold is the
organization/branding while the CLI/SDK identifiers remain unchanged, and update
the three affected sections that reference these names accordingly.
- Around line 20-25: Update the project template tree in
docs/pages/project-template.mdx to include the four missing top-level
directories created by `enclave init`: add `contracts/`, `program/`, `server/`,
and `client/` at the top of the directory listing (before the existing `deploy/`
entry) and make the exact same change in the second occurrence of the tree later
in the file so both sections (the one around lines 20–25 and the one around
lines 32–38) reflect the real scaffold produced by `enclave init`.
---
Nitpick comments:
In `@docs/pages/CRISP/setup.mdx`:
- Line 44: The doc uses inconsistent capitalization for the term "ciphernode" —
update occurrences so the term is consistent (either always lowercase
"ciphernode"/"ciphernodes" or always capitalized "Ciphernode"/"Ciphernodes");
specifically change the instance "Ciphernodes" on the line currently reading
"Starts Ciphernodes using `enclave.config.yaml` via `scripts/dev_cipher.sh`" to
match the chosen style and ensure the other mentions ("ciphernodes" and
"ciphernode network") are adjusted accordingly throughout the CRISP setup page.
In `@docs/theme.config.jsx`:
- Line 91: The Twitter image meta tag currently uses a relative path in the tag
meta property='twitter:image' with content='/interfold-meta.jpg'; replace that
value with the same absolute URL used by the OG image (e.g.
https://docs.theinterfold.com/interfold-meta.jpg) so Twitter's crawler can
resolve the image; update the content attribute of the meta element named
twitter:image to the absolute URL to match the og:image entry.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: f6c5d8da-3ec7-4071-a6a9-b0f1b1699b02
⛔ Files ignored due to path filters (6)
docs/public/apple-touch-icon.pngis excluded by!**/*.pngdocs/public/favicon-16x16.pngis excluded by!**/*.pngdocs/public/favicon-32x32.pngis excluded by!**/*.pngdocs/public/favicon.icois excluded by!**/*.icodocs/public/interfold-logo.pngis excluded by!**/*.pngdocs/public/interfold-meta.jpgis excluded by!**/*.jpg
📒 Files selected for processing (30)
README.mddocs/README.mddocs/pages/CRISP/introduction.mdxdocs/pages/CRISP/running-e3.mdxdocs/pages/CRISP/setup.mdxdocs/pages/_meta.jsondocs/pages/architecture-overview.mdxdocs/pages/best-practices.mdxdocs/pages/building-with-enclave.mdxdocs/pages/ciphernode-operators/index.mdxdocs/pages/ciphernode-operators/registration.mdxdocs/pages/ciphernode-operators/running.mdxdocs/pages/computation-flow.mdxdocs/pages/compute-provider.mdxdocs/pages/getting-started.mdxdocs/pages/hello-world-tutorial.mdxdocs/pages/installation.mdxdocs/pages/introduction.mdxdocs/pages/noir-circuits.mdxdocs/pages/project-template.mdxdocs/pages/putting-it-together.mdxdocs/pages/quick-start.mdxdocs/pages/sdk.mdxdocs/pages/setting-up-server.mdxdocs/pages/use-cases.mdxdocs/pages/what-is-e3.mdxdocs/pages/whitepaper.mdxdocs/pages/write-e3-contract.mdxdocs/pages/write-secure-program.mdxdocs/theme.config.jsx
Collaborator
|
Thanks, @eccogrinder . There are a few typos that should be fixed before we merge this in, but otherwise it’s good to go. My docs update PR is mostly focused on correcting the technical explanation and processes: #1401 Your PR can go ahead and be merged first. |
0xjei
reviewed
Mar 10, 2026
0xjei
left a comment
0xjei
left a comment
Contributor
There was a problem hiding this comment.
great progress, there are just a few nits and is ready to go. I am not sure if we want to change repository links as well at this stage. If not, ignore the related comments that I have left! thanks @eccogrinder <3
Contributor
There was a problem hiding this comment.
Actionable comments posted: 9
🧹 Nitpick comments (2)
docs/pages/CRISP/setup.mdx (1)
44-44: Inconsistent capitalization of "Ciphernodes".Line 44 capitalizes "Ciphernodes", but line 88 uses "ciphernode network" and line 160 uses "ciphernodes" (both lowercase). Consider making this consistent throughout the document.
📝 Suggested fix for consistency
If capitalizing as a proper noun:
-3. Starts Ciphernodes using `enclave.config.yaml` via `scripts/dev_cipher.sh` +3. Starts ciphernodes using `enclave.config.yaml` via `scripts/dev_cipher.sh`Or update lines 88 and 160 to match the capitalized style.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/pages/CRISP/setup.mdx` at line 44, The document uses inconsistent capitalization for the project term (e.g., "Ciphernodes" vs "ciphernode network" vs "ciphernodes"); pick the canonical form (either "Ciphernodes" as a proper noun or lowercase "ciphernodes"/"ciphernode network") and update all occurrences to match—specifically change the instances referenced by the strings "Ciphernodes", "ciphernode network", and "ciphernodes" so the term is consistently capitalized throughout the page.packages/enclave-mcp/README.md (1)
3-4: Consider updating documentation site references to the new domain.The README still references
enclave.gganddocs.enclave.gg, but based on the broader PR changes (e.g., README.md line 489 usesdocs.theinterfold.com), the documentation domain has been updated. While keeping the package name@enclave-e3/mcpis intentional, the documentation links should point to the new domain for consistency.📝 Proposed fix
-MCP server for [Enclave](https://enclave.gg) documentation. Allows AI assistants to answer questions -about Enclave by fetching content directly from [docs.enclave.gg](https://docs.enclave.gg). +MCP server for [The Interfold](https://theinterfold.com) documentation. Allows AI assistants to answer questions +about The Interfold by fetching content directly from [docs.theinterfold.com](https://docs.theinterfold.com).🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@packages/enclave-mcp/README.md` around lines 3 - 4, Update the README links that currently point to enclave.gg and docs.enclave.gg so they use the new documentation domain (e.g., replace "enclave.gg" / "docs.enclave.gg" with "theinterfold.com" / "docs.theinterfold.com" respectively) while keeping the package name `@enclave-e3/mcp` unchanged; search the README for any occurrences of "enclave.gg" or "docs.enclave.gg" and replace them with the corresponding new domain strings to ensure consistency with the rest of the PR.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/pages/architecture-overview.mdx`:
- Around line 94-95: Typo in the developer guidance bullet: in the bullet text
starting with "Compute Providers" replace the misspelled word "verfiable" with
"verifiable" so the line reads "Compute Providers: To run your E3P using
verifiable or oracle-based systems." Locate the markdown bullet under "Compute
Providers" and update the word only, preserving surrounding punctuation and
formatting.
In `@docs/pages/best-practices.mdx`:
- Around line 8-9: Replace occurrences of the standalone word "Interfold" in the
docs text with the official rebrand "The Interfold" (capital T and capital I) so
the sentence reads "clear guardrails for confidential compute. This guide
distills the equivalent playbook for the The Interfold." — locate the phrase
"Interfold" in the sentence and prepend "The " to make the proper name "The
Interfold".
In `@docs/pages/building-with-enclave.mdx`:
- Line 1: Update the H1 page title header string "# Building with the Interfold"
so that "The" is capitalized as part of the proper name; locate the header line
(the H1 starting with "Building with the Interfold") and change it to "#
Building with The Interfold" to reflect the correct proper noun capitalization.
In `@docs/pages/installation.mdx`:
- Around line 3-18: Replace every instance of the product name that uses
"Interfold", "Interfold CLI", or phrases like "installing Interfold" with the
approved full brand name "The Interfold" (capitalized and including "The"),
including the page title/heading and the Quick Install section; specifically
update strings such as "Interfold CLI", "installing Interfold", and any other
occurrences in this document to "The Interfold" to ensure consistent branding
across headings and body copy.
In `@docs/pages/putting-it-together.mdx`:
- Line 218: Replace the lowercase "the" in the phrase "the Interfold" with an
uppercase "The" so the text reads "The Interfold" (update the occurrence in the
line containing "[Gnosis Guild](https://gnosisguild.org), the initial
development team building the Interfold." to use "The Interfold").
- Around line 185-191: The document uses "the Interfold" in lowercase but the
official branding requires "The Interfold"; search the page for all occurrences
of the phrase (plain text, bolded, and inside list items/headings) and replace
"the Interfold" with "The Interfold" so capitalization is consistent (e.g.,
update the sentence "The Interfold provides a framework..." and the list item "-
The Interfold distributes trust..." plus any other instances, including bold or
emphasized variants).
In `@docs/pages/sdk.mdx`:
- Around line 2-8: Update the SDK-facing copy to use the full rebrand name "The
Interfold" by renaming occurrences of "Interfold SDK" to "The Interfold SDK"
(e.g., the frontmatter title string and the header "# Interfold SDK"); also
update other inline prose occurrences referenced (around lines 198-210) that
drop the leading "The" so all instances consistently read "The Interfold SDK".
- Around line 177-180: Clarify that the config key name hasn't changed by
explicitly referencing the existing mapping: update the sentence to say that the
Interfold, CiphernodeRegistry, and FeeToken addresses are provided via the
existing contracts.enclave mapping (e.g., VITE_ENCLAVE_ADDRESS) rather than
implying a new interfold key; mention the exact symbols contracts.enclave and
VITE_ENCLAVE_ADDRESS so readers know where to find the addresses for Interfold,
CiphernodeRegistry, and FeeToken.
In `@docs/README.md`:
- Around line 13-14: Update the inconsistent capitalization in the README text
by changing the phrase "the Interfold" to "The Interfold" so the project name is
consistently capitalized; locate the occurrence of the string "the Interfold" in
the README paragraph (the line that currently reads "This is the documentation
site for the Interfold...") and replace it with "The Interfold" to match "The
Interfold protocol".
---
Nitpick comments:
In `@docs/pages/CRISP/setup.mdx`:
- Line 44: The document uses inconsistent capitalization for the project term
(e.g., "Ciphernodes" vs "ciphernode network" vs "ciphernodes"); pick the
canonical form (either "Ciphernodes" as a proper noun or lowercase
"ciphernodes"/"ciphernode network") and update all occurrences to
match—specifically change the instances referenced by the strings "Ciphernodes",
"ciphernode network", and "ciphernodes" so the term is consistently capitalized
throughout the page.
In `@packages/enclave-mcp/README.md`:
- Around line 3-4: Update the README links that currently point to enclave.gg
and docs.enclave.gg so they use the new documentation domain (e.g., replace
"enclave.gg" / "docs.enclave.gg" with "theinterfold.com" /
"docs.theinterfold.com" respectively) while keeping the package name
`@enclave-e3/mcp` unchanged; search the README for any occurrences of "enclave.gg"
or "docs.enclave.gg" and replace them with the corresponding new domain strings
to ensure consistency with the rest of the PR.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: fa26db97-bf9c-4d10-aecb-fc0c8527671c
📒 Files selected for processing (27)
README.mddocs/README.mddocs/pages/CRISP/introduction.mdxdocs/pages/CRISP/running-e3.mdxdocs/pages/CRISP/setup.mdxdocs/pages/architecture-overview.mdxdocs/pages/best-practices.mdxdocs/pages/building-with-enclave.mdxdocs/pages/ciphernode-operators/index.mdxdocs/pages/ciphernode-operators/registration.mdxdocs/pages/ciphernode-operators/running.mdxdocs/pages/computation-flow.mdxdocs/pages/compute-provider.mdxdocs/pages/getting-started.mdxdocs/pages/installation.mdxdocs/pages/introduction.mdxdocs/pages/noir-circuits.mdxdocs/pages/project-template.mdxdocs/pages/putting-it-together.mdxdocs/pages/sdk.mdxdocs/pages/use-cases.mdxdocs/pages/what-is-e3.mdxdocs/pages/whitepaper.mdxdocs/pages/write-e3-contract.mdxdocs/pages/write-secure-program.mdxpackages/enclave-mcp/README.mdpackages/enclave-mcp/tsup.config.ts
✅ Files skipped from review due to trivial changes (1)
- packages/enclave-mcp/tsup.config.ts
🚧 Files skipped from review as they are similar to previous changes (10)
- docs/pages/use-cases.mdx
- docs/pages/compute-provider.mdx
- docs/pages/getting-started.mdx
- docs/pages/ciphernode-operators/running.mdx
- docs/pages/whitepaper.mdx
- docs/pages/CRISP/running-e3.mdx
- docs/pages/CRISP/introduction.mdx
- docs/pages/write-secure-program.mdx
- docs/pages/write-e3-contract.mdx
- docs/pages/computation-flow.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR updates docs and repo-facing branding from Enclave to the Interfold where appropriate, without changing underlying tooling identifiers. (FYI: I don't have access to change the "About" page text.)
I made several commits before opening this PR and wanted to note what was intentionally left unchanged / may need follow-up.
Included
Intentionally left unchanged
enclaveEnclaveTokenFollow-up / clarification
In a few places, the docs now use Interfold conceptually while the underlying tooling still uses
enclave. I left actual identifiers unchanged to keep this PR non-breaking.Additional follow-up items:
putting-it-together.mdx/dnsaddr/bootstrap.enclave.ggleft as-isExample intentionally left unchanged: