[POOL][Scrypt][Scrypt-N][X11] Profit switching pool - wafflepool.com

[utahjohn]

can anyone verify this block found on wafflepool?

judgecoin    2014-07-10 03:32:59    00000000016303f9c21c032a6bb25021be5e0d1d266a75a7e2002ad019e65273    500.00000000    immature

I searched blockchain explorer and nothing.  It would appear they are on wrong wallet.

[utahjohn]

Ouch looks like PW shitcanned the orphans already ... No announce yet so I wait ...

[DrunkenDonkey]

@Waffle, this is happening, happened and will happen, have you considered having someone trusty, utahjohn for example, giving the ability to disable single coin for a time and raising special notification for you? So the switcher will consider the other coins for a while?

[utahjohn]

@Waffle, this is happening, happened and will happen, have you considered having someone trusty, utahjohn for example, giving the ability to disable single coin for a time and raising special notification for you? So the switcher will consider the other coins for a while?

I would not even consider that LOL, but it would be nice to have a way to send an immediate alert to PW. 

[utahjohn]

I've already raised my irritation about "Ninja Hard-fork" with Judge ... quietly ignored LOL

[DrunkenDonkey]

I would not even consider that LOL, but it would be nice to have a way to send an immediate alert to PW. 

Well you are well active, notably active when pw is sleeping (different time zones?) and gives the impression you follow the stuff. Ofc there are more candidates, PW was joking with someone that he have to hire him or pay for support Such events don't happen often, but still happen, not sure if PW will be open to some sort of a wake up type of alert, probably won't embrace it, but a very very restricted ability to disable a single coin for max of say 8 hours, login based ofc, that only 1 person other than PW have access to might help mitigate the "sorry folks, we have been on the wrong fork all night" issues.

[utahjohn]

I would not even consider that LOL, but it would be nice to have a way to send an immediate alert to PW. 

Well you are well active, notably active when pw is sleeping (different time zones?) and gives the impression you follow the stuff. Ofc there are more candidates, PW was joking with someone that he have to hire him or pay for support Such events don't happen often, but still happen, not sure if PW will be open to some sort of a wake up type of alert, probably won't embrace it, but a very very restricted ability to disable a single coin for max of say 8 hours, login based ofc, that only 1 person other than PW have access to might help mitigate the "sorry folks, we have been on the wrong fork all night" issues.

Well if I were on payroll hmmm I'd consider it.  Yes I'm active all over threads. I don't sleep much.

[suchmoon]

I've already raised my irritation about "Ninja Hard-fork" with Judge ... quietly ignored LOL

So what was the "heads-up" time for this one? I tried digging through the judge thread but it's hard to figure out exactly when the fork was announced or how it was announced. Github says last commit was "2 days ago" so apparently 24-48 hours before the fork.

[atomicchaos]

It's the risk we take for larger reward. I don't expect Pool Waffle to be completely in tune with all these little Alts and their decisions, assuming it happens infrequently. It's similar to playing penny stocks, as they can be very unpredictable.

Running a pool takes a lot more than is seen by most, especially one of this size. I think we share responsibility in keeping in tune with what we are mining, and many thanks to Utahjohn for the heads up, I was nearly completed in switching all of my rigs over to X13 when I saw the message, and then went back to X11 (which is top dog again now). At least I have the capability now, and all rigs are loaded with SGminer 5.0 for auto-switching algorithms if I could figure out how to get it to play better with CGwatcher like some have already done.

[atomicchaos]

I just noticed Judgecoin being mined again, I'm already back on X11, but was curious if it was on the correct chain now.

[utahjohn]

Would someone confirm this block found on Wafflepool:
judgecoin    2014-07-10 13:41:04    00000000006be1c6d9c46d62606007e21a727d121852e682b2e32e782177d964    500.00000000    immature
I am on wallet 1.1.0 and get block# 6964 with 24 confirmations.

Just checked again:

08:12:25
?
getblock 00000000006be1c6d9c46d62606007e21a727d121852e682b2e32e782177d964


