Current
Requests for Comment
Review substantial protocol, policy, economic, security, governance, and cross-repository proposals before treating them as commitments.
When an RFC is required
- A public protocol or interoperability contract changes.
- Order, payment, settlement, dispute, identity, authorization, or custody boundaries change.
- A fee, recipient, reward, public fund, or economic policy changes.
- A new optional hosted dependency changes independent-operation assumptions.
- Governance, licensing, privacy, security, or cross-repository ownership changes materially.
Status model
- Draft: authoring is incomplete.
- Review: ready for public technical and product review.
- Accepted or Rejected: the decision is recorded with rationale.
- Withdrawn: the author no longer proposes the change.
- Superseded: another RFC replaces the proposal.
- Implemented: release evidence confirms that the accepted proposal shipped within a stated scope.