💬 Berty is a secure peer-to-peer messaging app that works with or without internet access, cellular data or trust in the network
Berty is an anonymous, secure, peer-to-peer protocol that doesn’t need an internet connection to function.
There is a protocol that uses advanced cryptography and a messenger app that is built on top of the protocol.
- No phone number or email required to create an account
- End-to-end encryption used to encrypt all conversations
- Focus on leaking as little metadata as possible
- Decentralized, distributed, serverless
- No consensus, no blockchain
- No internet connection required (uses the BLE technology and mDNS)
- Free forever, no data stored, transparent code, open-source
Berty is currently developed by Berty Technologies, a French non-profit organization.
- When you need to share sensitive information.
- If you want to communicate with good anonymity.
- If you don’t want to use servers, because you want full control of your data.
- In countries that have censorship and restrict network access and usage.
- In areas with weak or no connection or cell reception.
- When you travel and you want to communicate safely through insecure public connections.
Note: the project is made by a small team of humans who are not experts and who make mistakes. Please, do not hesitate to point out if you notice a bug or something missing. See the contribute section below.
We cannot promise to give you the best app, but we can commit to doing our best in that direction.
Berty is still under active development and should not be used to exchange important data.
The current Berty Messenger implementation is using the Berty Protocol. Which means the encryption is safe and it’s a P2P app! Berty Messenger has not been hardened yet so avoid using it on devices with weak sandboxes. If you’re trying to roll your own app based on the protocol, beware that the app layer protocols used by Berty Messenger might change in the future.
The current Berty Protocol is partially implemented. The API will certainly change in a near future, so be prepared to have breaking changes if you start using it right now.
We will open betas for the different packages and apps soon, so anyone will be able to give it a try even without the coding skills. Subscribe to our newsletter if you want to be notified.
Note: this is an ongoing work. The repos are being opened progressively, and there will be more changes and updates.
Under the hood
A generic SDK that allows developers to write P2P applications. It contains everything needed (encryption, identities, network routing, group management, account management, device management, application lifecycle) so you can just focus on the high-level features of your app.
go get -u berty.tech/berty/v2
Main items in the repo
- ./go: Where all the Golang code belongs.
- ./go/pkg/bertyprotocol: Berty Protocol Golang SDK to create secure and autonomous groups using IPFS.
- ./go/framework/bertybridge: gomobile entrypoint.
- ./go/cmd/berty: Main Berty CLI, containing:
berty daemon: Runs the whole Berty Protocol instance.
berty mini: Simple CLI messenger app using Berty Protocol.
- ./go/cmd/rdvp: A Rendez-Vous Point server.
- ./go/cmd/betabot: An onboarding bot used during the beta phase.
- The Berty Messenger application, written in React Native.
- ./docs: Mostly auto-generated documentation.
We want to contribute to the world of free, secure communication without fear of censorship and surveillance.
Open source is more secure, since anyone can examine the code, improve it and maintain it. Our ultimate goal is to completely lose control of Berty and have it evolve as a global community project.
More info on berty/community.
We really welcome contributions. Your input is the most precious material. We’re well aware of that and we thank you in advance. Everyone is encouraged to look at what they can do on their own scale; no effort is too small.
There are plenty of ways to get involved and act for our community. It has been divided into two distinct parts: everything that is related to the code and everything that is not.
To put it very simply: * Code-related = Github * Not code-related = Open task
Everything on contribution is sum up here: CONTRIBUTING.MD
Stargazers over time
- Official website: https://berty.tech
- Assets: https://assets.berty.tech/
- App assets & mockups: https://assets.berty.tech/categories/app__v2.4/
Take a look at our community repo.
See all our available contact methods on the contact page of our website.
© 2018-2020 Berty Technologies h0