Quote
block transactions associated with wikileaks
1. There is a problem to detect transaction owner.2. If transaction is rolled back it can be repeated from another address binded to this wallet
MTGOX will not fail twice.
Topic: Probably solution for bitcoin developers after mtgox crash (Read 839 times)
2. If transaction is rolled back it can be repeated from another address binded to this wallet
MTGOX will not fail twice.
Than on a next day some gov agency will nicely ask developers to block transactions associated with wikileaks, SR and who knows what else, then on a next day blockchain will be forked and old bitcoin will be dead.
officially banned transactions.
That's a solution.
As i know crackers got many BTC (i don't want increase panic reposting this fact one more time)
Let's see what happens.
Mtgox has own wallet
Crackers has their own wallet
Obviously there is transaction between Mtgox wallet and Crackers wallet.
Now look at block chain
->block->block->block->block->block[fatal transaction]->block->block->block->block->block[transactions with crackers wallet]
We must prevent fatal transaction and all other transactions that will appear with that wallet.
We can cut block tree before transaction but this will crush all other markets because they based their bitocin<->real life money transactions on this branch of tree so they will have problem with their bitcoin balance (Coins that was sent will be back, coins that was recieved will be back too, and there is a happy situation then balance is approximately equal)
So cutting of tree is not good idea.
I propose not to break current chain. If all bitcoin client would reject some one transaction - transaction will become invalid.
So developers can update bitcoin client with list of officially banned transactions. This list can be updated only by developers. As updated client will recieve blocks it will automatically reject that transaction (or list of transactions).
// here comes probably a problem
Next transactions that will use bitcoins on that wallet became invalid automatically because all updated client at start make forced recheck and reject all transaction with wallet that have negative balance.
// and now a problem...
There is only one problem: wallet != address. So i don't understand how can detect that some address uses coins from some wallet.
I read documents about bitcoin inner structure but i understand not all. I don't understand mechanism of preventing/rejecting transactions that will make wallet balance negative.
But i believe there is some kind of preventing mechanism.
That's a solution.
As i know crackers got many BTC (i don't want increase panic reposting this fact one more time)
Let's see what happens.
Mtgox has own wallet
Crackers has their own wallet
Obviously there is transaction between Mtgox wallet and Crackers wallet.
Now look at block chain
->block->block->block->block->block[fatal transaction]->block->block->block->block->block[transactions with crackers wallet]
We must prevent fatal transaction and all other transactions that will appear with that wallet.
We can cut block tree before transaction but this will crush all other markets because they based their bitocin<->real life money transactions on this branch of tree so they will have problem with their bitcoin balance (Coins that was sent will be back, coins that was recieved will be back too, and there is a happy situation then balance is approximately equal)
So cutting of tree is not good idea.
I propose not to break current chain. If all bitcoin client would reject some one transaction - transaction will become invalid.
So developers can update bitcoin client with list of officially banned transactions. This list can be updated only by developers. As updated client will recieve blocks it will automatically reject that transaction (or list of transactions).
// here comes probably a problem
Next transactions that will use bitcoins on that wallet became invalid automatically because all updated client at start make forced recheck and reject all transaction with wallet that have negative balance.
// and now a problem...
There is only one problem: wallet != address. So i don't understand how can detect that some address uses coins from some wallet.
I read documents about bitcoin inner structure but i understand not all. I don't understand mechanism of preventing/rejecting transactions that will make wallet balance negative.
But i believe there is some kind of preventing mechanism.
Jump to: