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.npub1…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.@DirectHash.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!
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.npub1…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.@DirectHash.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!
2