Skip to main content

FPSF-MPC-001 — Governance

Layer: Governance · Audience: contributors, operators, security reviewers


Versioning Policy

This specification follows Semantic Versioning 2.0.0.

SegmentIncrement when...
MAJORBreaking change to the cryptographic protocol, key taxonomy, API, or authentication model. Operators must re-evaluate conformance.
MINORNew endpoints, optional parameters, or protocol extensions that do not break existing conformant implementations.
PATCHEditorial corrections and non-normative clarifications.

Changes of MAJOR version require a minimum 30-day review period, a documented rationale, and a migration guide.


Security Review Policy

Given the security-sensitive nature of this specification, proposed changes to Sections 8 (Cryptographic Foundations), 13 (Group Formation), 14 (DKG), 15 (Threshold Signing), and 27 (Security Considerations) MUST undergo independent cryptographic review before being incorporated into any version above PATCH.


Relationship to Other Specifications

FPSF-MPC-001 is a standalone system specification. It is referenced by FPSF-CPP-001 as the RECOMMENDED mechanism for generating bearer keys. Nothing in FPSF-MPC-001 depends on FPSF-CPP-001 or any other specification in the family.


Contributing


Changelog

VersionDateSummary
1.0.02026-03-25Initial release. Consolidates all prior draft work into a single specification. Defines the three-key taxonomy, Pedersen DKG protocol, FROST signing protocol, VRF-based group formation, public REST API, request authentication model, and all security requirements.

FPSF-MPC-001 v1.0.0 · Draft · Fabric Payment Standards Foundation · Apache-2.0