docs: refresh securing-mpc-with-tee-design-doc collateral-retrieval description

Open Beginner friendly
#3,096 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
85/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Quiet
Domain
documentation

Research direction

Open docs/securing-mpc-with-tee-design-doc.md at line 438 and compare the collateral flow with PRs #2944, #3010, and #3026. Check the operator guide PCCS configuration section from #3095; done means the stale endpoint and future-release note are removed, direct PCCS fallback is described, and the operator-facing configuration is cross-referenced.

Written by the indexing model from the issue text.

Description

Background

docs/securing-mpc-with-tee-design-doc.md line 438 says:

Collateral - the node will retrieve this from Phala's collateral
endpoint https://proof.t16z.com (api/upload)

This is stale. PR #2944 replaced the Phala combined-verify
endpoint with direct PCCS calls via dcap-qvl, and PR #3010 made
the endpoint list operator-configurable (multiple URLs, fallback in
order). The node no longer hits proof.t16z.com at all.

User Story

As a reader of the security design doc, I want it to describe how
collateral is actually retrieved, so I can understand the trust
model and threat surface without being misled by historical text.

Acceptance Criteria
  • Update line 438 (and the surrounding bullet/paragraph) to
    describe direct PCCS calls via dcap-qvl, with the configured
    pccs_endpoints list (default Phala) tried in order until one
    succeeds.
  • Drop the _Note - In a future release we may move to other Collateral retrieval methods, like self hosted DCAP, or on chain collateral._ line — self-hosted DCAP is supported now
    (#3026); on-chain collateral remains future.
  • Cross-reference the operator guide's PCCS configuration section
    for the operator-facing knobs.
Resources & Additional Notes
  • Direct PCCS calls landed in: near/mpc#2944
  • Multi-endpoint fallback: near/mpc#3010
  • Per-URL TLS trust override: near/mpc#3026
  • Operator guide PCCS section: near/mpc#3095
Dominant language
Rust
Stars
44
Forks
42
Avg merge
1d 13h
Merged PRs (30d)
111

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from near/mpc

All issues in near/mpc

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.