Good newsm fix is shipped and live 🎉 The marketplace was prepending a BTC address to your worker, which broke Hashden's routing. It now strips that automatically, so DirectHash hashpower attributes to the den with no change on your end. Tested end-to-end and rented hashpower is landing now. Just re-run your order and ping me, I'll confirm shares are coming through 🤙

I'll add a parse on my side to drop the btc address if it is automatically added.

I rented some hashpower on DirectHash myself and reproduced it, so I can tell you exactly what's going on 🙏 Good part first: you joined genesis-den correctly, your npub's registered with both a BTC and Lightning payout address, and the den's recording shares fine from other hardware. So nothing's broken on the Hashden side. The issue is the worker name DirectHash sends. It bakes your BTC payout address onto the front, so it ends up as: bc1q…5ulav.genesis-den.…directhash — four parts. Hashden routes on den-slug.npub[.rig], three parts max, so that extra BTC address makes the stratum unable to attach your shares to the den, it just reads the leading bc1… as a plain solo address. With Hashden you don't need a BTC address in the worker at all; your payout is set in the den when you join. On the Bitaxe you can fix it directly, set the Stratum User to: genesis-den..bitaxe1 On DirectHash there's currently no way to drop that forced BTC prefix, so rented hashpower won't attribute until you add a plain worker field. Ping me once the Bitaxe is updated and I'll confirm shares are landing!

Once you enable that I’ll test with hashden and buy some hashpower from you for my den.

Hashden: a marketplace of Bitcoin solo-mining dens. ⚒️ Join a den, point your Bitaxe (or rented hashpower) at it, and if the den hits a block the reward goes straight to miners through the coinbase, no pool wallet, no IOUs, no "we'll settle later." Non-custodial by design. Nostr login, no email/KYC. Sub-dust shares get fanned out over Lightning. Open alpha → https://hashden.app/

Thanks for the shout-out! I'll grab some hashpower from DirectHash later and point it at my den. ⚡ Quick one though, I don't see a worker name field in the advanced pool config. Hashden routes shares purely by the worker name (den-slug.npub.rig-id), so without a way to set that, shares wouldn't attribute to a den. Is the worker set somewhere else, or appended automatically?

Hashden’s been rock solid so far. The node is really the only thing that could give you trouble, but you can always plug in your own via RPC.

care to take a look at https://hashden.app ?

Join my den https://hashden.app/g/genesis-den

Mining is centralized. We can push back together. Hashden, a directory of Bitcoin solo-mining dens for small communities. Non-custodial. Anonymous by default. Open alpha → https://hashden.app #bitcoin #bitaxe