@ocean_mining bringing the money bags💰to @btchelevent. Come to our booth to find out how much more money you could be making with OCEAN.

Last year I wrote about a concept for pools and solo miners to reduce variance without the steep cost of FPPS. With our announced intent to open-source DATUM Prime early next year and collaborate with the SV2 community, this “DATUM Layer” idea is within reach.

Update on BIP110 reimbursements: The rebate we previously announced has now been paid at the best FPPS rate for the affected period. Transaction ID: 1f83d838b17b43b5504aa7823d6e89cf662ff0d261f4326041f741c9294d17eb Followup on BIP110 endpoint announcement: A clarification seems necessary about the announcement above, which some interpreted as the disclosure of some novel issue with hashrate distribution among the two competing chains during the recent BIP110 controversy and chain-split. It's not. The post is just a direct follow-up to the decision taken and publicly announced more than one month ago, about giving the few non-DATUM hashers (who still prefer to delegate block template creation to the pool operator, rather than taking control of it themselves, 4% of OCEAN’s hashrate) the same choice over BIP110 signaling as the DATUM miners (96% of OCEAN hashrate): xitter.cf/ocean_mining/status/20…. In that context, a choice was made to set the default Stratum endpoint to "pro-BIP". To be clear, this was not a statement of company advocacy for BIP110. At the time the decision was made, we were regularly hitting periods where more than 50% of OCEAN’s hashrate was actively signalling for BIP110, and we were fielding direct calls from customers telling us they were pro-BIP110 and asking how to signal. Setting the default accordingly was our attempt to have the endpoint at least resemble the expressed wishes of our own users at that moment. This choice of defaults was contested and somewhat controversial, but the main focus of the company was in giving all users a choice (which DATUM-wise was not a minor technical feat: some claimed it would have been impossible), and we were hopeful the number of users actually affected by the default would be minimal (even relative to the already small number of non-DATUM hashers). The way BIP110 unfolded confirmed this default choice as unfortunate, and the fact that some hashrate kept coming to that default endpoint, even after the BIP110 chain stalled out, seemed to corroborate that some hashers may have kept pointing to it due to a lack of information. That is why we processed the rebate above (some users who intentionally directed hashrate to the stalled chain may have also benefited from this, but our priority was to protect the uninformed ones).

DATUM restores miner sovereignty by letting miners choose how they build their own blocks. Power to the miners. 💪

.@Bitcoin_Lawyer closed out day 1 of @PlanBElsalvador in only a way a lawyer can with my favorite quote of the day: “You don’t want to do monthly AML/KYC on a space heater, you just don’t.” @ocean_mining is a permissionless mining pool. No account required. Plug it in and watch the sats flow. 🌊

Congrats @gzanganeh, @Bit__Gio and @tether on open sourcing Mining OS and the Mining SDK. Establishing an industry standard with a holistic view of the stack, from miners and transformers to pools, makes a lot of sense. Excited to see adoption grow, and looking forward to DATUM integration with MOS.

Booth upgrade complete. @LukeDashjr can now bilocate. @ocean_mining

"Emerging Best Pool to Watch: OCEAN" Appreciate the recognition @99BitcoinsHQ 99bitcoins.com/education/bit…

.@LukeDashjr absolutely crushing it in Dubai. @ocean_mining never sleeps, going to the ends of the earth to meet our miners where they’re at.

A friendly reminder that miners on @ocean_mining make more Bitcoin. $235k to $1.1M more per EH per year, according to our miners. Interested to learn more? Let's chat.