[ANN][The Original Multipool - Scrypt/SHA256/Scrypt-N/X11] multipool.us

[zepadee]

Wow your Luckycoin pool efficiency really sucks. My rejects are through the roof too.

[flound1129]

Wow your Luckycoin pool efficiency really sucks. My rejects are through the roof too.

When a block is being found every 10 seconds it's hard to be 100% efficient..

[juhakall]

Wow your Luckycoin pool efficiency really sucks. My rejects are through the roof too.

When a block is being found every 10 seconds it's hard to be 100% efficient..

Having an EU pool server would greatly help with this.

[Behemot]

Wow your Luckycoin pool efficiency really sucks. My rejects are through the roof too.

When a block is being found every 10 seconds it's hard to be 100% efficient..

Having an EU pool server would greatly help with this.

I have been under the impression there is EU server…

Anyway, what expiry time should I set for litecoin? Heard it may help with stale shares. I am having problems lately with pool-indicated hashrate. Have too miners for LTC, one +-100 kH/s, the other with two cards aprox. 100+90 kH/s. Miner No. 1 works fine, almost no stales and such but on web it still shows lower hashrate.

Now miner No. 2 has lots of stales with worksize of 256 but CGmienr itself shows higher harate (aprox. 20 kH/s difference) over 128 worksize, which on the other hand reports many "accepted untracked stratum share from pool 0". But no matter the settigs, web shows only like 120-130 kH/s.

[Armchair Miner]

Hey there, currently on :7777 mining FTC and cgminer keeps reporting  

Rejected xxxxxxxx Diff..... (SHARE SUBMIT Ntime out of r

...repeatedly

what'up?

when I switch to another pool, things go back to normal.

EDIT: Actual coin mined @ the time was FTC

[B.T.Coin]

We've gotten 4 orphans so far, if we get 2 more I'm going to take FTC off the multiport.

I read on the feathercoin forum that they were under the impression that you pointed the multiport to FTC to help them counter the 51 attack.
Although it was an automatic switch, it could be a good idea.
Why not offer altcoin developers the possibility to manually point the multiport to their coin when they are 51 attacked?
Obviously they have to compensate you/us for that so we make at least what we would on another coin, but they have big pots of pre-mined coins anyway that they could use for that. It might be a win-win situation.

[TheFuneral]

Hey there, currently on :7777 mining FTC and cgminer keeps reporting  

Rejected xxxxxxxx Diff..... (SHARE SUBMIT Ntime out of r

...repeatedly

what'up?

when I switch to another pool, things go back to normal.

EDIT: Actual coin mined @ the time was FTC

I think were on the wrong chain

[tlr]

We've gotten 4 orphans so far, if we get 2 more I'm going to take FTC off the multiport.

I read on the feathercoin forum that they were under the impression that you pointed the multiport to FTC to help them counter the 51 attack.
Although it was an automatic switch, it could be a good idea.
Why not offer altcoin developers the possibility to manually point the multiport to their coin when they are 51 attacked?
Obviously they have to compensate you/us for that so we make at least what we would on another coin, but they have big pots of pre-mined coins anyway that they could use for that. It might be a win-win situation.

I like this idea, it's similar to something I read in a fictional story in Bitcoin Magazine a few months ago. Basically in the future there will be companies that insure against double spends, and they contract with emergency hashing providers that will mine for them on demand in case of double spends.

[hendo420]

Hey there, currently on :7777 mining FTC and cgminer keeps reporting  

Rejected xxxxxxxx Diff..... (SHARE SUBMIT Ntime out of r

...repeatedly

what'up?

when I switch to another pool, things go back to normal.

EDIT: Actual coin mined @ the time was FTC

I think were on the wrong chain

Same problem

[robkoz]

I have the same

[juhakall]

Loads of rejects here too, with the same reason. Looks like some clocks are out of sync.

[Armchair Miner]

Yeah, sure, why not, insurance against rare but disastrous events. It would be in the interest of insurance company to have systems on the ready to prevent them from having to pay out the claim.

We've gotten 4 orphans so far, if we get 2 more I'm going to take FTC off the multiport.

I read on the feathercoin forum that they were under the impression that you pointed the multiport to FTC to help them counter the 51 attack.
Although it was an automatic switch, it could be a good idea.
Why not offer altcoin developers the possibility to manually point the multiport to their coin when they are 51 attacked?
Obviously they have to compensate you/us for that so we make at least what we would on another coin, but they have big pots of pre-mined coins anyway that they could use for that. It might be a win-win situation.

I like this idea, it's similar to something I read in a fictional story in Bitcoin Magazine a few months ago. Basically in the future there will be companies that insure against double spends, and they contract with emergency hashing providers that will mine for them on demand in case of double spends.

[Armchair Miner]

An hour or more later, :7777 is on FTC again, and this

Rejected xxxxxxxx Diff..... (SHARE SUBMIT Ntime out of r

...repeatedly

comes up again. I'm not coming back until this is addressed.

[gnarl]

Same here, all scrypt mining seems to be down. All ftc shares rejected.
Trc is still chugging along though

[captainfuture]

what happens with my ftcs in my personal wallet? are they safe?

[erk]

Same here, all scrypt mining seems to be down. All ftc shares rejected.
Trc is still chugging along though

ARG and LTC working, NVC isn't. There was some sort of an attack apparently on FTC about 12hours ago, but that's well over and done with I believe, though it's hard to get info out of those guys, the want to do PR damage control more than discuss what's actually happening. FTC is currently disabled on Cryptsy.

[ozoner]

Not flound's fault, the guy has to sleep sometime! :-)

Wonder if there's any way to script around this situation - where if the pool's hashpower on the current coin is 0, something somewhere says "ok, switch to the second most valuable coin, something's wrong somewhere". Shrug.

[flound1129]

An hour or more later, :7777 is on FTC again, and this

Rejected xxxxxxxx Diff..... (SHARE SUBMIT Ntime out of r

...repeatedly

comes up again. I'm not coming back until this is addressed.

This is only happening on FTC..  I have taken FTC out of the multiport for now while I try to figure out what is going on..

We are on WDC now and it seems to be fine.

Always on the nights I fall asleep early...

[Armchair Miner]

True, on DGC and seems OK. Good that FTC is out. However, I have been mining some other FTC pool in the meantime and there seemed to be no problem except that the mining yield on new coins seems to go up and down constantly. Have yet to mature and cash out those FTC though.

Falling asleep early at night? That's nothing. Wait till you fall asleep early during the day.

An hour or more later, :7777 is on FTC again, and this

Rejected xxxxxxxx Diff..... (SHARE SUBMIT Ntime out of r

...repeatedly

comes up again. I'm not coming back until this is addressed.

This is only happening on FTC..  I have taken FTC out of the multiport for now while I try to figure out what is going on..

We are on WDC now and it seems to be fine.

Always on the nights I fall asleep early...

[flound1129]

Well this is apparently affecting at least one other FTC pool as well.  I have fixed the issue by patching stratum to not check ntime (seriously, who cares what time a share thinks it is as long as it is valid?) but I'm keeping FTC out of the multiport for now in case we're on the wrong chain or something.