Community
Questions, ideas, vulnerabilities
Questions, ideas, vulnerabilities — every channel has its place.
Pick the channel that fits
We sort mail by topic so your message lands where it belongs.
Expertise
The protocol is open to developers — share your expertise in cryptographic identity, security, or developer tooling.
Me2eM Team
Maintainers of the Me2eM protocol — a decentralized, seed-derived identity and authorization protocol.
A
B
C
Frequently asked
Who maintains Me2eM?
Me2eM is developed on a voluntary basis: the protocol, the packages, and this website are maintained by volunteers under the me2em-org organization on GitHub. The project needs sponsorship — contributions directly fund development and infrastructure.
Why is the protocol name capitalised the way it is?
"Me2eM" is the only correct form in human-facing prose. The all-lowercase variant is reserved for machine identifiers (code, URLs, packages). The brand does not decline or conjugate — the "iPhone rule". The full rules live in the Brand Guidelines.
Can I use the Me2eM code, name, and logo?
Yes. The protocol source (GitHub) is licensed under Apache 2.0, and this website under MIT. The name and logo may be used to refer to the protocol and compatible implementations, provided the brand canon is respected: the name is written Me2eM, the logo is used as-is. Full rules: Brand Guidelines.
Where is the documentation?
All documentation lives at /docs — core guides, API references, glossary, and quick starts. Package references: @me2em/core, @me2em/crypto, @me2em/react.
How do I report a vulnerability?
Email [email protected] — this is the only private channel. See SECURITY.md in the protocol repository for details.
How can I contribute?
Check CONTRIBUTING.md in the protocol repository for guidelines on filing issues, opening pull requests, and joining discussions.