Yeah;  the disconnects on sha256 must have to do with higher hashrate connections...

My S3 isn't seeing the disconnects at all;  but my S7 regularly seems to start beeping and drop its fans while at the same time I can see it's output in MinerMonitor drop to the 100-300Gh range;  then less than a minute later it pops right back up to speed and is hashing fine.    Its acting like I yanked it's internet access for a short bit....   I put a failover pool #2 to solo.ckpool;  but the miner stayed locked on the solo pool instead of switching back to zpool.

I wonder how a wallet can cause this... very strange.   Seems to happen when my share % has peaked for 10-30 min.

http://zpool.ca/?address=1GCXCFihv74gusaM9fHNgbeH5ogk9sPhMC

Most of my rentals had nice linear profitability slopes on the 24hr earnings graph;

My s7 is rather... jagged.

Note:  setting difficulty manually to a value too low, just right, or too high;  had zero effect.

i think I've seen a dropout on my s7 already.  They weren't noticeable on my s3.

Strange; may be an avenue to consider.... Although i myself can't see how it would apply.

Lol; yeah.  And the SHA profitability estimate is hanging around 0.0035 which is on par with what it should have been when it was reporting 0.0054.

I just got the S7 hooked up an hour ago;  it's mining to its own address; so I can keep its profit separate from the rest of my little farm.

I'll report earnings as they reach milestone points

Yeah.  Typically when trying a new algo ill give it a minimum of 24Hrs by itself just to see what my 24 hour graph looks like;  see if its worth adding it to my list.


The fact that the short term profitability shows Zero still;  is a turnoff for most I would think;  but that happens with every algo when its brought in.

I think i spent 3 days on DMD-GR before I gave up on it; and it ultimately got removed.   I dont even think there were any found blocks on that algo.

*edit* does the pool's code monitor the Deltas of the coins difficulty as they change throughout the day?   This is more of an advanced question;  so im not expecting an answer....

I need to get off my butt and give it a shot... but that means setting up a new miner app;  and adding it to my round of algorithms.
Hopefully sometime in the next few days ill have the chance to get to it.    I am personally curious on it's profitability compared to the other algos.

Still going strong.  I am really kind of baffled at the differences between a month ago and now given the fact that the pool's code hasn't really changed.   The major difference is I moved my S3 from my parents house to my house;  My internet here was very crappy last month and I moved it there to see what the latency difference of a fiber connection would have... if any.   it was very minor;  just fewer rejected shares due to a block found during transmission to the pool.

I am still seeing two payments/day for at lease 2.2-2.8mBTC;  which yesterday got me just above 5.5mBTC during both periods that there are 2 payments in the 24/hour earnings graph.  I noticed the pool's short-term earnings estimate in the upper right for SHA was 0.0033/Gh;  yet luck/profitability seemed to be right about where it normally is (maybe one device more profitable in that time?).

So by this figure ~0.165BTC/Mo (~$72) if the current profitability holds true... again;  I being lucky enough to have an unfettered power connection at my residence =)

I suggest btc....  It's 100% consistent

I know how you feel.  The issue of being stuck on lyra constantly was my fault;  But the profitability thing has me puzzled.   maybe its just the pools luck is up or the new coins and changes to which ones we run are effecting it as well....

I also finally have my GPU set up with most of the profitable coins, and just started running a separate process for the newer CPU based coins.  Plus my orbs are self-overclocking upwards of 1000Mhz;  from the base of 800-850... it depends on temperature on how high they will go.

I don't monitor the processes on my antminer;  so I can't comment on the issues people were having with sha256/diff/disconnects.  And I am waiting on getting the S7 and doing another several days of comparing share% vs. hashrate% of pool.   Regardless;  I am very impressed; and I have brought a few people to this pool in recent days.

If anyone wants me to post up my GPU multi-algo batch file;  I'm glad to share it if people need the help.  I have a few copies of ccminer that I keep in the same directory to use for optimizes in certain algos.

