SEP-0000: Template
SEP-0000: Template
SEP-0000:
| Field | Value |
|---|---|
| SEP | 0000 |
| Title | |
| Author(s) | <Name / handle> |
| Status | Draft |
| Created | YYYY-MM-DD |
| Target Spec Version | <e.g., 1.1.0> |
Summary
One paragraph explaining the change.
Motivation
What problem does this solve? Why is the current specification insufficient? Use RFC 2119 keywords where you are specifying required behavior.
Specification
The normative description of the change. Include:
- Prose changes to the relevant spec document(s).
- Any changes to the JSON Schemas, shown as before/after.
Backwards Compatibility
State explicitly whether this change is backwards compatible. If it is not, describe the migration path and the SemVer impact (MAJOR / MINOR / PATCH).
Security Considerations
Describe any new attack surface or mitigation. Cross-reference the Security document.
Reference Implementation
Optional. Link to a proof-of-concept implementation, if any.
Open Questions
List unresolved issues that must be settled before acceptance.