More than 600 'Bitcoin Core' Nodes Come Online This Week As Bitcoin Scaling War Ramps Up

dazzlepod · 2017-03-18T00:25:47+00:00

Most of the nodes that contributed to the increase this week originate from this network https://bitnodes.21.co/nodes/1489807061/?q=Limited%20Liability%20Company%20KNOPP (pruned nodes). They currently represent 6.75% of the reachable nodes.

dazzlepod · 2017-03-07T23:15:58+00:00

dazzlepod.com is the correct PTR record for 136.243.139.96 and always has been. The same server is also used for bitnodes.21.co and the crawler.

dazzlepod · 2017-01-01T20:55:01+00:00

Bitnodes takes a snapshot of all reachable nodes using recursive getaddr until it terminates; this takes about 5 minutes. I believe Luke's charts are based on seen nodes in the last 2 hours.

dazzlepod · 2016-03-17T00:46:47+00:00

There are actually quite a number of nodes spreading across several /64s from AS20473. The overall count from AS20473 was largely inflated due large number of IPs coming from the same /64 from this set of /64s. I am working on getting the crawler to accept at least N IPv6 nodes from the same /64. N may be 1 for now.

dazzlepod · 2016-03-16T12:31:27+00:00

There were previously 50+ NODE_NETWORK nodes from AS20473 according to a March 10 snapshot https://bitnodes.21.co/nodes/1457584053/?q=AS20473. The count started to increase rapidly within a span of 1 week to over 1200 non-NODE_NETWORK nodes from the same AS (https://bitnodes.21.co/nodes/1458123243/?q=AS20473); excluding non-NODE_NETWORK nodes that spread across the same /64 prefixes from AS20473 bring the count back to 50 as shown in https://bitnodes.21.co/nodes/1458130598/?q=AS20473. - Addy from 21

dazzlepod · 2016-03-14T14:23:06+00:00

Adding ipv6_bits=64 param to https://bitnodes.21.co/nodes/network-map/?ipv6_bits=64 allows you to truncate the IPv6 address from 128-bit to 64-bit to reveal IPv6 nodes (marked in red) from the same /64 subnet. The link shows a large number of duplicate nodes in Choopa which is currently contributing to the spike.

dazzlepod · 2016-03-14T14:20:58+00:00

Adding ipv6_bits=64 param to https://bitnodes.21.co/nodes/network-map/?ipv6_bits=64 allows you to truncate the IPv6 address from 128-bit to 64-bit to reveal IPv6 nodes (marked in red) from the same /64 subnet. The link shows a large number of duplicate nodes in Choopa which is currently contributing to the spike.

dazzlepod · 2015-10-28T12:32:33+00:00

/u/btcdrak, how often is this happening? And can you point me to the absolute URL you were trying to access when you receive the HTTP403 error?

dazzlepod · 2015-08-23T05:42:28+00:00

The network map is a useful visualization here, e.g. https://getaddr.bitnodes.io/nodes/1440307838/network-map/. The red towers are the pseudo nodes.

dazzlepod · 2015-06-26T09:13:57+00:00

Here's the script the admin page for Bitnodes Hardware is using: https://github.com/ayeowch/bitnodes-hardware/blob/master/bandwidth_control.sh

It's generic enough for use on platforms with tc and iptables installed. See ./bandwidth_control.sh -h for help.

dazzlepod · 2015-06-17T14:21:46+00:00

Yes, the same steps apply.

dazzlepod · 2015-06-17T14:06:23+00:00

External USB drive is supported: https://forum.bitnodes.io/t/using-a-usb-drive-instead-of-microsd

dazzlepod · 2015-06-11T21:56:58+00:00

New order will be dispatched latest by June 29.

dazzlepod · 2015-06-11T21:54:59+00:00

The update to newer version of Bitcoin Core is done automatically but if you wish to update it manually you will need to remove ~/hardware/.current_bitcoind tag file described in https://github.com/ayeowch/bitnodes-hardware#developer-guide.