another 5+mbtc day.  not a fluke.

I'm very happy its a trend for me.  Then again;  I also have since yesterday; added yescrypt/argon and 4 orbs... so the more the better the way BTC is rising =)

Libcurl is a part of the miner app as it has dependencies for the communication; which is the alert it is giving you; telling you the application can't do that function.  It doesn't look like a server-returned response as I read it.

That's a problem with your build.

Compile yourself or find another pre-built copy somewhere...

oah snap.  ill add the v2 and see what changes if anything.

and the miner algo setting is proper;  it was set to lyra2v2.... just not the password setting.

edit:  yep.  seems; like it may have worked.   a longer than 1 min trial is needed to confirm;  but it didnt even push itself straight to lyra;  it stopped on X15 and started mining away;  so it may be fixed.   I feel like a moron... lol

blue circle is when I added lyra2 to the list.
red circle is showing a mona block being generated; thus the payout spike.
green (hard to see) highlights the before and after being stuck on lyra.

So thats why I normally only jump on lyra when there is a large hashrate and profitibility that I notice;  when I notice it... then I have to remove it from the batch file and restart the process to continue gaining as-normal.....   without my interactions;  I can definitely see a hit in my payouts if i leave it locked on lyra.

my password isn't that long.... can't be it.  My longest password is 66 chars.
Presently this is the password i'm using on my lyra2 batch line: c=BTC,d=1,x11=8.2,x13=6.8,qubit=12.5,x15=5.6,c11,lyra2=9.6
I haven't taken the time to see what my hashrate actually is with c11 so its not customized like the rest of my algos.  I'm only keeping the algos on that have consistently given me a decent profit when I did 24 hour tests on each individually.


As for the difficulty in Argon;  I tried not specifying a diff, then I tried setting to 1;  no effect.  tried setting to a fraction (0.1) and stratum assigns me to a diff of 1 or 2..

I'm using a current cpuminer argon2 optimized fork.

crackfoo:  when clicking on total paid to get a list of transaction history;  I am not able to get a scroll bar to scroll through the list.

Maybe its the fact im on FF;  but;  it seems the other FF related issues i commented on months ago have gone away.

also; I am still getting my miner stuck on lyra2 every time I add it to my rotation of algos in my batch file...   The profitability is half of what it was when I added it;  and by some quick math, the stratum should have dropped me to another algo by now.   Any idea why?   Ive even changed the profitibility to be 1 (where others are set to considerably more) and it will still keep me locked on lyra2.

Throestyle1:  just the payment address as a username no "dot workername"

even when mining cpu on x11 before;  share submittal freq just seemed higher when I was doing CPU mining before.

then again;  maybe im just ignorant to the graces of having high output asics and video cards for some time...

thanks for the input tho.  ill ignore it.

Anyone else having this type of issue with argon2?

Its acting like when i had the same issue with lyra2 having the difficulty is set too high;  the first 8-16 hashes (im running 2 quad core xeons) never get accepted;  then after the first accepted share;  it tends to see more accepted... until a block/work restart is performed...

thoughts?  This doesn't seem very normal...

im actually not counting it all just the "balance" total;  not total unpaid.

The un-exchanged balance is usually half of what has already been sold on the exchange if my mining hardware keeps online reliably. (this detail probably was superfluous)

my 5.3mbtc 24/hr total was on the actual listed 24 hour total list of tx id's.....

I always have my S3@ stock speeds, and an Asus GTX980 mining (presuming my internet isn't down, or the antminer doesn't get its usb disconnect issue and turn off the green light/stop hashing); and generally see 3-3.8mbtc/day on the 24hour payout list between just those two miners + the 8 5-chip scrypt orbs (~2.8Mh) that i normally also have plugged in.
During that day of the 5.3mbtc in 24 hour earnings;  i saw a nice linear sawtooth pattern on the 24 hour graph that looks eerily identical to today's graph that currently only shows one payout on the list/summary of 24hr tx's.  Before the payout freq change;  I would see ~3TX/day every 6 hours;  with an average of 1.2mBTC each.   Given the payout changed the size and scale of the sawtooth pattern;  its hard to understand how it was much higher with less hardware and no visible increase in the payout earnings or balance.

