Yes, each rig gets a worker name and is tracked separately (for ranking which will inform future renting). It optionally integrates with HashGG (so it knows your stratum endpoint, and is auto-updated if you re-configure HashGG), but it also operates without it (you can put in any stratum endpoint). I currently have it connected in through HashGG configured with Playit.gg for this run.
1 Like
Next milestone reached. Autopilot auto-extended one rental, the other rental rejected the extension request, and it rented another to take its place (interestingly, the name looks like the same rig that rejected the extension 
) Short blip during ramp up and now back in business:
Auto-pilot rents rigs at min length (which is typically 3-hours), to reduce the impact of an underperforming rig and to potentially use that information when deciding whether to extend or to swap for a different rig. It requests an extension at 30 minutes before end, and if rejected it plans the next rental to minimize the ramp-down/ramp-up period.
2 Likes
Wow great job! I underestimated your abilities and getting a MVP so quickly! How’s the markup above hashprice on this platform vs Braiins?
1 Like
We’ll definitely add metrics for markup above hashprice (I haven’t compared it to Braiins yet). I also want to look into adding a visualization of percentage loss (or gain, if lucky) per session, if we can parse metrics from Ocean (still need to investigate that as well). Lots of ideas to improve on the application.
Getting back to the first live run, one issue has surfaced (this is why live production tests are important)
Looking at the telemetry, it looks like the sequence of events was:
- Two old rigs expired, and autopilot moved to refill my target of 400 TH/s.
- It rented a rig for 205 TH which never delivered a single hash (stuck 0%, now confirmed “offline”). Dead-weight spend of ~3,586 sats which should auto-dispute when the window opens.
- With that rig contributing 0, a ~91 TH gap remained. Autopilot made a mistake and tried to fill it by renting a 444.8 TH/s rig. It needed ~91 TH and bought 445!
That last step is obviously where the problem happened. The logic’s “greedy fill” is improperly ranking cheapest-first over best-fit. This can lead to a small top-up gap being filled by a large rig. This should be easy to fix. I’ll let the live run complete though to see if anything else interesting emerges.
1 Like
Hi guys, chiming in here. I was also somewhat dismayed at this Javier Hermosa’s dismissal of BIP 110 (though he stated it was his personal opinion, not of Braiins, but hey, companies are made up of people so if the head is against it I don’t hold high hopes). I like the idea of supporting other hashrate providers in Hashrate Autopilot. However, I just left for a trip and I’ll be on the road for about a month, and when I get back I will first have to focus on client projects. I don’t know when I will have time to dive deeper into this yes.
1 Like
No worries. Shanks has been helping a lot with the background details on MiningRigRentals, and I think with a little more work we can take the prototype for Pickhash to something solid. With a little polish, even the prototype itself is shippable as Beta software for folks to help test – just the one logic error to fix so far. It will give folks a user-friendly (non-KYC) alternative to Braiins Hashpower ahead of BIP-110 mandatory signaling.
This will all be a great source of information to build from when you get to adding MiningRigRentals as another provider in Hashrate Autopilot in the future. I might put in a PR for you to use as a reference point (though it will probably be after BIP-110 activates, since I have one more important thing to work on – Pickhash has been a slight detour..)
1 Like
Like you I favour consistent hash
Question: do we even know what miningrigrental’s stance on BIP110 is? Have they publicly said anything? Just want to make sure we aren’t just moving from one anti-BIP110 service to another. Even if they’ve said nothing about the topic, that’s also cause for concern.
1 Like
Something else I just found out about MRR: https://www.reddit.com/r/MoneroMining/comments/1skpb2x/proof_that_miningrigrentals_sellers_are_reselling/
Seems like people are reselling Nicehash and other hashrate providers for a markup and MRR has said this is allowed on their platform. Braiins has MRR blacklisted so it doesn’t seem like it’s possible for Hashpower to be directed to MRR. Just an FYI.
I suppose you are paying a bit of a premium for KYC removal in that case. Hopefully the direct rig owners are able to price the middle men out, but we’ll need to collect more metrics to see. My preliminary observation is that MRR is a bit more expensive to use than Braiins or Nicehash. I certainly wouldn’t fault anyone who wanted to stick with Braiins for that reason. Pickhash just provides optionality for those who decide it is worth it to boycott them.
3 Likes