Decentralized Email

From BiblePay Wiki
Jump to: navigation, search

BiblePay Decentralized SMTP E-mail is a novel feature that allows a user to send encrypted e-mails over the BiblePay network (eliminating the need for your ISP).

This means that in times of distress, as long as the biblepay network is up and functioning with TCP/IP, even if cloudflare, DNS, and cloud e-mail providers are down, you may successfully send an encrypted e-mail from one biblepay user to another through SMTP from your favorite e-mail client.

    There are many reasons why one would choose encrypted point to point e-mails over traditional plaintext emails:
  • Secure encrypted delivery means that it is impossible for anyone in the middle to eavesdrop on the e-mail content. Therefore it cannot be censored, leaked or suppressed, or targeted for ads. The message is encrypted with RSA. The decryption occurs on the recipients biblepay core client.
  • RSA over TCP-IP mechanism is theoretically more secure if you trust RSA more than HTTPS. Even if HTTPS is secure, you are still vulnerable to the point of encryption at a centralized location. For example some believe in centralized encrypted e-mail services, however you can only be assured privacy after the starting point on the centralized servers. If HTTPS is insecure then the entire process is insecure. RSA on the other hand is not known to have any vulnerabilities yet. The email is encrypted on your machine before it goes out to the biblepay network.
  • Once groups are formed, you can e-mail a group for tribulation updates. Think of how valuable this would be if you wanted to reach 5 family members and 5 camp members. In contrast to sending a plain vanilla email.
  • Email blasts for marketing: You can embed biblepay payments into the email for the recipients for a target promotional campaign. We will provide a mechanism to recoup the biblepay that is not claimed.

Features that work today:

The user record (accessed by clicking User Record from the QT Menu), allows you to store your Nick Name, Longitude, Latitude, Internal Email address and RSA Public Key. The Longitude and Latitude are optional and only used for the future tribulation map. The internal email address is your nickname plus @biblepay.core. When you first create a record, if you do not have an RSA keypair, biblepay will make one for you and save the public key in the chain. This will allow other people to e-mail you encrypted emails and chats.

Sending an Encrypted E-mail from One biblepay user to another BiblePay User by NickName

To do this you must first know the nickname of the other person. Go to your favorite e-mail client (such as Outlook or Firebird), and compose a new e-mail. Ensure the "From" selection is your [email protected] Make the e-mail To "[email protected]". Populate the subject and the body. We do support attachments, but we have a 1 megabyte limit on total e-mail size so please be sure to be below that. Once you click send, the e-mail will be encrypted with the recipients public key, and it will go out of the biblepay network in an encrypted format (that absolutely no one can read). Once your recipient comes online, their e-mail client will pick up the e-mail from biblepay. It is then decrypted with his-her private key when it is leaving biblepay core.

Where is my RSA Private Key stored?

Your RSA private key is stored in ~/.biblepay/SAN/privkey.priv. NOTE: If you delete your private key, you will lose access to all of your encrypted e-mails, unless they have been downloaded into your e-mail client. So please keep the key safe.

Features that are coming soon:

Ability to embed BiblePay funds inside an email.

Ability to embed MultiSig funds in an e-mail (this lets you recover the funds if they are not spent).

Ability to send a message to "ALL" (unencrypted). This allows for e-mail blasts, and for marketing blasts. A fee will be charged for these.

Encrypted Chat

You may also enter into encrypted chat with another user. Click "Chat | Private Message - Encrypted" and then enter the recipient username. If the user is at the machine while the ring occurs, you will enter into an encrypted chat dialog with the user.

How to set up my e-mail client with BiblePay ?

From Outlook, click Home | Account Settings | Create New Account. When asked "Exchange or IMAP/POP?" choose IMAP/POP.

For User Information, place your Nickname (or your preferred full name) in Your Name (this field is only used for E-mail content, not by biblepay validation or routing).

Email address must be Your Nickname + @biblepay.core.

For example, if your nickname is Santa, the e-mail address is [email protected] Account Type: Pop3. Incoming Mail server: The LAN address of your machine where biblepay core full node runs. Outgoing mail server: The LAN address of your machine where biblepay core full node runs.

Logon information: User name is your nickname. Password: Your user name (NOTE: See checkbox setting called AuthorizePayments). Click Test Account Settings to ensure they work then save the record.

SMTP Port Number: 30025

POP3 Port Number: 30110