Peter Surda
a69732f060
- addrthread is supposed to spread addresses as they appear. This was never finished during migration to asyncore - conservative to prevent flood and loops - randomises order - move protocol constants into a separate file - move addr packet creation into a separate file - see #1575 |
||
---|---|---|
build | ||
buildscripts | ||
desktop | ||
dev | ||
docs | ||
examples | ||
fabfile | ||
man | ||
packages | ||
src | ||
.gitignore | ||
.readthedocs.yml | ||
.travis.yml | ||
android_instruction.rst | ||
bandit.yml | ||
checkdeps.py | ||
configure | ||
COPYING | ||
Dockerfile | ||
INSTALL.md | ||
LICENSE | ||
MANIFEST.in | ||
PULL_REQUEST_TEMPLATE.md | ||
pybitmessage | ||
README.md | ||
requirements.txt | ||
setup.cfg | ||
setup.py |
PyBitmessage
Bitmessage is a P2P communication protocol used to send encrypted messages to another person or to many subscribers. It is decentralized and trustless, meaning that you need-not inherently trust any entities like root certificate authorities. It uses strong authentication, which means that the sender of a message cannot be spoofed. BM aims to hide metadata from passive eavesdroppers like those ongoing warrantless wiretapping programs. Hence the sender and receiver of Bitmessages stay anonymous.
Development
Bitmessage is a collaborative project. You are welcome to submit pull requests although if you plan to put a non-trivial amount of work into coding new features, it is recommended that you first describe your ideas in the separate issue.
Feel welcome to join chan "bitmessage", BM-2cWy7cvHoq3f1rYMerRJp8PT653jjSuEdY