[ANN] ccminer 2.3 - opensource - GPL (tpruvot)

[pallas]

Either very bad luck or something wrong on the sib pool.

[1714012709]

1714012709

[1714012709]

1714012709

[1714012709]

1714012709

[1714012709]

1714012709

[bensam1231]

Either very bad luck or something wrong on the sib pool.

4% of the network hashrate is going to have bad days. Throw those dice on a pool with more hash.


DCR pool getting 'server full' messages? Anyway around this?

[pallas]

Either very bad luck or something wrong on the sib pool.

4% of the network hashrate is going to have bad days. Throw those dice on a pool with more hash.

4 blocks in 2 days with a TTF or 2 hours is very bad luck or, possibly, an issue.

[bensam1231]

Either very bad luck or something wrong on the sib pool.

4% of the network hashrate is going to have bad days. Throw those dice on a pool with more hash.

4 blocks in 2 days with a TTF or 2 hours is very bad luck or, possibly, an issue.

It doesn't matter what the TTF, statistically speaking depending on the % chance over time determines essentially luck. That's why you stick to pools with higher %s of the network hash or you risk high variance.

Higher block times makes variance even larger as there are less data points.

[pallas]

Either very bad luck or something wrong on the sib pool.

4% of the network hashrate is going to have bad days. Throw those dice on a pool with more hash.

4 blocks in 2 days with a TTF or 2 hours is very bad luck or, possibly, an issue.

It doesn't matter what the TTF, statistically speaking depending on the % chance over time determines essentially luck. That's why you stick to pools with higher %s of the network hash or you risk high variance.

Higher block times makes variance even larger as there are less data points.

well, TTF essentially tells the probability to find blocks, is just another index, so yes it does matter.
we should have found 24 blocks on average on two days, and only found 4, even if we had low relative hashrate, it's pretty bad IMHO.

[bensam1231]

Either very bad luck or something wrong on the sib pool.

4% of the network hashrate is going to have bad days. Throw those dice on a pool with more hash.

4 blocks in 2 days with a TTF or 2 hours is very bad luck or, possibly, an issue.

It doesn't matter what the TTF, statistically speaking depending on the % chance over time determines essentially luck. That's why you stick to pools with higher %s of the network hash or you risk high variance.

Higher block times makes variance even larger as there are less data points.

well, TTF essentially tells the probability to find blocks, is just another index, so yes it does matter.
we should have found 24 blocks on average on two days, and only found 4, even if we had low relative hashrate, it's pretty bad IMHO.

Yeah, it would matter on 'average' in a perfect world with perfect variance. That's not the way luck works though. The less data points the higher the variance. It's entirely possible that the pool might've found 2x what it should, however, that chance is much less likely then finding .5x what it should because it has less data points therefore other pools will have higher luck (assuming all the other pools aren't split into equally shaped pieces, like 20 5% network hash pools).

It is bad, but not outside of the norm with high variance. That's why you can't sit on a pool with 1% of the network hash and expect it to find blocks. It's the whole reason solo mining doesn't work at high difficulty unless you posses a significant amount of the network hashrate.

[Epsylon3]

I checked the log, there was only one rpc request failed this morning.. nothing wrong i think.. i remember x11 was hard also at this difficulty on gpus in the past, and sib is slower..

[pallas]

I checked the log, there was only one rpc request failed this morning.. nothing wrong i think.. i remember x11 was hard also at this difficulty on gpus in the past, and sib is slower..

Thanks. Could you please check DGB as well? Few blocks and mostly orphans.

[Epsylon3]

DGB orphans seems normal, i always had some, similar behavior as joincoin (could be the multi algo limit rule maybe)

[bensam1231]

DGB orphans seems normal, i always had some, similar behavior as joincoin (could be the multi algo limit rule maybe)

Yes. They're insanely hard to calculate profitability for too because of this and how they distribute coins.

[bensam1231]

So DCR server has a miner cap now? Trying to get on it with a different IP and it's not working. Keeps sending 'server full' messages.

[agente]

