Skip to main content

EWIP Process

EWP Improvement Proposals (EWIPs) define protocol enhancements.

Overview​

EWIPs follow a structured process similar to Bitcoin BIPs and Ethereum EIPs:

  1. Discussion → GitHub Issue with idea label
  2. Draft → Formal proposal submitted as PR
  3. Review → Community feedback and revision
  4. Final → Merged into specification

Status Flow​

Draft → Review → Final
          ↓
       Withdrawn
          ↓
       Stagnant (6+ months inactive)

EWIP Types​

TypeDescription
CoreProtocol semantics, verification rules
NetworkingHTTP API, endpoints, transport
InterfaceEIP-712 types, JSON schemas
ApplicationHigher-layer patterns

Template​

See proposals/README.md for the full EWIP template.

Scope​

EWIPs MAY address:

  • New message types
  • New endpoints
  • Verification rule changes
  • New content types
  • Discovery mechanisms
  • Cryptographic agility

EWIPs MUST NOT:

  • Remove mandatory fields without version bump
  • Change semantics invalidating existing signatures
  • Introduce centralized dependencies

Contributing​

See CONTRIBUTING.md for full guidelines.