Whenever something like the crazy creva price spike happened;  I will see a big spike in the thin line of the 24hr earnings graph that shows total mined; and later when its added to my balance, the solid lower portion of the graph sees nearly the same rise of a balance(assuming the lower one is green; i'm mostly colorblind;  although I can see some of every color).

I will grudgingly admit that I had a new lady over;  and unplugged all my gridseeds and cast them aside to get rid of some wire mess and noise while she was here for a few days;  and I haven't taken the time to hook them all back up again.... so I could be adding ~2.8Mh of SCRYPT to the earnings if I get them plugged back in.... but im kinda baffled as to why my earnings yesterday were higher when the orbs weren't even hooked up and theres no visible spike in profitability in the graph.

3.5mBTC/day is pretty much a chicken I can count before its egg is hatched;  its been that consistent ever since switching to zpool from xpool when it first opened to the public.  Only when hardware goes offline for more than a couple houes;  do i notice a hit in my 24hr earnings.

I believe once this next payout minimum is reached (at this time I assume it will be roughly 4 hours from now by guessing)  I will see another ~5Mbtc+ day;  just with these two pieces of hardware.  I'm speechless....

http://zpool.ca/?address=1PHSDYvVp6HpqtuUPocK41DrdeHbbezaeP  
if you want to see the statistics and such from what i'm generating my info off of and what this hardware is doing.  Please note in my TX history;  the large high frequency payouts are from doing 5TH+ rentals to test the pool profitability and share% readout issues I was seeing specifically with the SHA256 algo.    I didnt ever seem to notice any discreptency with the video card mining;  as when I was pulling 10Mh, and the pool statistics were showing 100Mh of miners;  I was getting just a hair under 10% share percentage so I never looked closer at it.

When I did the first 50Th rental (pool was avg 25-50Th for the preceding weeks) so I was sure I should be seeing very close to 50% share credit;  when in fact I was typically seeing ~43% or less.  That's when I first mentioned a potential problem on this forum; but was easy to dismiss it because it will weight different people to different coins at different times (as I understand it); so you cant go based off individual coin share %...


Another strange thing was the share% seen on left next to the "miners" section on the wallet page;  it shows a share % that was very much not the same as what was expected to be seen when doing the simple calc between that number, my pool reported hashrate and the total pool hashrate reported to the top right;  or the mined block share % credited to me.  seemed around plus or minus 80% of the expected amount.  It correlated to the mined block credit percentage i was expecting vs. seen  so that lead me to think the table at the upper right is just got an error in its display.  But it is way beyond me;  I know coding and languages;  but I don't want to learn how someone wrote all the code for the pool because they went though al this trouble to write it in the first place; and I know first hand how people always had trouble figuring out how I did things in my 3d engines i worked on in the 90's  I know there are much more qualified people to look into that since they have been at it longer than I and have time invested in it already.

Yeah;  and the new payout schedule takes my small account 24hour estimates and changed them drastically; for only a few hours/day I see a realistic 24hr total, but now only a single 2.5mbtc payout when there's still 1-1.5 to be paid; so I only truly see my real 24hr earnings for a short window twice a day.

Doesn't really bother me though.

I'd say for people mining with larger farms; don't use a light wallet so the multiple tx issue clogging their wallet is non-existent in that respect....  I actually loved the old payout schedule.  It was an easier way to know if any gear went down in the past 2-6 hours;  vs getting a payment alert and value from my wallet only twice a day.   Just my .02c on that matter.

FWIW; I mostly mine with sha256 on this account;  and am typically seeing ~3.5mbtc/day.   Without any major exchange bonuses/luck; today I am at 5.3mbtc in the last 24....

So something seems different.


Definitely a pleasant surprise.