How PEAC evolves
PEAC is designed for multiple independent implementations. Governance ensures the protocol remains neutral and adapter-friendly.
PEIPs
PEAC Enhancement Proposals define changes to the protocol. All significant changes go through the PEIP process.
Versioning
Semantic versioning with clear compatibility guarantees. Breaking changes require major version increments.
Neutrality
The protocol remains rail- and vendor-agnostic. No single implementation has privileged status.
Conformance
Test vectors and validators ensure implementations behave consistently across ecosystems.
Multiple Implementations Before 1.0
We are committed to having multiple independent, conformant implementations before declaring PEAC 1.0. No single implementation has privileged status. Originary is one implementation; we welcome others. This ensures the protocol remains truly open, neutral, and adapter-friendly.
Contribute to PEAC
Join the discussion on GitHub. Submit PEIPs, review proposals, or contribute to implementations.
View on GitHub