Community
Build the protocol in public.
ECCP should be inspectable as both a standard and a codebase. Releases, contribution paths, and discussion channels are surfaced here so the project does not depend on private coordination.
GitHub Releases
Recent shipping activity from the public repo.
Release data is fetched from the GitHub API at build time, with a safe static fallback if the API is unavailable.
No releases were returned from the GitHub API. Check repository permissions or publish the first tagged release to populate this section.
Contribution Flow
Fork, ship, and review in public.
ECCP should evolve through auditable discussion. Protocol work, client UX, and bridge contributions all benefit from the same public review surface.
Fork
Fork the repository, branch from the current mainline, and keep the change scoped to one clearly reviewable concern.
PR
Open a pull request with protocol rationale, screenshots when relevant, and links to any specification discussion that shaped the change.
Review
Expect feedback on correctness, trust boundaries, and regression risk. Security-sensitive changes should explain the threat model explicitly.
Community Surface
Join the channels that match the work.
Keep protocol conversations public, route feature ideas through GitHub, and handle sensitive vulnerability reports through the security path.
Matrix Room
Coordinate with contributors in the public ECCP Matrix room.
GitHub Discussions
Use discussions for roadmap questions, implementation notes, and ecosystem proposals.
Security Policy
Read the disclosure surface and report security issues through the documented channel.