Modified code so that clients send out their inventory lists with the the objects with the most proof of work first. The purpose is to ensure that a small minority of users contributing a relatively low amount of computational resources will not be able to DOS the network because their low proof of work messages are likely to be the last ones delivered and the first ones delayed past object expiration, as discussed here: https://bitmessage.org/forum/index.php?topic=4067.150 |
||
---|---|---|
archpackage | ||
debian | ||
desktop | ||
ebuildpackage | ||
man | ||
puppypackage | ||
rpmpackage | ||
slackpackage | ||
src | ||
.gitignore | ||
arch.sh | ||
configure | ||
COPYING | ||
debian.sh | ||
ebuild.sh | ||
generate.sh | ||
INSTALL.md | ||
LICENSE | ||
Makefile | ||
osx.sh | ||
puppy.sh | ||
README.md | ||
rpm.sh | ||
slack.sh |
PyBitmessage
Bitmessage is a P2P communications 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, and it aims to hide "non-content" data, like the sender and receiver of messages, from passive eavesdroppers like those running warrantless wiretapping programs.
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 solicit feedback on the DevTalk pseudo-mailing list: BM-2D9QKN4teYRvoq2fyzpiftPh9WP9qggtzh