| simd | title | authors | category | type | status | created | feature | supersedes | superseded-by | extends | |
|---|---|---|---|---|---|---|---|---|---|---|---|
XXXX |
Title of SIMD |
|
Standard/Meta |
Core/Networking/Interface/Meta |
Draft |
(fill me in with today's date, YYYY-MM-DD) |
(fill in with feature tracking issues once accepted) |
(optional - fill this in if the SIMD supersedes a previous SIMD) |
(optional - fill this in if the SIMD is superseded by a subsequent SIMD) |
(optional - fill this in if the SIMD extends the design of a previous SIMD) |
A brief summary of what the feature is.
Why are we doing this? What use cases does it support? What is the expected outcome?
What alternative designs were considered and what pros/cons does this feature have relative to them?
Is there any new terminology introduced with this proposal?
Explain the feature as if it was already implemented and you're explaining it to another Solana core contributor. The generally means:
- Explain the proposed change and how it works
- Where the feature fits in to the runtime, core, or relevant sub-system
- How this feature was/could be implemented
- Interaction with other features
- Edge cases
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 and RFC 8174.
How will the implemented proposal impacts dapp developers, validators, and core contributors?
What security implications/considerations come with implementing this feature? Are there any implementation-specific guidance or pitfalls?
Why should we not do this?
Does the feature introduce any breaking changes? All incompatibilities and consequences should be listed.