Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Dstack spike — boot the universal image in a CVM, verify the chain end-to-end

未关闭
#491 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
15/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
cloud, docker, github, typescript

调研方向

Start with ADR 0027 and the deploy train that produces BOS_IMAGE_DIGEST; issue #490 must land first. The spike requires provisioning a Phala Dstack TDX CVM, booting the pinned universal image, and checking attestation, trustless verification, and in-CVM TLS. Record the Path B feasibility verdict and findings in ADR 0027, then update its status.

由索引模型根据 Issue 内容生成。

描述

ready-for-human

Blocked by: #490 (ADR 0027 must exist first)

What to build

A throwaway spike proving the confidential verified-serving tier (ADR 0027) end to end: deploy the universal image to a testnet Phala Dstack CVM and verify the full chain of trust. Output is spike notes appended to ADR 0027 and a go/no-go on its strong version — then promote the ADR to Accepted or amend it.

Steps

  1. Prereqs (human-side): Phala Cloud account + TDX CVM provisioning; decide instance sizing. No platform code changes expected — the universal image is already the right artifact.
  2. Boot Path A first (self-contained): build/push a testnet image whose compose pins the GHCR digest (the deploy train already produces BOS_IMAGE_DIGEST); stage the tenant namespace so the instance boots self-contained; run it in the CVM with BOS_ACCOUNT/BOS_GATEWAY env.
  3. Verify the chain:
    • compose-hash (RTMR3) ↔ pushed GHCR digest ↔ the exact bytes CI built
    • /.well-known/attestation returns quote + event log + VM config; nonce freshness via reportData works
    • Trustless verification locally with dcap-qvl / dstack-verifier (not just Phala's hosted API)
    • TLS terminated inside the CVM (ZT-TLS pattern): enclave-held ACME keys, /evidences/ bound to the quote, CAA records set
  4. Go/no-go: config-hash runtime-data binding (Path B's anchor). Can the enclave report the resolved FastKV config hash (+ registry height) in runtime data, and hard-gate CDN-fetched bundles against the config's SRI pins? If awkward, record the fallback: Path A-only verification (compose-hash ↔ digest, no config binding).
  5. Write up: append spike notes to ADR 0027 with findings, friction points, and the Path B verdict; update the ADR Status (Proposed → Accepted, or amend). Flag future work: bos deploy --confidential, bos verify <domain>, on-chain DCAP verification, FastKV-published measurement allowlist.

Acceptance criteria

  • Universal image boots in a testnet Dstack CVM, self-contained, identity-driven (BOS_ACCOUNT/BOS_GATEWAY)
  • Compose-hash verified against the pushed GHCR digest
  • /.well-known/attestation verified trustlessly (local dcap-qvl/dstack-verifier), nonce-fresh
  • TLS termination inside the CVM with evidence binding demonstrated
  • Path B (config-hash runtime-data binding + in-enclave SRI pin gating) verdict recorded: feasible or fallback
  • Spike notes appended to ADR 0027; Status updated
主要语言
TypeScript
星标
5
派生
3
平均合并
10 小时 12 分钟
30 天内合并 PR
102

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

NEARBuilders/everything-dev 的其他 Issue

查看 NEARBuilders/everything-dev 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。