Update for OCEAN miners:
We want to clarify yesterday’s activity around the BIP-110 and non-BIP-110 mining options.
For roughly 18 hours, some miners using OCEAN’s Stratum templates may have believed they were mining on the non-BIP-110 chain while their hashrate was directed to the BIP-110 chain.
To eliminate any possibility that miners were disadvantaged, OCEAN will make a direct Bitcoin rebate payment to affected miners based on the rewards they would have earned on the non-BIP-110 chain during that window.
Approximately 0.3 BTC will be distributed, with payments completed within the next 72 hours.
We’ll publish the transaction details once the payments are sent.
The default endpoint is now back on the non-BIP-110 chain. Both options remain available so every miner can choose where to direct their hashrate.
Your hash. Your choice.
Isn't the whole point of OCEAN supporting DATUM to let miners control what they're actually mining?
told ya
i'm glad this got resolved. I was wondering what happened with it.
Same here. I am also glad it’s resolved, but still curious how that “accident” happened in the first place. 👀
Given Luke position on BIP-110, this is certainly an interesting “accident” 👀
It's a breach of trust, but then... I didn't see anyone else actually checking what they were mining, and I am not even mining.
Dont. Trust.
Yesterday I noticed my hash rate had diminished severely. I assumed some of my little miners were off line. When I checked they were all running normally. It was a puzzle to me. I figured it was a BIP-110 problem, but I don't even run datum, so I was confused. Late in the afternoon everything returned to normal. Is it realistic to assume I got hijacked?
I thought you turned them off so I didn't tag you when I found that the default pool was being rerouted. It looked like they were flip flopping between chaintips in the beginning, then they chose the main tip for a few hours, then it switched to BIP-110 for a longer time, then back to the main tip. From a pool perspective, the only moment to defend the 110 chaintip was when they were of equal length. But once it moved past the split, it should have stayed on the main tip. Deviations from that were likely interference, so if you're on Ocean's default pool, you definitely got swapped around.
I don't know enough about how share difficulty targeting works on ocean's stratum (and datum) backend software, because that stack is closed source. What could have happened is that you got too high share difficulty with each tip reset and then needed time with adjusting, but that is me guessing, based on how I've seen Ocean do share difficulty adjustments a little under 2 years ago when I tested it with a bitaxe.
Once the BIP went live Ocean posted monitoring for both chains. Eventually I thought it was safe to jump back in. I guess I was a little early. 😀
They must be really happy right now that siggy didn't find a BIP-110 block while they were capturing hashes, because they would have owed you a lot more haha
That's why I don't solo mine. I'm not that lucky 😀
They changed their ToS a few days before too https://x.com/sashahodler/status/2086830294045196755?s=20
https://twiiit.com/sashahodler/status/2086830294045196755
Maybe ocean should support only datum and remove the stratum endpoint.