Topic: █▓▒░-< [ZPOOL.CA][BTC Multipool] The miners multipool >-░▒▓█ Paid 925+ BTC - page 58. (Read 217685 times)

ok so this is what i have right now not working just keeps cycling to the next algo and saying terminating workio then it moves to the next algo and says it again endless loop.



:start

ccminer -r 0 -a x11   -o stratum+tcp://mine.zpool.ca:3533 -u mybtcaddress -p x11,x13,x14,x15,quark,lyra2v2
ccminer -r 0 -a x13   -o stratum+tcp://mine.zpool.ca:3633 -u mybtcaddress -p x11,x13,x14,x15,quark,lyra2v2
ccminer -r 0 -a x15   -o stratum+tcp://mine.zpool.ca:3733 -u mybtcaddress -p x11,x13,x14,x15,quark,lyra2v2
ccminer -r 0 -a lyra2v2 -o stratum+tcp://mine.zpool.ca:4533 -u mybtcaddress -p x11,x13,x14,x15,quark,lyra2v2
ccminer -r 0 -a quark -o stratum+tcp://mine.zpool.ca:4033 -u mybtcaddress -p x11,x13,x14,x15,quark,lyra2v2

sleep 5000
goto start


i want to put more algos in and set the profit ratios.

whoops, it should be mine.zpool.ca. I think what most miners do, it put their Mhash rate in as their prof values.

i hate to be another one of those ppl but i'm stuck. i was mining with nicehash as i am a noob don't want to lose btc to them anymore. trying to get the auto switching thing to work but i am confused.
1. do i point at stratum+tcp://mine.zpool.ca: or stratum+tcp://yaamp.com:?
2. i want to set my own profit calculation in the password but am unsure of how to calculate the ratios as i do not have the base for scrypt as stated on http://www.zpool.ca/site/multialgo
i am using win 7 latest drivers from nvida and ccminer1-7-6neoscrypt version.

known hashrates whole rig.
x11 9 Mhash
x13 8.5 Mhash
Lyra2REv2 57 Mhash
Blake (2b) 2400 Mhash
NeoScrypt 1.3 Mhash
Quark 21 Mhash
Qubit 25 Mhash
Blake (14r) 3800 Mhash
Blake (XVC) 4500 Mhash

not sure if i can just modify the example on above site with the right algos and ports as written. currently just mining on neoscrypt with a simple bat file. Thank you in advance.

Sweet, seems to be working. Thanks!

I believe tpruvot will be putting out an update on git for lbry today sometime:

https://github.com/tpruvot/ccminer

Or here:

http://ccminer.org/preview/ccminer-1.8-lbry-rc.7z

I'm testing it now: vardiff doesn't seem to work.

EDIT: looks fixed now

PEOPLE please join the lbry algo as we have a TTF of 2 days :-D
lotta lotta profit but need more hashrate.

Ill do some testing when I get back home tonight.

Do you know if you can mine it on nvidia cards? Preferably with ccminer as the sgminer forks I've tried seem to freeze my computer within minutes.

Hopefully the ppl who wanted it will come and mine some as well.

Thanks

On there but it will take about 2-3 days to find a block at current hash rates.

lbry is loaded now but could use some testers.

I jumped off for a bit due to skein and nist5 being super profitable.. Let's crush some sib

Here I am! :-)
but are you gone?

