https://bitcointalksearch.org/topic/delayed-multisig-wallet-feasible-916622
It's generally a bad idea to post the exact same question in two different places.
You end up with a split conversation where nobody knows what has already been said.
Here's my response from your other thread:
You'll want to take the time to really think through all the possible situations and attacks that might be possible with something like this.
If a mining pool doesn't see the second signature in time, what happens when they eventually include the transaction in a block (after X blocks have occurred)?
How would this be different from a mining pool refusing to honor the second signature and including the transaction in a block (after X blocks), or would it be different?
Couldn't an attacker eat up all of the memory (or disk space) of the mining pools by generating these transactions as fast as they can so that the pools need to store millions of transactions that aren't ready to be confirmed, and then transmitting the "cancel" signature before the deadline?
If a mining pool doesn't see the second signature in time, what happens when they eventually include the transaction in a block (after X blocks have occurred)?
How would this be different from a mining pool refusing to honor the second signature and including the transaction in a block (after X blocks), or would it be different?
Couldn't an attacker eat up all of the memory (or disk space) of the mining pools by generating these transactions as fast as they can so that the pools need to store millions of transactions that aren't ready to be confirmed, and then transmitting the "cancel" signature before the deadline?
