my #bitaxe runs like shit on public pool and Ocean...erratic connection, resets inexplicably, hashing power goes to zero randomly.
then i changed to solo.ckpool.org and it runs like a charm and is also reporting 10-15% higjer hash rate. anyone else? these other pools siphoning hash, or just run poorly in incomparison?
#bitcoin
#homemining
#asknostr
nostr:nevent1qqsry7wq3fsn2can6y37rky9f4g3asx8zz2t39w5dlje0845yehuuxcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsyg9xr84hd9jtsu9qakk3x0d3hysc8djnxvedu426qvad5n33r46ex5psgqqqqqqsdc2nh9
Only have pointed mine to solo ck pool need to try ocean
nostr:nprofile1qqswswmx4rkj6d7q05dtafhpkqq2z42fc62s37jvtp642m2jkpfxc2cpzamhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuegpzamhxue69uhkummjw35hxtnwdaehgu339e3k7mgpr3mhxue69uhkummnw3ezumt4w35ku7thv9kxcet59e3k7mgtxa5me was it you that also had this issue?
Yes, I had the same experience. I tagged @OCEAN about it and @GrassFedBitcoin replied saying it was actually working. But I don't think it was.
I've been mining on ckpool for 10 days now with no issues.
thanks. i suppose that would explain the hashrate inconsistency, but doesnt explain why the machine disconnects or starts mining at almost 0 hashes. based on how much better my bitaxe performs on ckpool, something else going on that they should look into.
Here too. Tried public pool and can rarely even connect. I had CKpool set as the fallback pool, and it kept using the fallback for two days until I switched it to the primary. As far as hash rate I can’t confirm
Oddbean new post about login | logout