{"name":"sha256","port":3333,"coins":43,"fees":2,"hashrate":"183172041305187","workers":162,"estimate_current":"0.00000139","estimate_last24h":"0.00000155","actual_last24h":"0.0016","rental_current":"0.00160940",

rental_current - pool can offer rent like NH
estimate_current - well, this is what you get if pool mines blocks next second
estimate_last24h - https://bitcointalksearch.org/topic/m.14285380 Also just noticed the "estimate_last24h" , is not the "last" 24h, it should be what we project in the next 24h... I'll fix that.
actual_last24h - you got it explained plus it needs to be divided by 1000

not sure if it was fixed(IMHO broken), but those were planned in original yaamp code to compare how much estimate_last24h deviated from actual_last24h, in above example it is (155/160 - 1)*100= -3,125%

OK, I made a few changes:

• I now use the numbers from the Zpool API. Until I understand what each number means, I take the lowest amongst all 4 numbers calculate with that, whichever it is.
• I disabled all coins except for Sha, Scrypt and X11, coins with decent amounts of orders on NH. L2v2 would be next as things look now, but I leave it disabled for now.
• I changed my config:

I still need some help with this one:

My setting is purely based on guesswork, I have no idea what kind of impact the diff will make, so I haven't got the slightest clue as to which number I should put in, and how I can calculate that. What do you think is reasonable?

I am actually doing that: 135% or more = buy, 125% or more is go ahead, 115% or less = throttle down and decrease as fast as I can, <115% for more than 15 minutes = sell. I decrease the price as often as I can without losing substantial hashrate, and if my hashrate is too low I increase to a level where it substantially grows while still making at least 125% profit. Also, right now I set it up so that I don't buy hashrate that can't complete an order in 24h. (That is, it looks for the NH price of enough hashrate to mine 0.01 BTC worth at that same price point, in 24h or less.)

As for the buy/sell hashrate fees: I know. It seems to be like this:

If you buy hashrate, you pay almost 4% fee. (That is, buy 0.01, get 0.0096). BUT: Once you remove an order, you get 3% of the remainder refunded. So in short, if you buy 0.01, you pay 0.0001 + 3% of what you use.


I'd really appreciate that! One advantage is that you can get those numbers in less than one second, whereas the page I used consistently takes 20 seconds to load.

I think if I use 140% (like ax66 suggests) I could use those numbers, even if they're a bit more volatile.

I still don't think 140% would get me to break even though, or I should fine-tune my sell vs decrease policy.

Come join me on testing the sib miner.  I only have 4.5 Mhash and look to find a block every 2.5 hours.  Could really use some backup

I forget what the actual amount is, but you all loose BTC when you cancel an order as well. How many did you cancel? I have a similar script, but you should also be adjusting your price to keep it on the lowest fringe.  I have bots running that I haven't put BTC in the accounts in months, they continue to earn. Not huge earnings, it is tricky with NH. They have their ups and downs, but in the end they continue to grow.

I haven't really looked into the API in a long time but looks like that actual_last24h need to be /1000

the names are a bit messed up, I'll need to go look and see what they were actually mean to say. dev won't change them since other apps are now using them...

I read almost the whole thread (yes!). I scripted a Zpool-based nicehash-order-manager, but I've lost quite a bit of cash, and I'm having a hard time figuring out what I'm missing.

Here's what I'm trying to do:

1. I pull the average rewards from ZPool algos from THIS PAGE. (Why that page? Those numbers seem more conservative and less volatile than what Zpool reports on its site, and I've read somewhere that ZPool has a tendency to have its averages a bit off.) I look at all numbers (i.e. current, last 2h, last 24h) and take the lowest as the 'right' one, just to be a bit conservative.

2. I pull the orders from Nicehash to see what hashrate goes for.

3. If the reported reward is more than 135% of the selling price of some substantial hashrate on nicehash, I buy the hashpower and point it towards zpool.

4. I poll the rewards every 60 seconds, and if they drop such that profit gets below 115%, I limit the hashrate on NH to the minimum, and if it doesn't come up after 15 minutes, I remove the order. When it rises again to above 125%, I set the limit back up to my calculated maximum (see below).

So, basically, I would think that 3% nicehash mining fee, 1% buying fee, 2% pool fee and 5% delta (spilled hashrate) adds up to 11% potentially loss to cover for, so I think the 15% is a reasonable selling-threshold.

I ran this script for about a day, I think it picked up about 10 orders, and while I was hoping to make some profit, I only found out that I lost about half what I started with. Bollocks!

But seriously, I'm a bit dumbfounded right now. So, what am I missing?

Here are the decisions I made that I'm uncertain about:

1. d=. And by max, I mean the max in the NH allowed range. I found out I had to specify it when Zpool gave an out-of-NH-range number, and when I set it to minimum, my hashrate delta was like 40%. I set it to the highest possible to prevent pool flooding, and now the hashrate delta stays nicely <5%. Is this totally idiotic? And if it is, how can I calculate what diff value I should provide? (As obviously I can't trust zpool to set them in NH's range)

2. I limit the orders to consume up to 35% of ZPool's total hashrate, and I have seen orders get there. I initially didn't think this could be a problem, but when I initially did 50%, I saw the rewards dropping significantly a few minutes later in some cases, so I thought those might be related to one another. I found out that I could take about a third without brining about major impact on the rewards. Maybe I'm wrong here though. Should I have only taken 10%? Or just a solid fixed amount based on the algo I'm trying to do?

3. I connect from both the EU and the US servers at Nicehash, whichever gives me the best rate. But EU-CA obviously has way more latency. Is that something to keep in mind, and should I just stick to Westhash?

4. I'm having trouble understanding the numbers at https://www.zpool.ca/api/status. For example: Estimate Last 24h: 0.00052364, Actual Last 24h: 0.5686. The difference in order of magnitude, is that just GHS vs THS? And is the estimate made 24h ago, or is this really an estimate of the next 24h? Also, what does rental_current mean? Is that the reward based on the last mined coin? And last, but not least, what attributes to the difference in the ZPool API and the page I mentioned above? (And which one do you guys think I should be using?)

5. Could it be possible that this loss can be attributed to a single algo? If so, is there any way I can still figure that out without having to test every damn algo again? The vast majority I've mined is X11, I've had multiple of those orders, all very profitable. I've also seen orders on Lyra2v2, a bit of Neoscrypt and an odd SHA256, it was highly profitable for about an hour today. All on the above policy. (Although I might stop doing Neoscrypt, because at times the minimum limit is already something like 20% of Zpool's hashrate)

6. Anything else / more numbers I should keep in consideration?

Sorry for all the things I don't quite understand yet! I'm passionate about learning all this stuff.

client thread gets created at stratum.cpp:344 by the stratum_thread which was created by main.


Looks the same to me. It's over my head now, you need someone who knows the application code.
Could be a race condition between threads due to some missing mutex.