BMLite – Lightweight client for
Bitmessaging
Vikram Reddy Pareddy
CSC8222 – Network Security
Georgia State University
Introduction
Problem:

NSA security fallout

How perfect is Https – centralized authority

How perfect is PGP/GPG – sender/receiver is
not encrypted

Proposed Solution:
Jonathan Warren's Bitmessage

Based on Satoshi Nakamoto's (a pseudonym of
a developer) Bitcoin concept
Bitcoins

Peer-to-peer network concept

Concepts: Transactions, Blocks, Proof-of-work

Transactions: The basic unit in Bitcoin concept
[Messages: The basic units in Bitmessage
concept]

Blocks: Makes sure that duplicates are not
created in the Bitcoin network

Proof-of-work – originated in HashCash by
Adam Back
HashCash

Proposed by Adam Back in March 1997

Protects the email system from Spamming and
Denial-of-Service attacks

This concept is extensively used in Bitmessage
Problem

In Bitmessage or Bitcoin system, the user has
to download the respective client into his
system

The first time download downloads all the
existing Bitmessages into the user's system

This is an issue because a naïve user may not
be comfortable to set it up
Solution

A web client that holds all the Bitmessage data

This web application is deployed on a server
which contains all the messages in the
Bitmessage network

A user logs into this system using his userID
and password and sends/receives messages
from this web client
Platform

The (hippie) development stack:
− AngularJS
− Node.js
− MongoDB
References

[Bitmessage: A Peer to Peer Message‐ ‐
Authentication and Delivery System by
Jonathan Warren]

Bitcoin Wiki
References

[Bitmessage: A Peer to Peer Message‐ ‐
Authentication and Delivery System by
Jonathan Warren]

Bitcoin Wiki

Proposal presentation

  • 1.
    BMLite – Lightweightclient for Bitmessaging Vikram Reddy Pareddy CSC8222 – Network Security Georgia State University
  • 2.
    Introduction Problem:  NSA security fallout  Howperfect is Https – centralized authority  How perfect is PGP/GPG – sender/receiver is not encrypted
  • 3.
     Proposed Solution: Jonathan Warren'sBitmessage  Based on Satoshi Nakamoto's (a pseudonym of a developer) Bitcoin concept
  • 4.
    Bitcoins  Peer-to-peer network concept  Concepts:Transactions, Blocks, Proof-of-work  Transactions: The basic unit in Bitcoin concept [Messages: The basic units in Bitmessage concept]  Blocks: Makes sure that duplicates are not created in the Bitcoin network  Proof-of-work – originated in HashCash by Adam Back
  • 5.
    HashCash  Proposed by AdamBack in March 1997  Protects the email system from Spamming and Denial-of-Service attacks  This concept is extensively used in Bitmessage
  • 6.
    Problem  In Bitmessage orBitcoin system, the user has to download the respective client into his system  The first time download downloads all the existing Bitmessages into the user's system  This is an issue because a naïve user may not be comfortable to set it up
  • 7.
    Solution  A web clientthat holds all the Bitmessage data  This web application is deployed on a server which contains all the messages in the Bitmessage network  A user logs into this system using his userID and password and sends/receives messages from this web client
  • 8.
    Platform  The (hippie) developmentstack: − AngularJS − Node.js − MongoDB
  • 9.
    References  [Bitmessage: A Peerto Peer Message‐ ‐ Authentication and Delivery System by Jonathan Warren]  Bitcoin Wiki
  • 10.
    References  [Bitmessage: A Peerto Peer Message‐ ‐ Authentication and Delivery System by Jonathan Warren]  Bitcoin Wiki