We had tested #Bitaxe in all the existing Pools, and we had Rejected jobs, Not-Found jobs, Very-Low jobs and Stale jobs in ALL of them.
It's curious that none of this happens in the PyBLØCK #Bitcoin POOL.
We don't have to share any metrics since you can check it for yourself.
I don't see this issue on nostr:nprofile1qqsq9k04vahllseell55m74n3047y88pzlr0z5yany32st29fapqmgsppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgawaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skctc87ckyu.
What machine, time, hashpower, etc?
A variety, from a Supra up through the new NerdQAxe++. Both via the default pool and via DATUM. For a long, long time. Both via my Comcast Business connection and via a cell hotspot.
IOW, I call B.S.
Tested a bit on SBI and Luxor at one point and that was OK, too.
Can you show us a screenshots of AxeOS of this variety? We only need the Shares pic to verify it.
Like I said, I call B.S. This is a Supra, which is the least powerful of the bunch, and it has no issues. You can even verify the shares at https://ocean.xyz/stats/bc1qce93hy5rhg02s6aeu7mfdvxg76x66pqqtrvzs3.SzarkaSayHash , since it's donating hash to the nostr:nprofile1qqsqhk42dz0exfcsln4yqmdkjys0nvd7dqndgacpsa7w7pt7njq2uuspzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcpzdmhxue69uhhqatjwpkx2urpvuhx2ue0qy28wumn8ghj7un9d3shjctzd3jjummjvuhsjgllr6.