Is there any reason or user experience why I am getting only 50-60% of miner-shown speed on MPOS pools like miningpoolhub or theblocksfactory? One day graph on the also show ~60% of miner shown speed.
I was trying myr-groestl and lyra2z algos and was very disappointed with the results - only half from expected ((
I am using latest ccminer 2.0 and ccminer-alexis 1.0 with gtx1070 and gtx750

Same problem here. I know many users have problems with miningpoolhub lyra2z and ccminer 2.0

[scryptr]

YIIMP IS DOWN--

My miners cannot connect, and the website won't display.       --scryptr

[rednoW]

YIIMP IS DOWN--

My miners cannot connect, and the website won't display.       --scryptr

yes, and the latest 4 decred blocks were orphaned ... 1 day work in vain ((

[scryptr]

YIIMP IS DOWN--

My miners cannot connect, and the website won't display.       --scryptr

yes, and the latest 4 decred blocks were orphaned ... 1 day work in vain ((

YIIMP IS UP--

Maybe  some changes, too.  --scryptr

[Epsylon3]

maintenance required following a hack... will be busy on that for 24h...

For the story, 31 DCR were stolen, and 1660 LBC, by some web server session hacking method..  (and also some dust from a few other coins)

Rewards on DCR were a bit messed up due to the reboot without closing the wallet properly... which made "orphans" and has dropped the earnings.

It took me some time to reimport the relevant backups to be able to restore them, its why the decred pool is stopped, to allow users to review their balance graph and understand what im doing...

So i had to rebuy these amounts from my pocket (and from two DCR donators/friends) after some "panic code to secure yiimp" yesterday evening.. and im now swapping mining wallets one by one.

Relevant txs :
DCR: https://mainnet.decred.org/address/DsXdQrmUFsYebPirWVfmV2TjgyG5Si94UeA
LBC: https://explorer.lbry.io/address/bKUDoSWWq8C7ZPyUxLgug7ZQ47qjZ24Fgy
BSD: https://chainz.cryptoid.info/bsd/address.dws?iMQTwUoSNJHUc79h3thRqJpKfFHLnj7iwW.htm (sent to cryptopia)

An extra DCR block reward was distributed to the users as compensation for the down time... Decred pool should be back online this evening

[daberti]

Welcome to the discussion thread for my ccminer fork.

This variant was based on cbuchner1 v1.2 beta, and now supports colored output, stats API, multiple pools, conditional mining and time limits, and many other features.

It contains most algorithms, except the ones specifically made cpu such as m7m. Some of the first algorithms were implemented by djm34, adapted to be usable on both linux and windows.
My releases are generally tuned for the Geforce GTX 750Ti, which is a good reference for tests (Linux + Windows) and has less hashrate drop in activity (unlike the 9xx series).

Epsylon, I'm using latest version (win binaries) on https://aeon.kryptopool.com/#
Geforce GTX 750Ti here, with latest NVidia win64 driver and 575 H/s.
Every now and then I can spot in the output a thick White horizontal line in the rightmost position of the line.
What is its meaning?

Thanks for your SW.

[Epsylon3]

euh, unsure i understand what you mean by " thick White horizontal line in the rightmost position of the line"

could you do some screenshot ?

[daberti]

quote author=Epsylon3 link=topic=770064.msg18585225#msg18585225 date=1492169671]
euh, unsure i understand what you mean by " thick White horizontal line in the rightmost position of the line"

could you do some screenshot ?
[/quote]

Sure. As soon as I'll see it again.
It is like an underscore char, White and bold.

EDIT:
Here we go
https://www.dropbox.com/s/dyurw5azmd8ze84/The_white_line.jpg?dl=0

[bensam1231]

maintenance required following a hack... will be busy on that for 24h...

For the story, 31 DCR were stolen, and 1660 LBC, by some web server session hacking method..  (and also some dust from a few other coins)

Rewards on DCR were a bit messed up due to the reboot without closing the wallet properly... which made "orphans" and has dropped the earnings.

It took me some time to reimport the relevant backups to be able to restore them, its why the decred pool is stopped, to allow users to review their balance graph and understand what im doing...

So i had to rebuy these amounts from my pocket (and from two DCR donators/friends) after some "panic code to secure yiimp" yesterday evening.. and im now swapping mining wallets one by one.

Relevant txs :
DCR: https://mainnet.decred.org/address/DsXdQrmUFsYebPirWVfmV2TjgyG5Si94UeA
LBC: https://explorer.lbry.io/address/bKUDoSWWq8C7ZPyUxLgug7ZQ47qjZ24Fgy
BSD: https://chainz.cryptoid.info/bsd/address.dws?iMQTwUoSNJHUc79h3thRqJpKfFHLnj7iwW.htm (sent to cryptopia)

An extra DCR block reward was distributed to the users as compensation for the down time... Decred pool should be back online this evening

Here's some fix it funding.

TX: 6e6613e21d3fcc172c895fcb49aebc692326ae9a3b6780ce4582dabe5fe87637