08:12:25
?
{
"hash" : "00000000006be1c6d9c46d62606007e21a727d121852e682b2e32e782177d964",
"confirmations" : 38,
"size" : 212,
"height" : 6964,
"version" : 6,
"merkleroot" : "a32b8291e81915d8d66278697027e416d80eb95f6d87a26d00551ba10d615686",
"mint" : 500.00000000,
"time" : 1404999664,
"nonce" : 7727659,
"bits" : "1c01e486",
"difficulty" : 135.25661491,
"blocktrust" : "874238c5f7",
"chaintrust" : "20a230b56d8d71",
"previousblockhash" : "63831504a23d5e203b3c3efc5dbe6a65dbda34f661919707ea1405e1a4daaf01",
"nextblockhash" : "0000000001d5cf55ca070985b08317f9e7a576c33f28224191f92db8c4d282b6",
"flags" : "proof-of-work stake-modifier",
"proofhash" : "00000000006be1c6d9c46d62606007e21a727d121852e682b2e32e782177d964",
"entropybit" : 0,
"modifier" : "480518df525ab6f6",
"modifierchecksum" : "c6d1d62c",
"tx" : [
"a32b8291e81915d8d66278697027e416d80eb95f6d87a26d00551ba10d615686"
]
}

I would venture a guess that PW has corrected problem and is now on correct blockchain.  ALthough this is not an "official" announce.  I'll move 1 miner back to X13.

[utahjohn]

OK I am seeing payouts on Judgecoin, unofficial "Greenlight" on X13

[atomicchaos]

OK I am seeing payouts on Judgecoin, unofficial "Greenlight" on X13

Meanwhile X11 is more profitable at the moment.

[utahjohn]

OK I am seeing payouts on Judgecoin, unofficial "Greenlight" on X13

Meanwhile X11 is more profitable at the moment.

Yep, I'm on both and Diamondcoin (groestl) also atm
Judgecoin PoW is a short time so take advantage before it runs out

[madian]

OK I am seeing payouts on Judgecoin, unofficial "Greenlight" on X13

Meanwhile X11 is more profitable at the moment.

Side calculus, I assume that for your farm of (if I understood correctly) mainly 280x you have a ~6x scrypt factor for x11 and a ~4x scrypt for x13 like I have with my 290s. Basically, since WP marks them as 4x and 3.5x, the vsLTC has to be at least 30% higher for x13 over x11 to be worth mining.

Coupling this with the fact that the reported BTC/MHd or the vsLTC figure are at least 12 hours old it becomes difficult to anticipate the moment we need to switch algo. For example, now it feels like the X13 is more profitable since the profit is rising while on X11 it's falling and since what we mine now gets converted at a later time I think basing our switch on trends and not fixed actual numbers might be better.

[utahjohn]

OK I am seeing payouts on Judgecoin, unofficial "Greenlight" on X13

Meanwhile X11 is more profitable at the moment.

Side calculus, I assume that for your farm of (if I understood correctly) mainly 280x you have a ~6x scrypt factor for x11 and a ~4x scrypt for x13 like I have with my 290s. Basically, since WP marks them as 4x and 3.5x, the vsLTC has to be at least 30% higher for x13 over x11 to be worth mining.

Coupling this with the fact that the reported BTC/MHd or the vsLTC figure are at least 12 hours old it becomes difficult to anticipate the moment we need to switch algo. For example, now it feels like the X13 is more profitable since the profit is rising while on X11 it's falling and since what we mine now gets converted at a later time I think basing our switch on trends and not fixed actual numbers might be better.

Exactly   I watch market trends and not exclusively reported profits as these are just guidelines

[chadwickx16]

OK I am seeing payouts on Judgecoin, unofficial "Greenlight" on X13

Meanwhile X11 is more profitable at the moment.

Side calculus, I assume that for your farm of (if I understood correctly) mainly 280x you have a ~6x scrypt factor for x11 and a ~4x scrypt for x13 like I have with my 290s. Basically, since WP marks them as 4x and 3.5x, the vsLTC has to be at least 30% higher for x13 over x11 to be worth mining.

Coupling this with the fact that the reported BTC/MHd or the vsLTC figure are at least 12 hours old it becomes difficult to anticipate the moment we need to switch algo. For example, now it feels like the X13 is more profitable since the profit is rising while on X11 it's falling and since what we mine now gets converted at a later time I think basing our switch on trends and not fixed actual numbers might be better.

Exactly   I watch market trends and not exclusively reported profits as these are just guidelines

Can I get a utahjohn algo switcher?

[utahjohn]

LOL I don't sleep much just take 1-2 hr naps and monitor what's going on   I especially watch newly introduced coins to see what's going on with them.

[utahjohn]

Can I get a utahjohn algo switcher?

I have sugested possible methods to PW including a voting system to influence coin switcher ...

[chadwickx16]

Can I get a utahjohn algo switcher?

I have sugested possible methods to PW including a voting system to influence coin switcher ...

Yeah, I just switched to Sgminer5 and I love it, I was against the algoswitcher here, but now I am for it.