Timeline for Is there a way to create a transaction that it can only be confirmed after another unrelated transaction has been confirmed?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 20, 2017 at 6:53 | comment | added | Nate Eldredge | The bribe transaction could itself include an OP_TRUE output, so if someone else wants to add a second bribe, they can spend the output of the first bribe; and they can include an OP_TRUE of their own and repeat ad infinitum. This gets awkward if the censored transaction is very popular, because the bribes may step on each other. Or, each one contains several OP_TRUE outputs; now the number of available places to hang a bribe grows exponentially. | |
| Jun 20, 2016 at 14:12 | vote | accept | Murch♦ | ||
| May 6, 2016 at 10:00 | history | bounty ended | Murch♦ | ||
| Apr 29, 2016 at 18:58 | history | edited | morsecoder | CC BY-SA 3.0 |
flip chronological order of A & B
|
| Apr 29, 2016 at 18:44 | history | edited | morsecoder | CC BY-SA 3.0 |
flip chronological order of A & B
|
| Apr 29, 2016 at 18:35 | history | answered | morsecoder | CC BY-SA 3.0 |