After BIP110 failed I attempted to return to an earlier version of Knots and ended up loosing access to my Umbrel. I reinstalled Umbrel OS and Bitcoincore, I understand Knots will no longer be supported.
Since the Umbrel version of Datum requires Bitcoin Knots can another app like Stratum be used to point to Ocean.xyz?
You don’t need another Umbrel app if the goal is just to keep mining with OCEAN. Their non-BIP110 Stratum endpoint is back on mine.ocean.xyz:3334, so you can put this directly into the miner:
Pool URL: stratum+tcp://mine.ocean.xyz:3334
Username: your-bitcoin-address.optional-worker-name
Password: x
That uses OCEAN’s block templates instead of making your own through DATUM. OCEAN currently lists the regular pool fee as 2%, compared with 1% when using DATUM.
Upstream DATUM can talk to Bitcoin Core, but the Umbrel DATUM app is currently wired specifically to the Bitcoin Knots app. The Stratum V2 UI app isn’t a drop-in replacement here because OCEAN’s regular endpoint is Stratum V1.
Also, Knots is still available in the Umbrel App Store. The current package has a pre-RDTS v29.3.knots20260507 option under Settings → Bitcoin Knots Version, so using that with DATUM is still an option if you specifically want to make your own templates. Since you’ve already reinstalled and synced Bitcoin Core, pointing the miner directly to OCEAN is probably the simplest route.
Thank you!
I connected my Avalon Nano to Ocean then installed MinerSentinal. To my surprise it seems to be working. I used the Personal Pool option and Ocean’s pool URL. No pool stats yet, hasn’t been running for an hour yet.
That actually makes sense. MinerSentinel reads the Avalon Nano directly over its local API, so the miner stats can work with OCEAN regardless of which pool it’s using.
The pool stats are separate though. The current MinerSentinel app only knows how to fetch pool-side stats from CKPool or Public Pool’s HTTP APIs. OCEAN’s mine.ocean.xyz:3334 address is a Stratum endpoint, so putting it in the personal/custom pool field won’t make MinerSentinel’s pool stats populate.
I’d use MinerSentinel for the Nano’s local hashrate, temperature and accepted-share count, then use OCEAN’s My Stats page with your payout address for the pool-side numbers. Once the Avalon shows accepted shares, OCEAN should start showing the worker too.
Yes Aiden, you’re right. I’m doing the same and it’s working well.
I was glad to see Core put back the option to control the OPT_RETURN.
Thanks!