 Show Posts
|
|
Pages: [1] 2 »
|
we were going to reduce the 2 hour drift to 15 minutes, then i brazenly chose 30 seconds. 2 * 15 is 30 seconds which is our blocktime. we decided not to go with that as blocktimes do vary a bit.
No, you didn't. You copied and pasted code from peercoin without fully understanding it, a la https://github.com/peercoin/peercoin/pull/93/commits/4281cb55b04600189bff4f0c8a92e042b34e75f8. 2 * 60 * 60 makes sense as a way to show **2** hours. 2 * 15 doesn't make any sense, if 30 seconds is your desired value. You'd simply just write 30 if that were the case. 2 * 15 is a mistake made by a programmer trying to depict 15 minutes, as the comment indicates. In this case, you weren't even the programmer who made the original mistake. You were a copy & paste monkey who didn't catch it. Which is fine, but rather than own up to your mistake, you try to invent a reason to make yourself look better. This is not trustworthy behavior. |
|
|
|
Almost. We’ve already spend 1000+ hours for coding, you can check the GitHub here and our roadmap here.
I looked at your GitHub. There's nowhere close to 1,000 hours of work there... ? I just see a few skeleton files here and there. Nothing significant. |
|
|
|
Besides a slightly updated algo which frankly is not much. [ ... snip ...]
To be fair, that statement could be used to describe Raven as well. They didn't create a new algorithm, so much as they combined a bunch of pre-existing algorithms. Sure, Raven has promised to do something more than simply x16r in the future, but it's just a hope and a prayer at this point. |
|
|
|
I repeat my questions one more time. How the autoexchange works on Zpool? Why SYS instead of BTC and LANA instead of LTC? And where is my funds?
If you specify a BTC wallet as your username, then your password needs to be c=BTC. If you use an LTC wallet, then your password needs to be c=LTC. If your wallet does not match what you specify in your password, then you end up with nothing. |
|
|
|
|
Since the project team doesn't seem to want to do it, I'd like everyone here to know that the end date of the Voluntary Miner Contribution Program has apparently been extended to February 28. This is three days later than the original date of February 25. They went so far as to edit their reddit comment with the new date, but not actually notify anyone via a new thread or tweet or anything.
|
|
|
|
zpool's API has some kind of limitation on it. If you poll it too quickly it returns nothing. Thus, appearing down.
If my miner has just polled the API, and then I restart it, 9 times out of 10 the API return is blank. Yes, it's very annoying.
1 query every 10s is the limit. 2018-01-26 11:32:21,345 [ zpool][ pools][ ERROR] zpool API error. Attempt: 1/10. 'ValueError: No JSON object could be decoded'
2018-01-26 11:32:32,443 [ zpool][ pools][ ERROR] zpool API error. Attempt: 2/10. 'ValueError: No JSON object could be decoded'
2018-01-26 11:37:56,408 [ zpool][ pools][ DEBUG] Getting zpool data.
In this scenario, assuming you don't have multiple systems making similar API calls from the same IP, you're not necessarily experiencing the 10-second limit crackfoo described. Rather, this is likely due to the site being hammered overall, and not being able to keep up with the sheer volume of requests. Of course, the end result is still the same. |
|
|
|
When you're under-guessing my performance my share % also decreases. There are never any changes in my console to substantiate these radical and frequent drops of performance. My submitted shares and hashrates remain consistent.
Even if your number of submitted shares remain consistent, if everyone else submits a higher percentage of shares for that block than usual, or if more miners come onto that pool because of a profitability spike, your % is going to decrease for that block. Mining involves luck. Both at the pool level and the individual level. Some blocks you get lucky, some blocks you get unlucky. The hash rate on the site is merely an estimate based on submitted shares. Thus, it makes sense that if your rigs get unlucky and post fewer shares over a period of time, the hash rate estimate is going to trend downward. But, the hash rate in no way affects your payout. You're paid based on submitted shares for found blocks, relative to the number of everyone else's submitted shares. That's it. |
|
|
|
thanks for the reply. Its awesome that you supply this service to us. Thanks for stating that you have no intention of paying us what you owe unless we actually do more work and you take another % off that. Im sure that you guys are still collecting your 2% no matter if the coins are there or not.
So saying that. WIll you take all the coins owed and give us the BTC equiv or do we just have to suck it up as a loss and switch to btc and just hope someone will mine enough of X coin to get paid?
And what were to happen when you decide the algo/coin isnt worth it and drop it? IS it gone?
It seems from the reactions in other places that you guys maybe a little on edge.
From the homepage: Non-BTC payouts depend on that coin being mined as your BTC balance is traded internally by our system to your currency of choice. If we have not or are not mining that currency your payouts will be delayed until the pool has mined the blocks for you to get paid. If you notice in the pools status that the currency is red, it means there is not sufficient amount of the currency to pay miner(s). It's recommended to use BTC as any other coin could be removed at anytime and payouts will not occur.
...
BTC is the only guaranteed payout currency
Yet another way of saying this is that, being paid out in anything other than BTC is at your own risk. If I'm being paid out in an alt and I start to build up a large balance, and then that pool has issues, or the pool's balance of that coin becomes insufficient to make the next payout, etc, then I stop my miner and change my payout to something else until the situation is corrected. If I don't do that, I have no one to get angry at but myself. |
|
|
|
I Am new to mining and using Nvidia cards GTX 1070 total 4cards i want to ask
whether Nvidia cards software version affects the hashrate? because mine is updated version 390 while in zpool website i didnt see anyone using this version
also please help how to calculate daily profit for the currency i am mining example CRC coin which shows (0.45790) what does this means?
thanks
Driver version can have an effect on hash rate. Though from personal experience, it's usually negligible. I'd guess the reason you see older versions in the benchmark data is mainly that it doesn't pose any benefit to do frequent driver upgrades. It'd just be wasted time. Especially for a rig which has many GPUs and a weak CPU. Upgrading can take a long time in certain cases. And then there's the risk that the newer driver will be buggy or introduce new problems. "If it ain't broken, don't fix it." As for neoscrypt profitability, multiply 0.45790 by your hashrate in MH/s, and the result is the value you would receive after a day of mining if that profitability estimate holds true, measured in milliBTC or mBTC. If you're being paid in something other than BTC, you'll get the equivalent amount of that coin when it's added to your balance. |
|
|
|
it doesn't matter, as long as you're consistent - the profitability factors are relative to each other. you could do m7m=5,yescrypt=7 or you could do m7m=5000,yescrypt=7000 and the results would be identical
You're not wrong in saying that m7m=5,yescrypt=7 and m7m=5000,yescrypt=7000 will provide identical results. However, if your intention is for the stratum servers to ensure that you're always mining the most profitable algo for your equipment, then the profitability factors you provide in your password need to be the same denomination as the current estimate for the algo. Here are the "current" profitability estimates for m7m and yescrypt: m7m, 0.0733 yescrypt, 0.01403 Let's say you have an Intel Core i5-6600K. Your hash rates are as follows: m7m, 69kH/s yescrypt, 2.4kH/s If you specify your password as m7m=69,yescrypt=2.4, this is the math that the stratum server does: m7m, 0.0733 * 69 = 5.0577 yescrypt, 0.01403 * 2.4 = 0.033672 Well, m7m should be way more profitable for you than yescrypt, right? According to these calculations, you'd be making $0.38/day with yescrypt, but $56.57/day with m7m. Thus, the stratum server will keep you mining m7m all day long. Except m7m is measured in MH/s, while yescrypt is measured in kH/s. So, you won't be making $56/day in reality. Thus, the correct password would be m7m=0.069,yescrypt=2.4. This give us: m7m, 0.0733 * 0.069 = 0.0050577 yescrypt, 0.01403 * 2.4 = 0.033672 In reality, m7m is only going to bring you $0.06/day at that rate. Not $56. Then, yescrypt is more profitable at this point in time. And that's why right now, you see 21,000 miners on yescrypt, and only 634 on m7m. This can be confusing because if you look at the chart on the website, m7m is listed higher in the table than yescrypt, because it's "current" estimate is a bigger number. But because they're measured using different denominations, yescrypt is currently far more profitable. |
|
|
|
Using that method, both m7m and yescrypt should be in MH/s.
The yescrypt chart shows kH/s. Check the caption for the chart on the left, not the table on the right.  Anyway, if you do the math, MH/s doesn't make sense. The pool hash rate for yescrypt is only 6.1MH/s right now. If the profitability calculation was in fact using MH/s and not kH/s, that means that the entire pool of 21,000 miners would only generate $0.91 combined per day at the current rate. That's not right. |
|
|
|
Yeah, I read about the profitability factors, but I didn't know what denominations they were using. I though both were in kH/s since cpuminer would report both as kH/s. Then I once though they both were in MH/s, since both are reported MH/s on zpool's pool status table.
We need something to let us know which algo is using which metric.
Even a simple line like the Pool Status chart: * values in mBTC/MH/day, per PH for sha256 & GH for scrypt, blake, decred, x11, quark, qubit, kS for equihash
The way I do it is to navigate to Pool, select an algo, and look at the graph for "Last 24 Hours Estimate (mBTC/XXX/day)." Whatever it lists for XXX is usually the metric you need to specify in your password. If you're really unsure about a particular algo, you can verify simply by doing the multiplication yourself (estimate * hash rate), and checking to see that the mBTC amount is reasonable for a day of mining. |
|
|
|
Crackhead, your pool says:
We are short of this currency (7.67989501 LTC). Please STOP your miners and switch to BTC until we find more LTC blocks.
YOU are responsible if you continue to mine for LTC despite this warning.
Are you going to do anything about this? I don't want any shitty BTC with the huge fees and days long transaction times!
Can we get payouts consistently in BCH, LTC or DASH?
BTC is the only guaranteed payout. Anything else is dependent upon the pool mining sufficient quantities of that coin. LTC is a special case where crackfoo manually buys coins for payouts. But if he's busy sometime you won't get a payout for a day or two. Ultimately though, unless notified otherwise, BTC is the only sure thing. |
|
|
|
When using Sniffdog miner (CPU only), it would constantly say Yescrypt is the most profitable by a huge margin. However, using the batch file method of mining, it would always mine m7m instead. Basically the pool/site is saying m7m is more profitable. If you look at the pool status table, it does indeed list m7m on top of Yescrypt.
So who's right? And why the discrepancy?
PS: I only have m7m and yescrypt in the password, no other algos. (-p c=BTC, yescrypt, m7m)
I'm guessing Sniffdog is actually taking your hash rates into account. Whereas your .bat file isn't. You should change your password to reflect your hash rates. Also, don't use spaces in your password. -p c=BTC,m7m=X,yescrypt=Y Where X is your m7m hash rate in MH/s, and Y is your yescrypt hash rate in kH/s. See the bottom of http://www.zpool.ca/site/multialgo for a concrete example. |
|
|
|
|
Hi, I would like to participate in the alpha!
CPU: Intel Core i5-4590 3.3GHz
RAM: 32GB DDR3-1600
Browser: Firefox or Chrome
Phone: Apple iPhone X
Thank you!
|
|
|
|
X17 is up again and I've been mining XVG a few hours.
Total Unpaid seems to be growing but not Balance. Perhaps consequently payouts aren't being made.
Am I wasting my time?
No, you're not wasting your time. XVG blocks are just taking a while to confirm. Which means you'll see up to an hour between the time your unpaid balance increases and when your balance increases for each block. |
|
|
|
5% is to cover the discrepancy of the price you're paid, and the price the coins actually get sold at because 98% of the time, when the pool sells the coins, they A) fill the order at the top of the market at the price your estimated at, then into the next which is lower, and then the next lower etc.... often times I'm loosing this % as the price by then would dip more than 5%.
No complaints here. Makes complete sense to me. This is the best pool I've used thus far. Much appreciated! |
|
|
|
This is probably asked everyday and I apologize, but does this pool take 20% of what you earn on top of the 2% fee? I can't find a solid answer anywhere.
2% for crackfoo + an additional 5% to pay for transaction fees. So, 7% total. |
|
|
|
Can I mine to a segwit address?
bc1qqfvs463h2rm90m3gh53ehkzx70masrg5nr6nxh
please advise.
Thanks,
Someone recently stated that their bc1 wallet address didn't work. Though if you have a Segwit address which begins with a "3," that should work. |
|
|
|
|
