Topic: SOLVED [Bitcoins.lc] Issue with invalid shares (10 BTC bounty) - page 3. (Read 16752 times)
So does suggest that in the transaction is getting incremented when nonce overflows but hash of the header is still getting sent out with it?
Summarizing discussion from IRC: the problem is reproducible in that getwork is returning the same midpoint for ~14% of requests but slightly different data.
Code:
[07:41] I'm seeing duplicate midstates
[07:42] 2 03dde4101cba6ba4d3a9d98bf6f074324b5ef4104e76257aa1f6e4374df10311
[07:42] 2 1b34e9976f563be464fbab7eb16bcae30aea5bc2428bb39cc168a1ea380fa4a0 2 203f9fc272d15f9a48b7f5c01252e14737302d104669a5a7ad40d5bf20065393
[07:42] (here's how I reproed)
[07:42] for i in `seq 0 99`; do (curl -d '{"method":"getwork","params":[],"id":1}' http://xxx:[email protected]:8080/ > /tmp/state${i} &) ; done
[07:42] awk -F\" '{print($10)}' /tmp/state*|sort|uniq -c|sort|grep -v '^ 1'
[08:10] here's one midstate/data
[08:10] "midstate":"befe8ff2573584e44cd82e1f818c7867d83c4d47104b9c504651945c4b9fb8fe","target":"ffffffffffffffffffffffffffffffffffffffffffffffffffffffff00000000","data":"00000001458bbc3db0fdb6d264cfcd58bec77b06259835f18f8df83400000c680000000010ef5d24e007b8bf8e73d82cd2d62c2c87ed0f2dc404c7ecfa8ea1b83734d8754df2024e1a1d932f00000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000"
[08:10] here's another midstate/data with same midstate, different data
[08:10] "midstate":"befe8ff2573584e44cd82e1f818c7867d83c4d47104b9c504651945c4b9fb8fe","target":"ffffffffffffffffffffffffffffffffffffffffffffffffffffffff00000000","data":"00000001458bbc3db0fdb6d264cfcd58bec77b06259835f18f8df83400000c680000000010ef5d24e007b8bf8e73d82cd2d62c2c87ed0f2dc404c7ecfa8ea1b83734d8754df202511a1d932f00000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000"
[08:10] notice df202511a1
[08:11] as opposed to df2024e1a1
[07:42]
[07:42]
[07:42]
[07:42]
[07:42]
[08:10]
[08:10]
[08:10]
[08:10]
[08:10]
[08:11]
No specific reason why that'd help, but it helps with the process to know that the bug happens regardless. But Im not doka.
Hi!
We're having serious problems with invalid shares (mainly duplicated work!).
I'm looking for one or more people to help us solve this issue asap.
We have a bounty of 10 BTC for a solution that works and permanently solves the problem
Please contact me on IRC (#bitcoins.lc) or [email protected]
I'll provide any information necessary.
Some general info:
* Invalid shares are to 90%+ duplicated work
* Using latest git version of both bitcoind and pushpoold
* MySQL (MariaDB (Aria)) storage for shares
* Lates memcache + dependencies from apt-get (Debian Squeeze)
* 32 bit OS.
We need help asap.
Regards, Jim
We're having serious problems with invalid shares (mainly duplicated work!).
I'm looking for one or more people to help us solve this issue asap.
We have a bounty of 10 BTC for a solution that works and permanently solves the problem
Please contact me on IRC (#bitcoins.lc) or [email protected]
I'll provide any information necessary.
Some general info:
* Invalid shares are to 90%+ duplicated work
* Using latest git version of both bitcoind and pushpoold
* MySQL (MariaDB (Aria)) storage for shares
* Lates memcache + dependencies from apt-get (Debian Squeeze)
* 32 bit OS.
We need help asap.
Regards, Jim
First thing(s) i'd suggest:
- - Grab the stable releases of both bitcoin and pushpool
- - How fast is the harddrive? If it's not writing to the database quick enough that might be causing stale shares
- - Move to a 64bit os
PM me when your online I can probably help.
I don't know much about the pushpool side of things 
This is happening to honest users. I'm one of them 
It looks like someone is trying to scam you by sending in one result from many locations, hoping to earn many shares for little work.
Or is this happening to honest users?
If you can't tell, I've signed up and sent one of my workers to you. Check your PMs for the IP and username.
Unfortunately, I'm going to be unavailable for about an hour, and it doesn't look like you can wait. Hopefully someone else can step in and help.
Edit: usernames are random by design
something to do with the way you allocate to workers from main user accounts? clients running more than one miner on the same worker? Those are my initial thoughts. Are you assigning work from a user account but accepting work from a worker account?
Worker's doing duplicated work.
See screenshot below.
It's from all workers, all over the pool.
Duplicated work, and we really can't figure out why or what to do about it.
See screenshot below.
It's from all workers, all over the pool.
Duplicated work, and we really can't figure out why or what to do about it.
Bumping, not because I can help, but because this pool is awesome and needs someone to earn their $300 worth of BTC!
What do you mean invalid shares? Like you think you found a block, but it isn't accepted by the network because the network found a block moments before you found yours? Or is someone sending duplicates of their low difficulty solutions to you?
Hi!
We're having serious problems with invalid shares (mainly duplicated work!).
I'm looking for one or more people to help us solve this issue asap.
We have a bounty of 10 BTC for a solution that works and permanently solves the problem
Please contact me on IRC (#bitcoins.lc) or [email protected]
I'll provide any information necessary.
Some general info:
* Invalid shares are to 90%+ duplicated work
* Using latest git version of both bitcoind and pushpoold
* MySQL (MariaDB (Aria)) storage for shares
* Lates memcache + dependencies from apt-get (Debian Squeeze)
* 32 bit OS.
We need help asap.
Regards, Jim
We're having serious problems with invalid shares (mainly duplicated work!).
I'm looking for one or more people to help us solve this issue asap.
We have a bounty of 10 BTC for a solution that works and permanently solves the problem
Please contact me on IRC (#bitcoins.lc) or [email protected]
I'll provide any information necessary.
Some general info:
* Invalid shares are to 90%+ duplicated work
* Using latest git version of both bitcoind and pushpoold
* MySQL (MariaDB (Aria)) storage for shares
* Lates memcache + dependencies from apt-get (Debian Squeeze)
* 32 bit OS.
We need help asap.
Regards, Jim
Jump to: