Just to note this isnt the Bytecoin on cryptsy or any of the exchanges so afaik it is untradable on exchanges

yes he was hacked last week but that is not his full stash. His remainder is in cold storage.

I'm not completely sure. But I think they had something to do with satosji dice. And also greedy mining. Not mining transactions without fees

altexplorer.net i got joeyjones to add i0c

i will repeat again. DIFF1 is not generic it depends on the specific algorithm. it CANNOT be guessed. so until someone figures out what the diff should be for x11 you will still be exploitable

Had to give a bump here.

Stratum is NOT flawed. The pool operators are using an inappropriate DIFF1 and so that is why they are experiencing these issues. Scrypt and SHA256 are not affected (Give-Me-Coins pool helped me test it) on 2 open source forks of stratum compatible pool software (stratum-mining and eloipool)

Ahmed

the way of the trade im afraid. sadly cannot share everything i would like. too many op's are spoiled for choice with the current stratum :p

they are and the stratum and sha algorithm's do. these idiot's using stratum without checking the diff1 are at fault and its their responability. it 100% isnt a fault in my code at all. i take responsability for scrypt and sha any other algo is up the user as i dont know myself how to calc what a diff1 value should be

Heres how it works

Miner connects to pool, authorises and subscribes for work

Miner conencts sets their own diff and starts doing work. work is calculated by a DIFF1. (what the difficulty of a difficulty 1 share should be). Now if a miner hashes away at their hardcoded diff and ignores the diff the pool is sending. so the pool would increase their difficulty on the pools end to the max set (depends on the pool) and the pool wouldnt know that the miner is ignoring it. since the diff1 is wrong on the pool the pool would accept the difficulty the miner says it is and wouldnt check what the actual difficulty is.

This means stratum thinks the diff == (theoretic scenario of 2048) while the miner is submitting a diff of (theoretic scenario of 0.001) so the miner will get paid for hundreds of shares with a diff of 2048 when really it should be 0.001

Okay back.

Done a test on stratum-mining and eloipool using the exploit documented above.
Stratum-mining and eloipool in scrypt mode both reject these shares.
This makes it almost 99% sure that it is a diff1 error and stratum-mining IS NOT at fault. the pool operator's are at fault for not using the correct diff1's for the algorithm

Okay back.

Done a test on stratum-mining and eloipool using the exploit documented above.
Stratum-mining and eloipool in scrypt mode both reject these shares.
This makes it almost 99% sure that it is a diff1 error and stratum-mining IS NOT at fault. the pool operator's are at fault for not using the correct diff1's for the algorithm

sorry i wont be sharing my code as its all hardcoded and messy into my private fork of stratum

hmmm. thats what i would expect. tbqh darkcoin i couldnt give a crap about. its an unsupported scenario as i dont officially have it in the CryptoExpert repo. so any flaws are up to the OP. so atm i only care about:

Scrypt/ScryptJane (Uses Pooler's diff1)
Sha256 (Slush's Diff1)
Quark (PR from someone)
Skein (Uses SHA256 Diff1)

problem is what should the value be  

the big problem her is how to work it out. the only person i know who could do it is pooler.

my personal belief. it affects other algorithm's where we do not have an accurate diff1

how do you know for sure? pooler patched litecoin already befor

Do you know if this affects litecoin pools

finally completed the groestl algo module. (man that was tough) anyone here up for testing plz pm me and if possible jump on #cryptopools on freenode IRC.

Ahmed

well. it doesnt even look to be based off bitcoin. (might be a multicoin fork though?) so i'd kind of say our's is the real coin. i doubt the other one is even used at all