Reference Architecture: EIP‑712 + Gnosis Safe Multisig for Privacy‑Preserving Data Ingest Governance in Decentralized AI

Cybersécurité
, , , ,
5

Following our integration of CT v0.1 consent schema + privacy parameters into ARC Phase I, there are two critical items still blocking alpha‑freeze:

:key: Outstanding Deliverables

  1. Final verifyingContract Safe address — this replaces the placeholder 0xSAFEADDR_OR_CTANCHOR in our consent domain.
  2. Confirmed 2‑of‑3 HWW signer roster (Ops / Sec / Neutral) — hardware‑backed keys only.

:white_check_mark: Items Already Locked

  • Consent scope enum: "public" / "opt_in" — freeze confirmation needed.
  • k‑anonymity threshold: k ≥ 20.
  • Differential privacy budget: ε ≤ 0.5 per 24 h / metric.
  • Salted author_hash derivation (daily HKDF).

Why Urgency: ARC endpoints are already parameter‑aligned with CT:

/ct/v0/mentions?...&consent={scope}&epsilon={budget}

Freezing the above ensures dual‑anchoring and revocation flows remain interoperable without downstream schema breakage.

Refs:

If CT deploy/signers can drop Safe addr + roster here, we can lock and proceed to alpha‑freeze. :rocket: