 Show Posts
|
|
Pages: [1] 2 »
|
The early December 2013 network snapshots, i.e. with over 100k nodes, are 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 or likely stale. Those snapshots were linked to from getaddr.bitnodes.io/SNAPSHOT_NUMBER/ which have been removed since. 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/ |
|
|
|
Hm, not shipping in my country, that sucks  Send me an email and I will check if registered post is available for your country. Registered post requires only signature on delivery without tracking. |
|
|
|
Hey "disclosure" a.k.a. Addy Yeow!
Could you please add deregistration to your site? Or maybe some form of automatic decay, so that nodes inaccessible for over a month get dropped from your scanner?
I rather thoughtlessly registered several of my test nodes and I wanted to move them to a better, more permanent addresses. It was easy to press "ADD" before thinking it through. Some sort of verification similar to your incentive registration should be a good and safe deregistration.
Thanks.
Edit: Fixed spelling of the first name.
Done. Node will now be removed automatically from the site if it is down for more than a week. |
|
|
|
i must have this, when does it ship?
I have started to ship since yesterday (Friday AEST). However, due to the current backlog, new orders are now scheduled for dispatch latest by June 22. |
|
|
|
Definitely seems nice with the dashboard and the nice display, but I can get a quad-core 900MHz processor over this quad-core 600MHz processor as well as the same 1GB SDRAM from a Raspberry Pi 2 for only $35. You're paying a lot for aesthetics there...I guess for people who aren't too fussed about saving cash and want something that's much easier to setup this is good, though.
The ODROID-C1 base board is priced at $35 as well. You are not paying anything for aesthetics for Bitnodes Hardware as most of the cost goes to the 8GB eMMC and 64GB microSD. |
|
|
|
Does someone knows if a static IP address is required for participation or it will work with a dynamic IP address?
The PIX value documented in https://getaddr.bitnodes.io/nodes/leaderboard/#peer-index considers weekly latency as well. If you are behind dynamic IP, you may not stay on the same IP for a week hence limiting the PIX value that your node can reach. |
|
|
|
And another winner, 104.7.88.191 this time.
Edit: btw are there any details how the node is picked? Is it weighted by PIX are nodes that allready received an incentive removed from the list?
A node is picked randomly from a pool of eligible nodes, so a selected node may be selected again in the future. |
|
|
|
|
SSL-enabled URL with unverified cert is supported. Feel free to contact me directly using the contact link at the footer of the website.
|
|
|
|
For the Bitnodes project ( https://getaddr.bitnodes.io), I am using only 1 instance of the crawler which connect/disconnect from reachable nodes periodically. This should be sufficient to aggregate network metrics. Running more than 1 instance and taking up connection slots from peers will reduce the number of available open slots for actual peers to connect to. There are only 125 open slots available per node unless of course if you have configured it manually with maxconnections option in bitcoind.conf. |
|
|
|
|
Does anyone know about the Bitnodes crawlers from these addresses:
54.173.72.127 (ec2-54-173-72-127.compute-1.amazonaws.com)
54.183.64.54 (ec2-54-183-64-54.us-west-1.compute.amazonaws.com)
54.194.231.211 (ec2-54-194-231-211.eu-west-1.compute.amazonaws.com)
54.66.214.167 (ec2-54-66-214-167.ap-southeast-2.compute.amazonaws.com)
54.67.33.14 (ec2-54-67-33-14.us-west-1.compute.amazonaws.com)
54.77.251.214 (ec2-54-77-251-214.eu-west-1.compute.amazonaws.com)
54.94.195.96 (ec2-54-94-195-96.sa-east-1.compute.amazonaws.com)
54.94.200.247 (ec2-54-94-200-247.sa-east-1.compute.amazonaws.com)
They appear to have started around the same time so they may be operated by the same owner. If you are the owner of these crawlers, please consider running only one instance of the crawler to avoid taking up the available connection slots on each node.
|
|
|
|
They don't respond to ping either. I dropped them from Bitnodes crawler ( https://github.com/ayeowch/bitnodes/blob/master/crawl.conf#L46) as they don't seem to be contributing to the network. The nodes are hosted by OVH and they give you free /24 IP block when you subscribe with them. So, it is likely that the nodes from 46.105.210.* are operated by the same owner. |
|
|
|
|
Bitnodes crawler finds only the reachable nodes in the network, i.e. nodes that accept incoming connections.
|
|
|
|
An interactive visualization of all reachable nodes in the Bitcoin network is now available from https://getaddr.bitnodes.io/nodes/network-map/. The nodes are grouped by ASN. Each ASN is allocated a 64 by 64 square on x-z plane with its y axis from 0 to 160. Each node has a (x,y,z) point relative to its ASN based on its 32-bit (IPv4) or 128-bit (IPv6) IP address in integer value. ASNs are populated from inner to outer layer of the grid according to the number of nodes in descending order. Click on the colored circle to filter nodes by state or a square to highlight nodes in the ASN.  |
|
|
|
1) Go to https://getaddr.bitnodes.io/. 2) Click on the count to access the list of reachable nodes. 3) Search for your node and click on it to activate its status page. 4) Add a contact information to receive an alert when your node goes down or becomes unreachable. |
|
|
|
Ryan Zhou has abandoned NameTerrific ( https://www.nameterrific.com) apparently since late 2013. He no longer attend to any support request sent to NameTerrific. Neither is he responding to emails sent to him separately in regards to NameTerrific. See reports from other users here: 1) http://forums.whirlpool.net.au/archive/22169392) https://www.facebook.com/nameterrific3) https://twitter.com/search?q=nameterrificOne of my domains is registered with NameTerrific as well and I haven't been able to transfer my domain out to a proper registrar as NameTerrific does not respond to my auth code request. I had previously registered my domain with NameTerrific as he accepts bitcoins. Do not consider registering your domain with NameTerrific. You have been warned. |
|
|
|
|