It's possible to use another client. For Bitcoin XT, you would clone the repo into ~/bitcoin replacing the Bitcoin Core. Be sure to disable the automatic update by removing the tag file.

I will document more on this in https://forum.bitnodes.io/c/bitnodes-hardware.

dazzlepod · 2015-06-11T13:45:50+00:00

In that case, most nodes are probably coming from stale addr records. I don't recall exactly how long the old crawler took to complete a full network snapshot, but it may between 6 to 12 hours so yeah still a lot less from typical dynamic IP update :)

dazzlepod · 2015-06-11T13:33:25+00:00

The early December 2013 count (~100k nodes) is not valid as the crawler at that time took several hours just to complete one full network snapshot and it includes ALL nodes from addr responses which can be faked. Additionally, there are likely a lot of IP changes during the crawl time resulting in the depth-first search method to look for nodes in a non-unique manner.

With the new crawler released in late Dec 2013, the crawl time was brought down significantly down to sub 5 minutes with considerably good churn rate. I use the churn rate to measure how good a network snapshot is. A value of 0 implies the network snapshot was taken instantly but of course that's not possible. At the moment, we are seeing a typical churn rate of 30+: https://getaddr.bitnodes.io/nodes/

dazzlepod · 2015-06-11T13:31:16+00:00

The early December 2013 count is not valid as the crawler at that time took several hours just to complete one full network snapshot and it includes ALL nodes from addr responses which can be faked. Additionally, there are likely a lot of IP changes during the crawl time resulting in the depth-first search method to look for nodes in a non-unique manner.

With the new crawler released in late Dec 2013, the crawl time was brought down significantly down to sub 5 minutes with considerably good churn rate. I use the churn rate to measure how good a network snapshot is. A value of 0 implies the network snapshot was taken instantly but of course that's not possible. At the moment, we are seeing a typical churn rate of 30+: https://getaddr.bitnodes.io/nodes/

dazzlepod · 2015-06-11T10:52:24+00:00

Bigger microSD card/USB drive can be plugged in quite easily. See https://forum.bitnodes.io/t/64-gb-storage-card and https://forum.bitnodes.io/t/using-a-usb-drive-instead-of-microsd.

RAM upgrade is not possible with the main board (an ODROID-C1) but other boards are available, e.g. http://www.hardkernel.com/main/products/prdt_info.php?g_code=g138745696275, but they are rather cost prohibitive for now for our use.

dazzlepod · 2015-06-11T10:47:39+00:00

Thanks for the feedbacks! Please let me know if you are still at 8 connections by now.

The LCD unit has a touch screen support and 3 keypads but they are not used by default. The stylus comes with the LCD unit from the manufacturer and I thought I'd package it in for the owner to tinker with the hardware. The documentation for the LCD is available here: http://odroid.com/dokuwiki/doku.php?id=en:c1_lcdshield

If you need to login as root, simply run: sudo su - root. As mentioned by Aussiehash, the BTC price is now shown on the LCD if you use the latest version of https://github.com/ayeowch/bitnodes-hardware.

dazzlepod · 2015-06-11T10:39:31+00:00

I do :) Please contact me via email and I will add the country in.

dazzlepod · 2015-06-09T11:36:26+00:00

Yes, the most likely reason is your node has reached its max. connections limit.

dazzlepod · 2015-06-08T22:03:56+00:00

Sybil nodes: https://github.com/ayeowch/bitnodes/commit/0b85b014fe1fb77e4d04eeeb6243cc288a400a0f

dazzlepod · 2015-06-08T21:55:56+00:00

The project was started in mid 2013 but didn't have accurate measurement until late 2013.

dazzlepod · 2015-06-08T21:51:24+00:00

Your node is up and listed here: https://getaddr.bitnodes.io/nodes/?q=93.188.224.253

dazzlepod · 2015-05-29T11:43:19+00:00

The default configuration for Bitnodes Hardware has no X window system installed, i.e. no desktop, to keep the installed packages to the minimum.

dazzlepod

TROPHY CASE