Announcing the newest Bitcoin infrastructure node, or why Ethereum is so utterly fucked.

First things first, and I should hope that this goes without saying in 2018, but you really can’t have too many trusted, reliable, high-uptimei nodes on any peer-to-peer network, and Bitcoin is no exception. It’s sorta why “decentralise” was a meme back in 2013 before “blockchain” took over the lamestream news in 2015.

Anyways, that’s why I’m announcing Constantine IIii today, to be found at 158.69.54.79.iii The newest infrastructure node on the Bitcoin network – here to serve.
___ ___ ___

  1. If you’re employing dedicated servers from ISPs, as I am, it’s not even enough that your service provider keeps the lights on, the A/C running, and all the cords plugged in. Running Bitcoin nodes still takes a serious amount of babysitting because even the almighty TRB software is a ball of wet hair that dies for no reason, requiring semi-regular restarts and fairly absurd levels of vigilance. Running more than two nodes is quite the responsibility. Running five or even ten requires discipline and organisation, to say nothing of the financial commitment. []
  2. Constantine II’s predecessor, Constantine I, is still to be found at 37.59.43.190, but with the blockchain growing at upwards of 1*6*24*365 = 52.56 GB per year, he only has about 9 months to live before his 250 GB SSDs are obsoleted (optimistically 12-15 months with these baby blocks).

    When I was a tyke, the blockchain was only 20 GB and you could run a node on a MacBook… Time rests for no man, nor machine, but Good God was that five years well spent.

    All of which brings us neatly to Ethereum and this little doozy of an inconvenient truth, brought to us by Dan The Man :

    Bitcoin vs Ethereum blockchain sizes

    Although the percentage and Mb changes are somewhat arbitrarily based on when Dan turned on the metre, the controlled and predictable growth of the Bitcoin blockchain is even still starkly contrasted against the explosive and frequently manic growth of the Ethereum blockchain. In the 9.5 years that Bitcoin has been fucking shit up, its blockchain hasn’t even crested 200 GB in total size compared to the 675 GB accumulated by the metastatic Ethereum in just 2.5 years.

    As we can see, while Bitcoin will outgrow 250 GB SSDs that retail for $120 by the end of 2018, Ethereum is about to outgrow 1 TB SSDs that retail for $369 by Thanksgiving 2018 before maxing out 2 TB SSDs that retail for $770 by summer solstice 2019 and then 4 TB SSDs that retail for $1`700 by mid-2022 if the rate of growth doesn’t increase further still. Do you know how few users can afford that kind of investment ? Do you understand the compromises inherent in “sharting” that are being proposed to deal with it ? You should recognise the parallels between Vitalik’s latest hail mary and the failed MaidSafe enterprise, at the very least. Because maybe broken ideas will work for us! We’re special!!1

    But hey, no one said mass adoption would be easy, or lead to anything other than the exact same centralised fiat bullshit world that supposedly keeps you safe and warm at night, where all of your financial transactions are mediated and monitored through “regulated” and “chartered” middle-men using a currency WITH NO FUCKING CAP!!!11! It’s what Anthony di Iorio and his little puppet have always wanted – to rent you out to the highest bidder like the slave you are (archived). Pretty gross eh ? []

  3. As you’ll surely have noticed from the listing on the right sidebar, my other other infrastructure node, Shadchan, can still be found at 199.204.187.186, but it too is doomed to be replaced within the year. UPDATE 30/05/18 : RIP Old Boy. We’ll see if Pizarro is looking solid enough to host Shadchan II by then. Given the little exit scam that ZXPlay / ZXHost just pulled on me, I’m eager to try more trustworthy solutions. []

11 thoughts on “Announcing the newest Bitcoin infrastructure node, or why Ethereum is so utterly fucked.

  1. BingoBoingo says:

    Salud! It seems that only Shadchan out of your node pool is accepting inbound connections.

    Building bitcoind up to one of the sync aggression patches tends to result in much less tempermental behavior.

    • Haven’t tried the latest patch set but I’ll definitely give ‘em a go soon. Weird that the Contantines aren’t accepting new connex… must be the Easter holidays in byzantine node-land.

      Unless I accidentally IP banned your boy, what IP(s) are you trying from ?

    • Upon further investigation, Contantine I is being blackholed à la connect/disconnect and will hopefully be back to normal shortly.. Constantine II looks fine from this end.

    • BingoBoingo says:

      I’ve tried from a few IPs. I strongly suspect moving to a trb which is more finely flensed would help with your nodes’ connectivity issues.

    • The whole team is back and in top working order now. Thanks for being the proverbial alert reader.

    • BingoBoingo says:

      No problem at all, can confirm peering:

      {
      “addr” : “158.69.54.79:8333″,
      “services” : “00000001”,
      “lastsend” : 1522801544,
      “lastrecv” : 1522801542,
      “conntime” : 1522696470,
      “version” : 50402,
      “subver” : “/therealbitcoin.org:0.5.4.2/”,
      “inbound” : false,
      “releasetime” : 0,
      “startingheight” : 516330,
      “banscore” : 0
      },

  2. > Running Bitcoin nodes still takes a serious amount of babysitting because even the almighty TRB software is a ball of wet hair that dies for no reason, requiring semi-regular restarts and fairly absurd levels of vigilance

    Nope and… nope — “zoolag” ( 108.31.170.49 ) runs unattended for year+ at a time, with zero OOM, and — since “aggression” patch — never falls irrecoverably behind or otherwise “asks for” reset.

    • I suppose that zoolag’s reliability, just as my experience with various dediboxes and their varying degrees of unreliability, could be related to factors other than TRB itself, so perhaps it’s unfair for me to point the finger there alone. That being said, my experience was my experience and babysitting pre-“aggression” was an undeniable part of node maintenance.

      Anyways, “aggression” is now being tested in Constantine II. I guess I’m optimistic.

  3. […] world of the truly sovereign individual, like it or not. It’s a world of toxically powerful new technologies, many of which will explode in your hands if you’re not careful, intelligent, […]

  4. […] 2018/04/22 : With 250GB SSDs nearing the end of their capacities, it’s time to upgrade to 500GB non-rust-spinners! That means we’re in the range of USD […]

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>