Bitcoin Forum
April 25, 2024, 01:45:00 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 7 8 9 10 [11]  All
  Print  
Author Topic: BANK RUN! - P2P Fiat-Bitcoin Exchange  (Read 38985 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
jmw74
Full Member
***
Offline Offline

Activity: 236
Merit: 100


View Profile
April 25, 2014, 02:32:02 PM
 #201

Why the Bitmessage is no longer considered?

One thing is that it's python, which is not a big problem as with jython it should be not so hard to get it integrated into a java project, but a pure java solution would be more convenient. But that´s not the main reason...
I have not researched yet enough to discuss my skepticism regarding BitMessage in detail, but scalability, reliability and privacy are the areas where I am unsure. But as said, I need to investigate more to have a real opinion regarding those issues.

My impression of bitmessage is the same.  A nice first pass, or proof of concept. 

First major problem is that every node tries to decrypt every message on the network, this cannot scale.  In fact, just having every node get passed every message can't scale either, even if it doesn't have to try to decrypt them all (I'm sure the effort needed to test a message to see if it's "for me" can be reduced).

The other major problem is that if your node is offline for a while, you can permanently lose messages.  So you can't just integrate a bitmessage client into an app, the bitmessage process has to run continuously (or at least periodically).

And just in my casual use, it seems like the proof of work required by default is too small, I got spammed immediately.  That's not a major issue though.

I'm not an expert but there do seem to be better overall designs, but hard to say since they haven't been implemented.

1714052700
Hero Member
*
Offline Offline

Posts: 1714052700

View Profile Personal Message (Offline)

Ignore
1714052700
Reply with quote  #2

1714052700
Report to moderator
1714052700
Hero Member
*
Offline Offline

Posts: 1714052700

View Profile Personal Message (Offline)

Ignore
1714052700
Reply with quote  #2

1714052700
Report to moderator
1714052700
Hero Member
*
Offline Offline

Posts: 1714052700

View Profile Personal Message (Offline)

Ignore
1714052700
Reply with quote  #2

1714052700
Report to moderator
In order to achieve higher forum ranks, you need both activity points and merit points.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714052700
Hero Member
*
Offline Offline

Posts: 1714052700

View Profile Personal Message (Offline)

Ignore
1714052700
Reply with quote  #2

1714052700
Report to moderator
1714052700
Hero Member
*
Offline Offline

Posts: 1714052700

View Profile Personal Message (Offline)

Ignore
1714052700
Reply with quote  #2

1714052700
Report to moderator
Cryddit
Legendary
*
Offline Offline

Activity: 924
Merit: 1122


View Profile
April 25, 2014, 06:30:21 PM
 #202

You know, back in 2008 that was my response to Bitcoin itself. 

"Wait, every node is getting every message?  Can't scale..."

"Every node has to check encrypted signatures on every message?  Can't scale...."

Scale is still my biggest technical concern with Bitcoin, but when you actually figure out how much data you're talking about bitcoin scales fine.

jmw74
Full Member
***
Offline Offline

Activity: 236
Merit: 100


View Profile
April 25, 2014, 06:46:00 PM
 #203

You know, back in 2008 that was my response to Bitcoin itself. 

"Wait, every node is getting every message?  Can't scale..."

"Every node has to check encrypted signatures on every message?  Can't scale...."

Scale is still my biggest technical concern with Bitcoin, but when you actually figure out how much data you're talking about bitcoin scales fine.



Bitcoin is a lot closer to handling the whole world's transactions today than bitmessage is to handling the world's messaging. 

We can't wait for hardware to solve that, especially when (AFAIK) there are better algorithms that will vastly improve on bitmessage's efficiency.

In order to hide from the network which messages are for you, you do not need to accept all of them. 
puck2
Full Member
***
Offline Offline

Activity: 234
Merit: 105



View Profile
April 29, 2014, 04:14:33 PM
 #204

It seems that the whole "Tree Chain" conversation would be relevant here...  Huh
jmw74
Full Member
***
Offline Offline

Activity: 236
Merit: 100


View Profile
April 29, 2014, 06:51:33 PM
 #205

Why the Bitmessage is no longer considered?

One thing is that it's python, which is not a big problem as with jython it should be not so hard to get it integrated into a java project, but a pure java solution would be more convenient. But that´s not the main reason...
I have not researched yet enough to discuss my skepticism regarding BitMessage in detail, but scalability, reliability and privacy are the areas where I am unsure. But as said, I need to investigate more to have a real opinion regarding those issues.

My impression of bitmessage is the same.  A nice first pass, or proof of concept. 

First major problem is that every node tries to decrypt every message on the network, this cannot scale.  In fact, just having every node get passed every message can't scale either, even if it doesn't have to try to decrypt them all (I'm sure the effort needed to test a message to see if it's "for me" can be reduced).

The other major problem is that if your node is offline for a while, you can permanently lose messages.  So you can't just integrate a bitmessage client into an app, the bitmessage process has to run continuously (or at least periodically).

And just in my casual use, it seems like the proof of work required by default is too small, I got spammed immediately.  That's not a major issue though.

I'm not an expert but there do seem to be better overall designs, but hard to say since they haven't been implemented.

Now that I've read the bitmessage whitepaper more closely, it does seem like they do address scalability (to my satisfaction, anyway).  Currently all the nodes pass all the messages, but as it grows it will split up into a tree structure.

It does still kind of suck you can't just start your node and get your messages quickly (could take up to 2 days).  But I really don't have any suggestions for how to make it any better.
k99 (OP)
Sr. Member
****
Offline Offline

Activity: 346
Merit: 255

Manfred Karrer


View Profile WWW
June 10, 2014, 08:32:36 PM
 #206

I created a new thread with the updated resources: https://bitcointalk.org/index.php?topic=647457

https://bisq.network  |  GPG Key: 6A6B2C46
Pages: « 1 2 3 4 5 6 7 8 9 10 [11]  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!