From: Quinn Harris <btcdev@quinnharris•me>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Modularizing Bitcoin
Date: Sun, 19 May 2013 23:16:12 -0600 [thread overview]
Message-ID: <5199B19C.9020800@quinnharris.me> (raw)
In-Reply-To: <20130516100206.82680@gmx.com>
[-- Attachment #1: Type: text/plain, Size: 3289 bytes --]
Could this modularization effort lead to a special compiled bitcoind
simulator that runs many virtual instances of a node on the same system
(possibly same process)? The simulator would cache crypto computation
results (ECDSA, SSH-256) to significantly speed up processing
transactions and blocks between the virtual nodes. The virtual nodes
would also need to share the same block data in memory when possible.
This would also require significant additional work to simulate the
network and possibly computational limits.
The transactions on the existing block chain could be replayed into
randomly chosen virtual nodes to help ensure any code changes would not
have caused problems with historic transactions. You could even record
all the messages for some time on many real nodes and use that as test
data for the simulator. Many other test programs could be devised to
quickly simulate other network activity.
This wouldn't completely replace the test network but could provide
greater and quicker confidence that code changes are safe.
- Quinn
On 05/16/2013 04:02 AM, bitcoingrant@gmx•com wrote:
> 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>
>
>
>
>
> ------------------------------------------------------------------------------
> AlienVault Unified Security Management (USM) platform delivers complete
> security visibility with the essential security capabilities. Easily and
> efficiently configure, manage, and operate all of your security controls
> from a single console and one unified framework. Download a free trial.
> http://p.sf.net/sfu/alienvault_d2d
>
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
[-- Attachment #2: Type: text/html, Size: 9306 bytes --]
next prev parent reply other threads:[~2013-05-20 5:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2013-05-26 23:53 ` Luke-Jr
2013-05-16 10:48 bitcoingrant
2013-05-16 10:55 ` Addy Yeow
2013-05-26 23:57 ` Luke-Jr
2013-05-26 21:46 Ron
2013-05-27 2:57 Tamas Blummer
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=5199B19C.9020800@quinnharris.me \
--to=btcdev@quinnharris$(echo .)me \
--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