Skip to content

Docs: adopt "peppercorn" terminology (no interface changes) - #122

Draft
zjma wants to merge 1 commit into
mainfrom
cursor/pepper-terminology-rename-d458
Draft

zjma wants to merge 1 commit into
mainfrom
cursor/pepper-terminology-rename-d458

Conversation

@zjma

@zjma zjma commented May 5, 2026

Copy link
Copy Markdown
Collaborator
  • Add a Terminology section in README.md clarifying the naming update:
    • "the pepper" (formerly "pepper base"): long-lived provider secret
    • "peppercorn" (formerly "pepper"): one-way derivative used by circuit/APIs
  • Update comments to use "peppercorn" while retaining field/type names for compatibility:
    • prover-service/src/input_processing/public_inputs_hash.rs (hash comment)
    • prover-service/src/request_handler/types.rs (RequestInput.pepper doc)
    • circuit/templates/keyless.circom (signal pepper naming note)
  • Update the Python tool print label to "Peppercorn" in circuit/tools/input_gen.py.

Notes:

  • No code/ABI changes; all field names and Rust types remain pepper to avoid breaking dependents.
  • This PR addresses the internal terminology proposal from Slack.

Slack Thread

Open in Web Open in Cursor 

Co-authored-by: zhoujunma <zhoujun@aptoslabs.com>
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.

2 participants