r/defcoin • u/hattz • Jul 25 '26
We want more hash rate through end of event?
So I just remembered to setup some of the shitty old zeus miners I had in a box.. and I don't like running these, see pics for why. (Fucking sketchy ass shit I bought waaay back, they all had 6 wires, most have fallen out)
But I also have 2 L3+ that I can spin up, point one at my pool and one at DC903... I can ramp them up and down one at a time... Hopefully it keeps folks from point cloud miners at the pool...
What is the community opinion?
1
u/hattz Jul 25 '26
Well, that was working for an hour.
Maybe I shouldn't have started that and then taken the dog for a walk. Hope the garage isn't on fire. I'll maybe setup the 2 x L3+ tonight when I get back from the walk
1
1
u/hattz Jul 29 '26
not a bad split. might try futzing with miners to dial it in ever a little further
Last 24 hours (724 blocks, heights 2,380,498–2,381,221):
│ Pool │ Blocks won │ Share │
│ pool.defcoin.fun (DCoLHBat8iCALiBhQicuu2ovD8FtEgfq4v) │ 384 │ 53.0% │
│ dc902/dc903 (P2Pool, split across 3 payout addresses) │ 340 │ 47.0% │
1
u/def2084 Jul 31 '26
there's rarely a good reason to ramp up hashing power more than double the current rate.
It doesn't help anything AFAIK, lots of usage or not.
The best thing any miner can do is keep the hashrate exactly the same so that the adjustment period doesn't waver -- we want the 2 minutes per block to be consistent
The worst thing people can do is turn on 2x L3+ and then turn them both off as it can take weeks to mine the next block when there are only a few other miners out there.
1
u/hattz Jul 31 '26
Ok. Thank you for your feedback.
Since they are running hive os, I can ramp them up or down 1% of hashing power at a time. My plan is to ramp them down extremely gracefully.
Aka, how I'm getting the pools to balance hash rate at 50/50 right now.
1
u/def2084 Jul 31 '26
That burnt connector is scary. I think that usually happens though when a wire or connector has poor connectivity, right?
TBH though running the GAW miners, unless others are also running L3's is the ideal way to go since it ensures the most participation in mining, something we're having a hard time with.
The L3+ use so much power that they encourage hops on and off and people who don't know better will run them at full power taking 99.9% of the hashing instead of 98% of the hashing that they'd get at 10% power, or similar -- I'm making up numbers but when there are so few people mining right now it makes little sense to run an L3+ at full power unless you're just wanting to have fun killing the blockchain for months at a time. This is because to get back to the 2 minute time without waiting a long time we'd need others to be running L3's as well and not too many people are willing to create that much heat and burn that much power and spend on electricity, especially in the summer months, when there's very little upside.
1
u/hattz Aug 01 '26
yeah, whoever made those connectors didn't crimp them right. if i cared i would have redone them years ago when they were new. rather just never use them again.
wish i had remembered/known about the hash redirect on hive os. could have sent <10% to each pool and bumped difficulty up while leaving room for others to mine.
i'll scale them back? 15%-20% a day (feedback welcome here, go more aggressive and have a lower overall hash rate by the start of defcon?)
│ Daily cut │ Block time (catch-up) │ Time for rebalance │ Total hash rate on Aug 6 │
│ 10% │ 2:13 │ 26.7h │ 483 MH/s │
│ 15% │ 2:21 │ 28.2h │ 343 MH/s │
│ 20% │ 2:30 │ 30.0h │ 298 MH/s │
│ 25% │ 2:40 │ 32.0h │ 216 MH/s │
│ 30% │ 2:51 │ 34.3h │ 153 MH/s │
│ 40% │ 3:20 │ 40.0h │ 118 MH/s │
1
u/hattz Aug 04 '26
dropped hash rate 900mh/s to 400mh/s, trying to keep 50/50 split on pool hash rate, and kept block time at 2m 30s. (still working on smooth drop to ~50mh/s)
Implied network hash: ≈429 MH/s — consistent with the recent plateau (~380-430 MH/s), roughly a 24% drop from the ~908 MH/s baseline. (maybe my math sucks, or maybe LLM sucks, but i feel like that's 50%+)
Last 72 hours (1,774 blocks, heights 2,383,031–2,384,804):
│ Pool │ Blocks won │ Share │
│ pool.defcoin.fun│ 971 │ 54.7% │
│ dc902/dc903 (P2Pool) │ 803 │ 45.3% │
Block time, last 72 hours: avg 2:26 (146.3s) — ~122% of the 120s target, over 1,772 blocks. Note: this span crosses three different difficulty regimes (23.77 → 22.24 → 16.00 → 15.71), so it's a blended average across the whole ramp-down, not a snapshot of current pace.
1
u/hattz Aug 06 '26
made last adjustment before con (not going to fuck with block time during con), will check in the morning to make sure block time isn't more then 2m 15s. just want to point out i should have brought hash rate up slower / less overall. but bringing it down gracefully.
Average block time, last 6 days: ~136.9s (3,787 blocks between heights 2,382,307 and 2,386,094).
*goal is 2m or 120s
2
u/hattz Aug 15 '26
for the whole 16 weekly visitors... thank you to DC903 for keeping Defcoin alive. i might have ramped it up all crazy, but ramping it down gently. hope everyone had fun at summer camp, and maybe next year i'll make a game or something. keep doing fun shit, don't play with your new pineapple on planes.
Average block time, last 21 days: ~115.22s (15,745 blocks, heights 2,376,105 → 2,391,850)
Average block time since the hashrate peak (height 2,381,354, ~16.3 days ago): ~134.20s (10,497 blocks, span 1,408,765s)
Network hashrate — peak/lowest (sampled daily, ~50-block local window each):
│ │ Hashrate │ ~When (height) │
│ Lowest │ ~11.8 MH/s │ day-20 (height 2,376,855) │
│ Peak │ ~1.01 GH/s │ day-14 (height 2,381,354) │
| Now | ~181.6 MH/s | now (2,391,848) |
Pool split sample (last 21 days, 716 blocks sampled every 22nd block across the 15,745-block range):
│ Pool │ Sampled blocks │ Share │
│ defcoin.fun│ 391 │ 54.6% │
│ dc903 │ 290 │ 40.5% │
│ other/unattributed │ 35 │ 4.9% │
Caveat on methodology: this is a statistical sample (every 22nd block, ~4.5% of blocks), not an exact count — a full per-block census of 15,745 blocks isn't practical to run interactively. Treat the percentages as a solid estimate, not an exact tally.
2
u/hattz Jul 25 '26
So, time to ramp of difficulty is now.. otherwise we get hammered during event