Hello, Another of my crazy ideas:
When a transaction is first broadcast, it should include the hash of the block it wants to appear after, let's call it's basis block. That block can be anything the claimer wants; but it allows the miners to add this condition: the transactions outputs a new transaction claims must be before the new transaction's basis block. Consider this block chain fork: * -- * -- F -- * -- 1 -- 4 -- 5 \ * -- 2 -- 3 Let's say in block 2; I transfer coins from address A to Mt.Gox (or any other pooled-account online wallet). In block 1 I transfer credit from address A to address B. In block 3 I transfer credit from Mt.Gox's pool to address B. The chain at 3 races out first, but eventually the chain at 5 becomes "the one". If Mt.Gox are foolish enough to broadcast my withdrawl in 3; there is nothing to stop that same withdrawl making it into 4 (since it comes from a pooled fund address). Therefore Mt.Gox can't allow such a fast turnaround and must wait for six confirmations of 2 before allowing use of the funds. That is an inconvenience for all the honest users. With my proposed change, the Mt.Gox transaction broadcast at 3 would include "block 2" as its basis block. Therefore that transaction could never make it into block 4, as no miner will include a transaction based on block 2 in the block 4 chain. Mt.Gox is probably not a good example, as they have problems with fiat to deal with too. However, for other online wallet accounts it would allow faster acceptance of received funds, since there is no danger of loss should an attacker arrange a reorganisation. This basis block would be optional (implied by the input transactions if it isn't present); and would only need storing for the pending transactions, so no incompatible change is needed to the block format. Andy -- Dr Andy Parkins andypark...@gmail.com ------------------------------------------------------------------------------ Cloud Services Checklist: Pricing and Packaging Optimization This white paper is intended to serve as a reference, checklist and point of discussion for anyone considering optimizing the pricing and packaging model of a cloud services business. Read Now! http://www.accelacomm.com/jaw/sfnl/114/51491232/ _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development