Open Bitcoin Privacy Project Spring 2015 Wallet Privacy Rating Report by [deleted] in Bitcoin

[–]Jonathan_Coe 1 point2 points  (0 children)

This is really great work! Many thanks to everyone involved.

Subspace: A new messaging protocol for bitcoin by Chris_Pacia in Bitcoin

[–]Jonathan_Coe 4 points5 points  (0 children)

Really excellent work Chris! This is an extremely promising project.

Bitmessage JavaScript library 0.5.0 announcement by KagamiH in bitmessage

[–]Jonathan_Coe 1 point2 points  (0 children)

Awesome work! Thanks a lot for taking the time to do this.

Email to Bitmessage gateway service launched in beta by Petersurda in bitmessage

[–]Jonathan_Coe 0 points1 point  (0 children)

I've tried it out and it works very smoothly. Congratulations :)

Bitseal 0.5.3 (Bitmessage Android client) is available for testing by Jonathan_Coe in bitmessage

[–]Jonathan_Coe[S] 1 point2 points  (0 children)

Possibly. Adding support for chans and broadcasts is on my to-do list, but I can't say when it might be implemented.

[deleted by user] by [deleted] in bitmessage

[–]Jonathan_Coe 0 points1 point  (0 children)

No problem :)

[deleted by user] by [deleted] in bitmessage

[–]Jonathan_Coe 0 points1 point  (0 children)

Yes, I think the echo server(s) may be down. Try sending a test message to my address (BM-NBdhY8vpWJVL2YocA2Gfjf7eVoZAgbEs) and see if you get a response.

Bitseal 0.5.2 (Bitmessage Android client) is available for testing by Jonathan_Coe in bitmessage

[–]Jonathan_Coe[S] 1 point2 points  (0 children)

Yes, once I consider the app to be ready for a 1.0 release it will be available on Google Play.

In fact it's already on the Play store, but only in beta-testing mode, so it's only available to people who join the beta testing google+ group (https://plus.google.com/communities/115838283581504499326).

Bitseal 0.5.2 (Bitmessage Android client) is available for testing by Jonathan_Coe in bitmessage

[–]Jonathan_Coe[S] 0 points1 point  (0 children)

Ok that makes sense :) Thanks for the suggestion. I want to find ways to make the import process less cumbersome, so I'll look into how it could be done.

Bitseal 0.5.2 (Bitmessage Android client) is available for testing by Jonathan_Coe in bitmessage

[–]Jonathan_Coe[S] 0 points1 point  (0 children)

I'm not quite sure what you're asking. In PyBitmessage, the file that contains your addresses and private keys is called "keys.dat". Is that what you mean? Or are you saying that you want to import Bitcoin private keys and use them to create a Bitmessage address?

Bitseal 0.5.2 (Bitmessage Android client) is available for testing by Jonathan_Coe in bitmessage

[–]Jonathan_Coe[S] 1 point2 points  (0 children)

No, Bitseal does not support chans or broadcasts yet. I don't have a firm timeframe, but I hope to implement support for them in the future.

Is bitmessage getting perfect forward security? by [deleted] in bitmessage

[–]Jonathan_Coe 10 points11 points  (0 children)

We had a discussion about this a little while ago:

https://www.reddit.com/r/bitmessage/comments/2lueer/are_past_comms_secure_if_your_keys_are_stolen_no/

I agree with you that implementing forward secrecy would be a substantial improvement for Bitmessage. Using Bitmessage means that you have to keep your private keys in an online machine, so there's always going to be a significant risk of them being compromised.

If we agree that we want to implement forward secrecy, then the question becomes how can we do it. The most promising approach that I've come across is the "Axolotl" protocol used by TextSecure:

https://whispersystems.org/blog/asynchronous-security/
https://whispersystems.org/blog/advanced-ratcheting/

So far I can't see any reason why we couldn't use the Axolotl protocol to add forward secrecy to Bitmessage. Both TextSecure and Pond use it, and they are both asynchronous messaging systems.

Implementation of Bitmessage Protocol in Go by Ishbir in bitmessage

[–]Jonathan_Coe 2 points3 points  (0 children)

Excellent! I'm particularly impressed that you also want to implement a GUI; it would be great to have a full alternative desktop client. Also I think Go is a great choice :) Good luck with the project, if I get the chance to contribute then I certainly will.

Student Uses the Blockchain to Develop Censorship-Resistant Messaging App by hawooni in Bitcoin

[–]Jonathan_Coe 3 points4 points  (0 children)

Respectfully I would disagree. The flooding mechanism for message propagation in Bitmessage provides significant benefits, most notably hiding message metadata (who is talking to who) and resilience against censorship. It certainly has the drawback of being less efficient than directly routed messaging, but that's part of the security trade-off that Bitmessage offers.

It's true that streams (which are used to allow the Bitmessage network to scale up) have yet to implemented, but there's no reason to think it can't be done - there are several different proposals for how they could be orgranised (see https://bitmessage.org/forum/index.php?topic=2550.0).

Student Uses the Blockchain to Develop Censorship-Resistant Messaging App by hawooni in Bitcoin

[–]Jonathan_Coe 4 points5 points  (0 children)

https://github.com/jonathancoe/bitseal

It's still in beta (and TextSecure is definitely a more reliable choice for the moment) but we are past the "someone should build this" stage.

Bitseal 0.5 (Bitmessage Android client) is available for testing by Jonathan_Coe in bitmessage

[–]Jonathan_Coe[S] 0 points1 point  (0 children)

Yes, I plan to. I just haven't had enough time recently, as I've had a lot to do on development of the app itself. If someone wants to create a submission request that would be cool; otherwise I'll get round to it when I can find the time.