Topic: Wonder who this solominer is? 88.6.216.9 - page 5. (Read 60498 times)
If empty blocks pose a threat, the bitcoin developers should consider to correct it, even if it isn't without dangers. Bitcoin is great but I'm sure it isn't perfect. A programmer can hardly think of every possible loophole/attack vector. I agree quick solutions should be avoided. Let's see and watch if it happens again. Is MM still mining, and if so, is he still extending his mining /or botnet operation?
so you can still mine empty block or not ?
Yes. There has been no protocol change which prohibits empty blocks.
Sounds to me that this transaction was intentionally created to put MM out of business for a while and to do exactly what it is doing to miners who didn't upgrade.
This. Miners who upgraded have been rewarded with "bonus" compensation split equally by hashing power. Negligent miners are facing financial consequences for their idiocy. I would like to thank who ever released the "killer tx".
Sounds to me that this transaction was intentionally created to put MM out of business for a while and to do exactly what it is doing to miners who didn't upgrade.
This. Miners who upgraded have been rewarded with "bonus" compensation split equally by hashing power (it just sucks I got 2GH/s offline right now). Negligent miners are facing financial consequences for their idiocy. I would like to thank who ever released the "killer tx".
This is the broken P2SH transaction that has single handedly caused 35 (and counting) blocks to orphan:
http://blockchain.info/tx-index/3618498/4005d6bea3a93fb72f006d23e2685b85069d270cb57d15f0c057ef2d5e3f78d2
In several cases, it actually caused several others to orphan because unupgraded miners built on top of the blocks that included this tx and created 2-4 block long forks that eventually lost the race.
Interesting, can you describe what is broken about it, and why it is continuing to cause issues?http://blockchain.info/tx-index/3618498/4005d6bea3a93fb72f006d23e2685b85069d270cb57d15f0c057ef2d5e3f78d2
In several cases, it actually caused several others to orphan because unupgraded miners built on top of the blocks that included this tx and created 2-4 block long forks that eventually lost the race.
I don't understand the broken-ness well enough to explain it, but the smarter-than-me developers in bitcoin-dev said the script is invalid in some subtle way that the current bitcoin versions recognize and reject and that old bitcoin versions don't recognize and think is valid.
It's still causing problems because every time a block that contains the transaction is orphaned, the old bitcoin versions see that this transaction still exists in their list of transactions that haven't yet made it in to a block and so they try to put it in a block again (which causes that block to get orphaned by the new bitcoin versions that reject the transaction and so the cycle repeats over and over).
Why? I love it. Tx processing nodes should be up to date. Period. Casual users don't need the latest code but miners form the tx processing backbone. Could you imagine VISA releasing a major critical upgrade and a month after the hard deadline some merchant banks still hadn't gotten around to upgrading their systems?
Miners need to take their role more seriously. If they can't be bothered to upgrade even when given a months of notice, provided a deadline, and warned they risk losing all revenue .... well IMHO they shouldn't be mining. Racking up huge losses may convince them to either a) take it more seriously or b) quit. Either one is fine by me. The network is made stronger.
I don't understand the broken-ness well enough to explain it, but the smarter-than-me developers in bitcoin-dev said the script is invalid in some subtle way that the current bitcoin versions recognize and reject and that old bitcoin versions don't recognize and think is valid.
Sounds to me that this transaction was intentionally created to put MM out of business for a while and to do exactly what it is doing to miners who didn't upgrade.
This is the broken P2SH transaction that has single handedly caused 35 (and counting) blocks to orphan:
http://blockchain.info/tx-index/3618498/4005d6bea3a93fb72f006d23e2685b85069d270cb57d15f0c057ef2d5e3f78d2
In several cases, it actually caused several others to orphan because unupgraded miners built on top of the blocks that included this tx and created 2-4 block long forks that eventually lost the race.
Interesting, can you describe what is broken about it, and why it is continuing to cause issues?http://blockchain.info/tx-index/3618498/4005d6bea3a93fb72f006d23e2685b85069d270cb57d15f0c057ef2d5e3f78d2
In several cases, it actually caused several others to orphan because unupgraded miners built on top of the blocks that included this tx and created 2-4 block long forks that eventually lost the race.
I don't understand the broken-ness well enough to explain it, but the smarter-than-me developers in bitcoin-dev said the script is invalid in some subtle way that the current bitcoin versions recognize and reject and that old bitcoin versions don't recognize and think is valid.
It's still causing problems because every time a block that contains the transaction is orphaned, the old bitcoin versions see that this transaction still exists in their list of transactions that haven't yet made it in to a block and so they try to put it in a block again (which causes that block to get orphaned by the new bitcoin versions that reject the transaction and so the cycle repeats over and over).
This is the broken P2SH transaction that has single handedly caused 35 (and counting) blocks to orphan:
http://blockchain.info/tx-index/3618498/4005d6bea3a93fb72f006d23e2685b85069d270cb57d15f0c057ef2d5e3f78d2
In several cases, it actually caused several others to orphan because unupgraded miners built on top of the blocks that included this tx and created 2-4 block long forks that eventually lost the race.
Interesting, can you describe what is broken about it, and why it is continuing to cause issues?http://blockchain.info/tx-index/3618498/4005d6bea3a93fb72f006d23e2685b85069d270cb57d15f0c057ef2d5e3f78d2
In several cases, it actually caused several others to orphan because unupgraded miners built on top of the blocks that included this tx and created 2-4 block long forks that eventually lost the race.
I don't understand the broken-ness well enough to explain it, but the smarter-than-me developers in bitcoin-dev said the script is invalid in some subtle way that the current bitcoin versions recognize and reject and that old bitcoin versions don't recognize and think is valid.
It's still causing problems because every time a block that contains the transaction is orphaned, the old bitcoin versions see that this transaction still exists in their list of transactions that haven't yet made it in to a block and so they try to put it in a block again (which causes that block to get orphaned by the new bitcoin versions that reject the transaction and so the cycle repeats over and over).
This is the broken P2SH transaction that has single handedly caused 35 (and counting) blocks to orphan:
http://blockchain.info/tx-index/3618498/4005d6bea3a93fb72f006d23e2685b85069d270cb57d15f0c057ef2d5e3f78d2
In several cases, it actually caused several others to orphan because unupgraded miners built on top of the blocks that included this tx and created 2-4 block long forks that eventually lost the race.
Interesting, can you describe what is broken about it, and why it is continuing to cause issues?http://blockchain.info/tx-index/3618498/4005d6bea3a93fb72f006d23e2685b85069d270cb57d15f0c057ef2d5e3f78d2
In several cases, it actually caused several others to orphan because unupgraded miners built on top of the blocks that included this tx and created 2-4 block long forks that eventually lost the race.
Orphans are primarily due to the enabling of BIP16, I suspect.
I thought this as well but there has hardly been any P2SH transactions.
510b5a44935109e249a704c2900aa9d8303166062e81d2ac852c965b6266dcee
d0636198ea55fadee5b4ccc07c85012db7d07c2d25790b3aec770c86617801c0
9ab59e2d4be16c470160eb9b9a9d9799eaf29af0461aea131e748659d806fa1a
658fc92061f1c4125d5cd1034eb8a1f09bfebd32a988d855eb7ee63689759a21
b0539a45de13b3e0403909b8bd1a555b8cbe45fd4e3f3fda76f3a5f52835c29d
9c08a4d78931342b37fd5f72900fb9983087e6f46c4a097d8a1f52c74e28eaf6
are the only ones ever.
This is the broken P2SH transaction that has single handedly caused 35 (and counting) blocks to orphan:
http://blockchain.info/tx-index/3618498/4005d6bea3a93fb72f006d23e2685b85069d270cb57d15f0c057ef2d5e3f78d2
In several cases, it actually caused several others to orphan because unupgraded miners built on top of the blocks that included this tx and created 2-4 block long forks that eventually lost the race.
Orphans are primarily due to the enabling of BIP16, I suspect.
I thought this as well but there has hardly been any P2SH transactions.
510b5a44935109e249a704c2900aa9d8303166062e81d2ac852c965b6266dcee
d0636198ea55fadee5b4ccc07c85012db7d07c2d25790b3aec770c86617801c0
9ab59e2d4be16c470160eb9b9a9d9799eaf29af0461aea131e748659d806fa1a
658fc92061f1c4125d5cd1034eb8a1f09bfebd32a988d855eb7ee63689759a21
b0539a45de13b3e0403909b8bd1a555b8cbe45fd4e3f3fda76f3a5f52835c29d
9c08a4d78931342b37fd5f72900fb9983087e6f46c4a097d8a1f52c74e28eaf6
are the only ones ever.
Is there a chart or table somewhere with orphans?
http://blockchain.info/orphaned-blocks
Orphans are primarily due to the enabling of BIP16, I suspect.
Yeah, but the question is if those include MMs. Is there a chart or table somewhere with orphans?
Lack of 0 tx blocks could be
a) mystery is getting orphaned out due to incompatible blocks
b) he started including txs
a+b is possible too.a) mystery is getting orphaned out due to incompatible blocks
b) he started including txs
I thought MM got caught in a sinkhole.
Lack of 0 tx blocks could be
a) mystery is getting orphaned out due to incompatible blocks
b) he started including txs
a+b is possible too. a) mystery is getting orphaned out due to incompatible blocks
b) he started including txs
Orphans are primarily due to the enabling of BIP16, I suspect.
While "a" is certainly possible we should have seen a 15% increase in avg block time which hasn't happened over the last 4 days.
There definitely has been a drop:
And lots of orphans. Though other pools made the same mistake, I do suspect MM dropped the ball.
Clipse nailed it.
Lack of 0 tx blocks could be
a) mystery is getting orphaned out due to incompatible blocks
b) he started including txs
While "a" is certainly possible we should have seen a 15% increase in avg block time which hasn't happened over the last 4 days.
Lack of 0 tx blocks could be
a) mystery is getting orphaned out due to incompatible blocks
b) he started including txs
While "a" is certainly possible we should have seen a 15% increase in avg block time which hasn't happened over the last 4 days.
I see no mystery blocks since the 1st April switch...
http://blockchain.info/ip-address/71.123.170.150
Guess they are having to recode their software?
http://blockchain.info/ip-address/71.123.170.150
Guess they are having to recode their software?
Im pretty sure he caught on to the forum posts and just started to accept TX's, hashrate for unknown remained(in fact grew slightly) since 1 April.
Also, the Myster Miner is running across multiple relays, that single IP means nothing.
I see no mystery blocks since the 1st April switch...
http://blockchain.info/ip-address/71.123.170.150
Guess they are having to recode their software?
http://blockchain.info/ip-address/71.123.170.150
Guess they are having to recode their software?
Jump to: