Reference client for Bitmessage: a P2P encrypted decentralised communication protocol:
Go to file
Daniel Kraft 810387df3e Read also rpcport from namecoin.conf.
Read also the rpcport setting from namecoin.conf when it is
available and use that as default when switching the setting
in the UI dialog.
2013-07-17 18:33:26 +02:00
archpackage python2-gevent is optional 2013-07-12 18:09:59 +01:00
debian manual merge 2013-07-14 16:35:16 -04:00
desktop Packaging for multiple distros 2013-07-12 10:36:28 +01:00
ebuildpackage Packaging for multiple distros 2013-07-12 10:36:28 +01:00
man Packaging for multiple distros 2013-07-12 10:36:28 +01:00
puppypackage Use python2 within /usr/bin/pybitmessage #296 2013-07-14 12:31:58 +01:00
rpmpackage Packaging for multiple distros 2013-07-12 10:36:28 +01:00
slackpackage Packaging for multiple distros 2013-07-12 10:36:28 +01:00
src Read also rpcport from namecoin.conf. 2013-07-17 18:33:26 +02:00
.gitignore Adding src/.settings/ to .gitignore (for Eclipse developers) 2013-06-23 21:17:34 +01:00
COPYING Debian packaging 2013-04-01 20:23:32 +01:00
LICENSE Debian packaging 2013-04-01 20:23:32 +01:00
Makefile Use python2 within /usr/bin/pybitmessage #296 2013-07-14 12:31:58 +01:00
README.md Debian packaging 2013-04-01 20:23:32 +01:00
arch.sh Some Arch dependencies 2013-07-12 14:03:11 +01:00
configure Packaging for multiple distros 2013-07-12 10:36:28 +01:00
debian.sh manual merge 2013-07-14 16:35:16 -04:00
ebuild.sh Packaging for multiple distros 2013-07-12 10:36:28 +01:00
generate.sh Use python2 within /usr/bin/pybitmessage #296 2013-07-14 12:31:58 +01:00
osx.sh Generated py for search. 2013-07-12 02:01:33 -04:00
puppy.sh Fixing the puppy script 2013-07-12 12:07:55 +01:00
rpm.sh Packaging for multiple distros 2013-07-12 10:36:28 +01:00
slack.sh Packaging for multiple distros 2013-07-12 10:36:28 +01:00

README.md

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.

references