Secure peer-to-peer connectivity between dApps and wallets
Important
You are currently viewing the beta version of the repository.
See the documentation for a live demo.
- Privacy-first, end-to-end encrypted, no metrics, no tracking
- No central dependency, rather a variety of signaling layers
- Peer-to-peer transport via WebRTC (or other transport layers)
- Reuse of existing infrastructure and p2p standards
- User control over connection & configuration
A secure privacy-first protocol for establishing peer-to-peer JSON-RPC connectivity between decentralized applications (dApps) and cryptocurrency wallets.
Open Lavatory Protocol eliminates centralized relay servers by enabling direct peer-to-peer connections between decentralized applications (dApps) and cryptocurrency wallets. Using public signaling servers for initial handshake and WebRTC combined with asymmetric encryption, it prioritizes privacy and self-sovereignty.
Head to the documentation to learn more about openlv.
This repository includes the following packages:
| Package | Description |
|---|---|
| @openlv/session | a session represents a connection between dApp and wallet |
| @openlv/signaling | Implementation of various signaling layers |
| @openlv/transport | Implementation of various transport layers |
| @openlv/provider | EIP-1193 compatible provider |
| @openlv/core | shared types and utilities |
| @openlv/modal | preact modal for dApp connection management |
| @openlv/connector | Wagmi connector for dApp integration |
| [WIP] extension | Browser extension for improved dApp support |
| Examples | Description |
|---|---|
| sandbox | Interactive testing environment with debug features |
| wallet | Sample wallet implementation for testing |
| dapp | Wagmi-based dApp sandbox for end-to-end testing |
| docs | Documentation includes a running wagmi demo |
Important
This specification was written during a hackathon, it has its flaws, and should be treated as a proof of concept.
You can find the entire specification in spec.md.
We accept contributions via pull requests. Please ensure to push changesets for your changes. Also see issues to comment on RFCs.
The initial proof of concept was built in 48 hours at the W3PN Hacks 2025 hackathon in Berlin by @talentlessguy & @lucemans & @nevvdev.