From: Ron <rdwnj@yahoo•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Modularizing Bitcoin
Date: Sun, 26 May 2013 14:46:32 -0700 (PDT) [thread overview]
Message-ID: <1369604792.77530.YahooMailClassic@web124503.mail.ne1.yahoo.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3086 bytes --]
From: <bitcoingrant@gm•..> - 2013-05-16 10:02
One of the primary upcoming priorities for bitcoin’s infrastructure, beyond the bloom filter, will be the continued modularization of the system.
Here at the Bitcoin Grant, we would like to jump start this development with a financial incentive and initiate an ongoing conversation on how we can work together towards developing a smarter, more efficient system of tomorrow, today.
Up for grabs: 500 bitcoins or $500,000; whichever is greater.
Taking on a project of this scope is a highly intensive, technical undertaking and we believe excellent developers should be compensated as such, especially when it comes to open source projects.
One of the main goals will be to separate the wallet from the node, as we have already done with mining. This way, the wallet, which will only hold private keys and create transactions, would pass transactions directly to a relay node, based on the bloom filter. Meanwhile, the block node will maintain the block chain and validate and relay new blocks.
Such developments would significantly strengthen the system. Modularization would make cancer attacks less likely and increase the node count, which, currently, is fairly low.
This is by no means is a feature request, merely ideas as to initiate a discussion. We welcome any feedback or suggestions. And of course, let us know if you would like to contribute to this project by submiting a grant proposal.
http://bitcoingrant.org http://bitcoingrant.org/&lang=en
Hello
I don't know if this is the proper method of replying or even if
I am allowed to reply!
Modularization can have many meanings, depending upon one's past!
The code is somewhat compartmentalized/modularized now. But if one
forces complete separation of the parts, with a 'loose coupling',
etc., I find that the performance tends to suffer and the size
increases.
In the Java world there is the notion of refactoring one's code.
This would be too much, I think, in this case. When I developed
with a team and alone, I would make what used to be called
'step-wise refinements' on existing working code. To me, one of
things this meant was doing a one to one transformation of the
source code, in such a way as to have the identical, byte for
byte, executable file, but a 'better' set of source files. A
similar process would seem appropriate here. Especially since
there is much in the code that I don't understand :)
As to 'separating the wallet from the node', do you mean allowing
the wallet.dat file to be anywhere, and not restricted to the 'OS default'
or 'datadir' directory? If so, I have done that with no change to the
current behavior, and also the wallet.dat now can have any legal
filename too! I haven't tested it yet on bitcoin-qt, but it runs
on bitcoind. I am still 'ramping up' on github to get the code into
view. After testing on bitcoin-qt of course.
What may I ask, is a cancer attack?
If any of this inappropriate, forgive me.
Ron
[-- Attachment #2: Type: text/html, Size: 4785 bytes --]
next reply other threads:[~2013-05-26 21:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-26 21:46 Ron [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-27 2:57 Tamas Blummer
2013-05-16 10:48 bitcoingrant
2013-05-16 10:55 ` Addy Yeow
2013-05-26 23:57 ` Luke-Jr
2013-05-16 10:02 bitcoingrant
2013-05-16 10:27 ` Addy Yeow
2013-05-16 16:43 ` Brenton Camac
2013-05-16 19:35 ` Mike Hearn
2013-05-20 5:16 ` Quinn Harris
2013-05-26 23:53 ` Luke-Jr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1369604792.77530.YahooMailClassic@web124503.mail.ne1.yahoo.com \
--to=rdwnj@yahoo$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox