I believe the requests Jeff is seeing came from my crawler although anyone
could be running it (https://github.com/ayeowch/bitnodes) since there is no
IP address in the log to confirm the source of the requests.
This is a sample log of an actual request from my crawler at 148.251.238.178
:
Hi Mike,
That was because I had to restart the crawler for update. This disconnects
the crawler from all reachable nodes temporarily and it will take about 15
minutes (3 snapshots) before the crawler stabilize again. I will look into
annotating these drops with a note.
Cheers,
Addy
On Thu, Mar
. Thanks for doing
that. If you're in the mood for extending it, it'd be great to gather and
chart data on block and tx propagation times.
Do you think the recent explosion in running nodes is real, or due to some
kind of custom experimental thing?
On Thu, Nov 21, 2013 at 2:55 PM, Addy Yeow
I personally don't treat the relay field as optional, i.e. it is there as
0x01 if it is set. Otherwise, it is simply a trailing zero byte. Hence, the
right way of reading the packet as with any network packet is to first
retrieve the header information, get the actual payload length, then parse
.
On Thu, May 16, 2013 at 8:48 PM, bitcoingr...@gmx.com wrote:
our estimates: ~8000
- Original Message -
From: Addy Yeow
Sent: 05/16/13 06:27 AM
To: bitcoingr...@gmx.com
Subject: Re: [Bitcoin-development] Modularizing Bitcoin
Such developments would significantly strengthen
Hi list,
Can someone explain why do we have 32-bit and 64-bit timestamp fields
instead of all being 64-bit?
https://en.bitcoin.it/wiki/Protocol_specification
Cheers,
Addy
--
Learn Graph Databases - Download FREE
From https://en.bitcoin.it/wiki/Protocol_specification#version, is the
relay field (bool/1 byte) required in all version packets coming from
client with protocol version = 70001?
--
Introducing AppDynamics Lite, a free
7 matches
Mail list logo
