Topic: [ANN][The Original Multipool - Scrypt/SHA256/Scrypt-N/X11] multipool.us - page 138. (Read 424232 times)

From his post, it sounds like he's taken the FTC algo and tweaked the numbers a bit.  I predict this will have approximately zero effect on our ability to profit from DGC.

It also looks like you are paying out incorrectly for WDC.
Block 600122 only paid out 32 WDC:
https://www.multipool.us/blockdetail.php?block=600122&curr=wdc
But the block reward was 63.36 WDC + 0.1 in fees:
http://wdc.cryptocoinexplorer.com/block/9061d90039d4cabefedd60ef593f43a74bf4c7887f913beb85351b9502457109

Same for 600112:
https://www.multipool.us/blockdetail.php?block=600112&curr=wdc
http://wdc.cryptocoinexplorer.com/block/95a2472abe1d27530cd0b09a7b01f83b5c1b56093c749636302c80ac099bcd3d

And all the other blocks since 600,000.

Also, DGC has a mandatory update:
https://bitcointalksearch.org/topic/dgc-digitalcoin-client-version-02-released-mandatory-update-24-hours-289818

They are hard-forking at block 476,280 (currently on block 418,821).  It will be about around the end of the month.
They are changing their retarget logic to limit the difficulty adjustments to deal with prof hopping.  I will dig into their code tomorrow to see exactly what they are doing.

WDC hit block 600,000.  The reward for each block is now 63.36 (decreasing by 1% every 20160 blocks).
It looks like your prof calculation still assumes 32.

Multi, can I request a "portfolio value" for a total at the bottoms of the places where it shows our earnings.

Similar to how you have the "24 hour Profit Snapshot", but also include... (Total mined value, estimate), and (Current holdings estimate), again, based on the current market values.

A bonus would be to show us the "highest value" and "lowest value" for the last 60 days, or 90, also. Thus, we get a good idea when is a good time to sell. Eg, knowing it is 0.000302 value is useless, if we earned it when it was 0.001233 at a high. However, knowing that high, we can assume that we should hold, if it is that low, at the moment.

Just thinking of things that could help to add more function, without causing too much more programming difficulty. (That could be done with simple PHP, or even javascript, if needed.)

Love that page by the way. The profit snapshot... would be better to see 24-hr, 7-day, and 1-month totals too. (Assumed off the "actual time mined", since in 24-hours, there may not actually be 24-hours of actual work.)

This is starting to feel like a professional investment and mining portfolio tool now. If it just had the ability to deposit, and trade coins among ourselves, internally... it would make a great multi-trader platform too. (For the coins it provides mining ability towards. Thinking of the coins I could care less about, which I would rather trade for bottlecaps, without having to go through a middle-man.)

CAP is still set at 200 confirms until we know for sure the blockchain is stable.

It's taking a while to process the WDC.  We found hundreds of blocks.

possible sha-256 multiport?

maybe its just me but stats for CAP and CGB are not moving in my account 

A whole 48 hours?  Well I've been mining here since April, and I've never seen us make 50% of LTC, and certainly not recently.  I'd like to see some numbers around your claim.

No, the problem is that when LTC profitability is high, a ton of hash switches over to it and the average block time goes down to 2 minutes or lower.

With only <50 MH dedicated on the LTC port, the 60 minute round time means almost nothing as far as profitability is concerned.

The low profitability was being caused by the following:

1. Badly tuned server parameters on the faster coins (WDC and DGC), which have been fixed
2. Approximately 20-25% lower than average profitability almost every time we move to LTC (I believe due to the hashrate jump on the larger pools, mentioned above)

So the problem is people are saying they aren't getting a good return when the pool switches to LTC? With the 60 minute round, there are a number of times we've moved on to mining something else...the LTC-direct miners find a block and we still have shares that get paid out despite not mining LTC when it was found. What's the difference? It's just a bummer that this all had to happen right when LTC was the most profitable it's been in weeks and I just found out now it was removed from multipool.

I ran a 48 hour test run using the Multipool option and I earned about 50% less money than I would if I mined Litecoin at it's current difficulty on it's own.  Upon watching the multipool option it was even mining coins that were more profitable than litecoin.  The bouncing back and forth between coins with the combination of PPLNS payment option is very inefficient for your miners.  It seems to be no different than losing out when you go Pool Hopping which PPLNS was designed to circumvent.  This pool would be good if it was PPS only.

Just set that up. I'll let them run for a while and see what happens (I left one rig at 1, set the other at 30, disabled no-submit-stale so I can see reject #'s, and restarted cgminer on both rigs). I'll report back in a little while with the comparison, .

--expiry|-E    Upper bound on how many seconds after getting work we consider a share from it stale (default: 120)

I think setting this to 1 might be... bad..

What happens if you set it to 30 or 60?

I enabled no-submit-stales about an hour prior to the image because I figured it'd help preserve bandwidth. On or off doesn't seem to impact the stale rate, it just increases/decreases the amount of time spent connecting and sending data. Prior to that, I had that option turned off and there was still the same flood of stales showing up all the time.

Love the idea.. great implementation.. wish you had all the SHA256 options as well as the scrypt..

Seems you have no-submit-stales enabled. If you combine it with low scan and expiry then oh-golly we have a pickle Check the settings.

Maybe I should clarify that my post was not a whine but clear hunger for knowledge Was not mining multipool at the time of your disabling. Thanks for the answer.

can you PM me your IP address so I can run a traceroute back to you from the pool server?

I have no idea on that one. Usually it does say a new block was detected. I'm not sure about the above though; that was something I noticed after the screenshot.

I did have a few rejects that said they were below the target difficulty as well. As far as I can tell, all of them in the R pile in the image were from that.