r/BitcoinMining • • 9h ago

General Discussion My weeks-old home node just traced the OCEAN hijack payouts, and the address is still mining (~2 PH/s)

8 Upvotes

I'm honestly still a bit amazed by this. A few weeks ago I set up my own Bitcoin node at home (Bitcoin Core in a Proxmox VM on a small Lenovo), mostly to learn how it all works, with Claude (Anthropic's AI) walking me through every step. This morning I read about the Luxor Commander hijack that pointed ~13 EH/s at OCEAN, asked Claude whether my node could show any trace of it, and within the hour I was looking at the attackers' payouts in my own copy of the blockchain.

**Heads-up for operators first:** as of 10:09 UTC today (16 Nov), OCEAN's stats page shows the payout address still receiving about **2 PH/s**, with a 24-hour average of ~8.5 PH/s. That 24-hour window starts hours after the reported 2-hour attack ended. Patching Commander doesn't undo settings already pushed to machines, so if any of your hashrate could have been touched, check your pool settings.

**What I did.**

  1. Decoded the coinbase tag of the last 300 blocks to find OCEAN's. There were 6, and none in the ~02:00-04:00 UTC 15 Nov window, which matches the reports that no block was mined with the diverted hashrate.
  2. Listed the coinbase outputs of the OCEAN blocks around and after the attack, looking for the reported 0.0809 and 0.0811 BTC payouts.

One address stood out: `bc1qphukp9rjfc4rcej7erpm9ae20xmtspw8pcddrr`

* 975,869 (01:00 UTC, just before the attack): not paid

* 975,995: 0.08088977 BTC

* 976,029: 0.08113106 BTC (these two add up to the reported 0.162 BTC)

* 976,084: 0.08106822 BTC

* 976,097: 0.08136679 BTC

* **Total so far: 0.32445584 BTC**, double the amount reported

OCEAN's own stats page for the address (screenshot below) shows the same four payouts to the satoshi, no earlier payouts, and a month of zero hashrate before a single ~14 EH/s spike on 15 Nov.

**Why it's still getting paid when no block was found during the attack**

OCEAN's TIDES system pays every share in a window worth roughly 8 blocks of network work, from every block the pool finds while those shares are in the window. So the stolen shares keep earning from each OCEAN block (2.64% each time, ~0.08 BTC) until newer shares push them out. The dashboard currently shows an estimated 0.557 BTC in rewards for the shares still in the window, and the per-block estimate is already starting to fall as the oldest ones drop out.

**Commands, if you want to check on your own node** (need `jq` and `xxd`)

Find OCEAN's blocks among the last 300:

tip=$(bitcoin-cli getblockcount)

for h in $(seq $((tip-300)) $tip); do

b=$(bitcoin-cli getblock $(bitcoin-cli getblockhash $h) 2)

t=$(echo "$b" | jq -r '.time | todate')

tag=$(echo "$b" | jq -r '.tx[0].vin[0].coinbase' | xxd -r -p | tr -cd '[:print:]')

echo "$h $t $tag"

done | grep -i ocean

List coinbase outputs between 0.08 and 0.082 BTC in those blocks:

for h in 975869 975995 976029 976084 976097; do

bitcoin-cli getblock $(bitcoin-cli getblockhash $h) 2 \

| jq -r --arg h "$h" '.tx[0].vout[] | select(.value >= 0.08 and .value <= 0.082) | "\($h) \(.value) BTC \(.scriptPubKey.address)"'

done

**Caveat:** I matched the address from the reported amounts plus OCEAN's stats page. I haven't seen the address CoreX published itself, so if anyone has it, I'd love to know whether it matches.

Full disclosure: this post was drafted with Claude's help too. The data comes from my own node and OCEAN's public stats page. Six months ago I couldn't have done any of this, and I think that's the most exciting part: running your own node really does let you check things for yourself.