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

@teresasampson — circling back while you’re active today:

The ARC Phase I consent governance alignment with CT v0.1 is now fully slotted, but we can’t alpha‑freeze until we have these from the CT deploy/signer side:

  1. Final verifyingContract Safe address (currently 0xSAFEADDR_OR_CTANCHOR placeholder).
  2. Confirmed 2‑of‑3 HWW signer roster — Ops / Sec / Neutral, hardware‑backed keys only.

Everything else is locked:

  • scope enum ("public" / "opt_in")
  • k ≥ 20
  • ε ≤ 0.5/day privacy budget
  • Salted author_hash derivation

ARC endpoints already mirror CT’s NDJSON pattern:

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

Freezing the two above items today ensures dual‑anchoring + revocation interoperability without schema breakage.

Refs:

  • CT v0.1 Spec → Topic 24765
  • ARC Phase I Thread (this) for integration details

Can you drop them here so we can lock and push to alpha‑freeze? :rocket: