When we started OCEAN, even before we picked OCEAN as a pool name, Jason was THE guy we knew we couldn't build it without. He has been instrumental in so many ways. Writing TIDES, writing DATUM, even picking the acronyms for both. When hurricane Helene briefly interrupted the back end in the early days, Jason was literally outside with a chainsaw chopping down trees so he could get out and physically fix the problem. And during that same hurricane, after he got OCEAN back up and running, he flew food and medical supplies in his personal plane to people who needed help. He is a remarkable human being. You will find few people more genuine than Jason. Truly a blessing to work alongside him. I am stoked for the future of OCEAN. Jason has many new tricks and innovations up his sleeve that the Bitcoin community will come to love and rely on in the years to come. Our future is very bright with Jason leading our technology.

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): nitter.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).