We just sent our weekly Digibyte mining loyalty rewards, so please check your wallets.
Paid 2,499.99999702 DGB to 382 miners (6.54450261 DGB each)
Paid in 3 separate transaction id's. 8d23968a4bccd177a8765052aae3e507f720f7cc7c6286380d0399ed6d277d0b
b3fc0fd61e535c76ba76aff3e9ba58127d752f1a959b132fefbcdb7dc60ced36
e36a58b4f95a45278106d3bfd4ae63489bf22324e7e48d271cbf70afa206ed6e
Thank you for your loyalty!
Is there a weekly draw for the XEC pool?
I’m sure I’d build up a couple of draw tickets, but can’t see any draw details on the pool page
Is there api that can be submitted to https://miningpoolstats.stream/ecash so we can get the pool to show up, might help drive some more miners to the pool
Happy 4th of July, everyone!
Wishing all of our miners, builders, and the entire community a safe, fun, and relaxing Independence Day. Enjoy the fireworks, fire up the grill, and have a great holiday with family and friends!
Enjoy the day and happy hashing!
Anyone on here currently using any solar devices to run their rigs? Looking into DIY kits but was curious if anyone had any experience, one themselves or recommendations. Happy Hashing!
Non of these coins reached my wallet
Address SeAcE7ff5mJAQkJRXWvytmfZ8a3gXZCXuT
Please assist
We wanted to share a big thank you to Jared and the DigiByte team for working with us directly to get to the bottom of the SHA256 pool issue we hit after the recent DigiByte node upgrade.
After recently updating our DigiByte node to version 9.26.2, we started seeing a major drop in credited hashrate from certain SHA256 miners, especially NerdAxe and NerdQAxe units. Device hashrate stayed normal, but poolside credited hashrate fell off hard, which told us something in the share flow had changed.
Over the last few days we worked closely with the DigiByte side by feeding them real miner websocket logs, pool behavior, live testing results, and side by side comparisons from our environment. We were able to show exactly what miners were receiving, what they were submitting back, and how the behavior changed between the old and new node/job versions. That back and forth made a huge difference because it moved the conversation from theory to actual field data.
Jared stayed engaged through all of it, reviewed the evidence, acknowledged where the problem came from, and helped narrow it down to the version rolling and bit 23 interaction affecting some SHA256 firmware. Once that was understood, we tested the fix in our sandbox, confirmed it restored expected behavior, and then rolled it out live.
We really appreciate the fact that the DigiByte team listened, took the reports seriously, and worked with us to solve it properly. That kind of response matters a lot.
So sincerely, thank you to Jared and the DigiByte team for the time, the communicatio and the help getting this resolved. We are very happy to see this fixed and moving in the right direction.
Did finders bonus structure change? I was at 15%, then this morning after I found a block it dropped to 12%. I have not disconnected from the pool and I am topped rank miner at the moment by power/24hr
Name: tx_solar_miners
Wallet: ecash:qzsxe5tnrz5hwfwffta2uje9h38xukqhhsdwfck9n2
This morning I had a pending balance of around 95000 XEC.. I know it takes time to confirm, but I came home this evening to no pending balance and no XEC added to my total paid balance.
Am I missing something?
Not sure if it’s just me, but I’m finding my XEC miner dashboard takes ages to load my miner’s hashrate, blocks found, pending balance etc.
the other pool dashboards seem to load fine, just XEC takes some time for some reason
Curious what are people doing with XEC ?
Holding for now and building up I get it but is there any roadmap for the coin or any hope it will go up in value ? 🌙
Miners, the DigiByte Core team has released v9.26.2 today as an emergency fix for an active network attack.
What happened: Starting June 28, an attacker exploited a dormant bug in the v8 codebase that left DigiByte's retired Groestl mining algorithm (retired in 2019) unenforced. The attacker has been mining Groestl blocks at floor difficulty, causing brief chain splits and network instability.
What v9.26.2 does. Permanently blocks retired-algorithm blocks. Once the majority of nodes upgrade, the attack ends and the network fully heals.
The deadline. Block 23,808,000 (on or about July 6–7). At that point v9.26.2 nodes hard-reject all Groestl blocks. Nodes still on v8 will be on the wrong chain and will basically be inoperable.
For our miners:, we are upgrading our DGB pool node to v9.26.2 right now. There will be a brief maintenance window of approximately 5–10 minutes. Mining will resume automatically, no changes needed on your end.
No coins were stolen and no transactions were reversed. This is a stability and security fix. Keep your miners pointed at the digi pool as this should only be a brief max 10 minute downtime.
The HashedMax Team
Is it just me?? I sent a ticket but nothing has deposited since 10:19 this morning
Me tirem uma dúvida e como vai ficar os blocos achados de dgbs, com esta bagunça muitos saíram tiraram suas máquinas da rede dgb/digibyti.
The pool is saying I have 3.8 billion XEC pending 🤣
Got mine order from TinyChipHub today and I’m having some issues. The Watch Dog only works when connected directly to my PC via USB. Totally dead otherwise and I have tried other cables and power adapters. The ZyberBlanc is hashing but the fans are extremely loud even on Eco mode. Like 4x louder than a Nerdqaxe. My ambient temp is around 25c 77f. All my other miners sound normal. I emailed tch but haven’t heard back yet. Just wondering if anyone else is having issues.
The payout for the first 2 XEC blocks we hit have been successfully processed. Please check your XEC wallets (for those that mined with us).
As the title says this is my quick take on why it’s not profitable for me to continue pool mining DGB on the DGB Hmpool.
I’ve been mining from almost the start of the Hmpool journey, through ups and downs the team behind the hmpool has been nothing but great and very supportive, helpful and quick fixing bugs etc.
Given my little home setup, which consists of 2x Avalon nano 3S’s and one NerdQaxe++, running standard configuration (no overclock/high mode) about 15Th in total it simply doesn’t add up to the current configuration of the Hmpool to continue pool mining DGB. I’ve found 56 blocks since first connected, in that amount of time I only collected about 9800 DBG, compared to running let’s say on SoloHash with 0.5% fee I would have had collected: (56x259)-0.5%=13.778,8.
There are too many small and very unsupportive mining devices like NMminer (or whatever these ESP 32 boards are named) and small USB stick free leashing while not contributing anything in return. Let’s be honest these stupid NMminers and USB stick hashing on what a couple of 100mega hashes/s doesn’t find anything. They are simply free loading on the true/real miners doing actual work.
If you ask me everything under bitaxe gamma ~ 1-1.2th/s should have their own pool not shared with everyone else. Please consider splitting the payout scheme into two separate models so the trash free-loader devices can find 0-5 DGB blocks per year on their own pool (at best, let’s be honest it would be 0 blocks). The true miners can enjoy a fair and reliable system without freeloaders.
Anyways sorry for the salt, i just see hashing numbers continue to drop and real miners leave…. But i see why. I’ll unfortunately also switch my miners over as it doesn’t make sense and never has been due to the current model.
On xec pool i got 8.69g now and somebody 20g or 200 and no block found how is this Happening? Now we should theoreticlly 2 Blocks found but nothing.
@hashedmax look into it pls desoo is my id
ecash:qz02zgkaed5l605jr8prqyywyn2pedtcx589l53pzx
Pls they would be 2 Blocks aleeady aomething is wrong
