Web3 Charge Protocol (W3CP) – A modern, identity-first EV charging protocol designed for simplicity, security, and Web3-native integration.
W3CP is currently an experimental research and demonstration project. W3CP does not implement or extend OCPP and is not intended to be an OCPP-compatible protocol.
W3CP explores a fundamentally different, identity-first architecture for EV charging. Any future interoperability with existing protocols, if pursued, would be handled via separate compatibility or adapter layers, outside the core protocol specification.
- This specification and any accompanying demos are not production-ready
- APIs, data models, and flows may change without notice
- No stability, security, or availability guarantees are provided
- Not intended for commercial or operational use at this stage
- Project does not support OCPP and is not intended to.
The goal of the project at this phase is exploration, validation, and iteration of ideas around identity-first EV charging.
The EV charging world deserves better.
For too long, the charging ecosystem has been burdened by outdated, fragmented, and inflexible protocols — systems that stifle innovation, confuse developers, and slow down progress.
W3CP was created to change that.
W3CP is designed from the ground up as a unified, secure, and evolving platform.
Its purpose is simple: to give developers, infrastructure manufacturers, vehicle makers, and most importantly users a coherent and modern foundation that adapts as fast as technology does.
Charging is not static — neither should the protocol be.
At the heart of W3CP lies decentralized identity.
Authenticity, ownership, and security are not afterthoughts — they are the DNA of the protocol.
Every interaction in W3CP begins with identity, ensuring trust and transparency across the entire ecosystem.
W3CP is built by engineers who live the complexity of today’s charging protocols.
It’s structured, modern, and simple — a protocol that feels like an API you actually want to work with.
It enables:
- Automated and testable flows for cars, charge points, and backends
- Dynamic adaptability without breaking changes
- Clear “smart capabilities” that define exactly what each side supports
No more guessing. No more brittle versions. No more breaking every release.
| 🚀 W3CP | |
|---|---|
| Fragmented and asynchronous mess — every implementation behaves differently, leading to inconsistent user experiences. | Structured, modern, and simple. Designed for predictability and coherence across all actors. |
| Poor concept of identity. Authentication and authorization are often an afterthought. | Identity-first design. Decentralized identity is the core, enabling secure and seamless interactions. |
| Brittle versions and painful migrations. Upgrades break compatibility and slow innovation. | Evolving platform. Versionless evolution allows dynamic feature rollout without breaking existing systems. |
| No focus on automation or testability. Manual testing dominates and slows certification. | Automation-ready. Built for continuous testing, validation, and CI/CD integration. |
| Mixes simple and complex use cases in one bloated spec. Hard to implement and even harder to extend. | Simple core, extensible design. Clean separation between essentials and optional features. |
| Vague API definitions. Developers struggle to understand what features are supported. | Smart Capabilities. Each side clearly advertises supported features — no more guessing or hidden behavior. |
| Limited evolution toward Web3 and digital trust models. | Future-ready. Integrates decentralized identities, blockchain integrity, and transparent APIs. |
W3CP starts simple — and grows with you.
Its extension-first philosophy allows seamless evolution without chaos.
Whether you’re building a minimal home charger or a smart energy ecosystem, W3CP scales with your ambition.
W3CP is more than just a protocol — it’s a foundation for the next era of energy.
An ecosystem built around:
- Decentralized identities
- Blockchain-backed integrity
- Smart capabilities
- Transparent, interoperable APIs
It’s a protocol that evolves with time — not against it.
For those who build.
For those who innovate.
For those who care about doing things right.
Charging. Standardized.