From: Kyle Jerviss <kjj@jerviss•org>
To: Christophe Biocca <christophe.biocca@gmail•com>,
Bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] we can all relax now
Date: Wed, 06 Nov 2013 23:24:48 -0600 [thread overview]
Message-ID: <527B2420.6030603@jerviss.org> (raw)
In-Reply-To: <CANOOu=-MsPPgACKcHvsvtFAOAiULL+BOQvJz1tC3L=nT8wN01Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 5059 bytes --]
What I want is configurable 1/10/100 millisecond ticks, and accurate
flow of information.
It doesn't seem necessary to really emulate the whole protocol, nor to
be overly concerned with the content of messages, nor to simulate every
little housekeeping step or network message.
I'm not looking for a bitcoin-network-in-a-bottle, I just want to see
flows. In the current situation, how often does a miner win if they
hold their block until they see another one? How does that change with
various numbers of remote sensors?
Other applications in the future could very well involve transaction
spread, double spends, network partitions, transaction replacement, etc.
If the simulation run in question involves blocks, I'd like realistic
latencies for blocks. If it is about transactions, the latencies should
be realistic for transactions.
What is realistic for those? That brings me to...
I'll kick in another 1 BTC for an instrumentation package for the
reference client. Same conditions as before. A runtime option,
disabled by default, that collects data for the simulator. If this
creates an uproar, I'll also accept a compile-time option. Support
dumping to a file that can be uploaded to a parser as the bare minimum,
and if you are feeling clever, add automatic uploads to a server
specified in the conf file, or whatever. All data should be anonymous,
of course. Local file should be in a format that humans can read (JSON,
XML, CSV, etc) so that people can verify that the data is indeed anonymous.
I want stats on peers (number, turnover, latency, in/out, etc), stats on
local operations (I/O stats, sigs per second when verifying a block,
fraction of sig cache hits when validating, etc) and whatever else might
be useful to a simulator. Each parameter should collect min, max, mean,
std. deviation, etc so that the simulator can provide realistic virtual
nodes.
Also, I don't want anyone to think that they need to satisfy me
personally to collect on either of these two bounties. I will pay mine
for a product that is generally along the lines I have laid out, if a
couple of the core devs (Gavin, Greg, Jeff, sipa, Luke, etc) agree that
your work is useful.
Christophe Biocca wrote:
>
> I might try building this sometime soon. I think it may also serve an
> educational purpose when trying to understand the whole network's
> behaviour.
>
> What level of accuracy are we looking for though? Obviously we need to
> fully emulate the steps of the network protocol, and we need to be
> able to specify time taken for transmission/processing for each node.
> Do we care about the actual contents of the messages (to be able to
> simulate double spend attempts, invalid transactions and blocks, SPV
> node communication), and their validation (actual signatures and proof
> of work)?
>
> I imagine the latter is pretty useless, beyond specifying that the
> signature/proof of work is valid/invalid.
>
> If we could build up a set of experiments we'd like to run on it, it
> would help clarify what's needed.
>
> Off the top of my head:
>
> - Peter Todd's miner strategy of sending blocks to only 51% of the
> hashpower.
> - Various network split conditions, and how aware of the split nodes
> would be (and the effect of client variability).
> - Testing the feasability of network race double spends, or Finney
> attacks.
> - Various network partition scenarios.
> - Tricking SPV nodes.
>
> On Nov 6, 2013 6:37 AM, "Jeff Garzik" <jgarzik@bitpay•com
> <mailto:jgarzik@bitpay•com>> wrote:
>
> I will contribute 1 BTC to this bounty, under same terms and
> expiration.
>
>
> ------------------------------------------------------------------------------
> November Webinars for C, C++, Fortran Developers
> Accelerate application performance with scalable programming
> models. Explore
> techniques for threading, error checking, porting, and tuning. Get
> the most
> from the latest Intel processors and coprocessors. See abstracts
> and register
> http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> <mailto:Bitcoin-development@lists•sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
>
> ------------------------------------------------------------------------------
> November Webinars for C, C++, Fortran Developers
> Accelerate application performance with scalable programming models. Explore
> techniques for threading, error checking, porting, and tuning. Get the most
> from the latest Intel processors and coprocessors. See abstracts and register
> http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
[-- Attachment #2: Type: text/html, Size: 7426 bytes --]
next prev parent reply other threads:[~2013-11-07 5:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 5:33 kjj
2013-11-06 9:26 ` Frank F
2013-11-06 11:35 ` Jeff Garzik
2013-11-06 18:06 ` Christophe Biocca
2013-11-07 3:44 ` Peter Todd
2013-11-07 4:15 ` Kyle Jerviss
2013-11-07 4:33 ` Peter Todd
2013-11-07 4:59 ` Kyle Jerviss
2013-11-07 13:09 ` Peter Todd
2013-11-07 4:56 ` Gavin Andresen
2013-11-07 13:24 ` Peter Todd
2013-11-07 16:14 ` Mike Hearn
2013-11-07 18:28 ` Daniel Lidstrom
2013-11-08 19:49 ` Andreas M. Antonopoulos
2013-11-08 20:33 ` Gregory Maxwell
2013-11-15 10:58 ` Peter Todd
2013-11-07 8:07 ` Jannes Faber
2013-11-07 5:24 ` Kyle Jerviss [this message]
2013-11-06 18:17 ` Melvin Carvalho
2013-11-06 22:19 ` Jouke Hofman
2014-05-10 11:05 ` E willbefull
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=527B2420.6030603@jerviss.org \
--to=kjj@jerviss$(echo .)org \
--cc=Bitcoin-development@lists$(echo .)sourceforge.net \
--cc=christophe.biocca@gmail$(echo .)com \
/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