What is Harbor?
Harbor is a self-custodied encrypted messaging protocol being built on Base L2. The current repository is a developer preview with local identity creation, backup primitives, deployed testnet contracts, and incomplete real messaging.
What does self-custody mean?
Self-custody means you hold your own private keys. In the current web implementation, keys are generated and stored locally; V1 backup and device-enrollment flows can export encrypted identity material under user action.
What happens if I lose my device?
If you lose your device without a backup, your identity and message history are permanently lost. There is no recovery mechanism. This is why Harbor prompts you to create an encrypted backup during setup.
How do I backup my identity?
During setup, Harbor prompts you to create an encrypted backup file protected by a password. Store this file securely. The backup cipher round trip works, but persistent restore after reload has a known blocker in the current web client.
What blockchain does Harbor use?
Harbor is built on Base, an Ethereum L2 network. Base provides low transaction costs and fast confirmation times while inheriting Ethereum's security guarantees.
Do I need cryptocurrency to use Harbor?
You need an Ethereum wallet to create a web identity. Real message sending is not launch-ready yet; when enabled, on-chain operations will require Base transaction fees or relayer sponsorship.
How is Harbor different from Signal or WhatsApp?
Harbor is designed around self-custodied keys and blockchain delivery rather than company-operated message servers. The current repository is still missing the complete contact, send, receive, decrypt, and persistence path.
Is my data stored on a server?
The intended delivery layer stores encrypted messages as Base events. The current web client stores identity data locally and has no Harbor-operated message server, but real message persistence is not wired end to end.
Who can read my messages?
The protocol is designed so only intended recipients can read message contents. The current implementation has launch blockers in the integrated messaging path, so this should be treated as a target property rather than a completed product guarantee.
Can I use Harbor on multiple devices?
Not as a complete product flow yet. V1 enrollment functions exist and transfer encrypted identity private keys to the new device, but device certificates and complete multi-device delivery are not implemented.