<p>Nevertheless: I wrote my previous article because I found there seems to be quite a bit of interest among
the plebs around renting hashrate, and so far I had not found much written about it beyond shit slinging
between knotzis and coretards. I'm writing this second part for the same reason, plus another specific
gap I've noticed. I see many plebs ask questions about how much money will you spend doing this, or what
amount of hashrate can you secure if you are willing to dedicate X sats per month to mining. And the
answers that come back are typically long rants on the different convoluted factors that influence the
answer. Not that those answers are wrong, for it is really a convoluted topic and it's hard to talk
specifics a priori. Hence why I want to write this article where I provide specific numbers on my
experience: so that it serves others as a very relatable and simple to understand report on how much
someone actually spent mining in a certain way. Hopefully it makes for a better data point to those who
find themselves on the fences of trying out.</p>
<p>The ultimate goal of it all is to spread knowledge, in the hopes people will be enlightened and motivated
by this and will take part instead of letting Foundry mine everything. My part will end here, and then
it's your turn to act.</p>
<p>I hope you find it interesting and useful. And I hope that, if you support BIP110, you'll roll your
sleeves and replicate this, adding the hashrate you can afford to the cause.</p>
<p>Now let's jump into the mud.</p>
<h3>Quick review of the system + how it performed</h3>
<p>I'm running Knots with the BIP110 patch, DATUM and hashbidder in a server I physically host myself. All
three services are hosted in a single VM. The DATUM endpoint is publicly reachable via a VPS I rent
(with sats), which then gets redirected to the DATUM process running in my server.</p>
<p>The uptime of this has been perfect. Any bit of downtime has been related to blips in my residential
networking or host downtime due to maintenance that is not related to the mining bit. None of the
Bitcoin/mining services have had any operational hiccup (hashbidder did stop working here and there, but
that was simply because I was always using the bleeding edge version and some bugs made it to
production). Resource consumption for this stack is a non-issue: stable and predictable, so the VM this
has been running on has had 99.86% uptime during the last couple of months.</p>
<p>I encountered a few small issues with Hashpower, but they were all trivial and didn't affect my
experience. The service has had a few outages of the API and web, yet as far as I can tell the actual
delivery of hashrate has been working constantly. If that failed at any time, it was brief enough to get
camouflaged as your usual hash delivery spikeyness.</p>
<p>I did face some issues with <ahref="https://hashpower.braiins.com/api/">Hashpower's API docs</a> being
incorrect: some endpoints behaved differently than what they advertised in the documentation. I got in
touch with their support in mid April and they told me they would address the issue. I checked while
writing the article and the issue is still unsolved.</p>
<p>Regarding rejected shares, I think the setup has worked out great. I just checked, and the datum dashboard
indicates I'm sitting at 0.06% (0.0006). I wouldn't be able to judge the quality of this rate myself, but
others more experienced in mining have assured me it's great, so I'll parrot back that it's great.</p>
<p>When it comes to bidding, I can assure you it has been quite optimal. I've taken whatever prices existed in Hashpower and never said "no, I won't mine now because XYZ price is too high". But I did a pretty decent job at staying as close as possible to the cheapest price being served. It is common to see bids that are 10%/20%/50% above market price in Hashpower. In my case, I'm pretty confident I must have stayed constantly between 0-5% of the cheapest bid. I can't show you the data to back it up, and won't go into the details, but hashbidder just does a good job of doing that. You can try for yourself and verify.</p>
<h3>Facts, figures, performance</h3>
<p>Okay, now let's show some serious data. Let's begin with how much I mined:</p>