Cameron Garnham [ARCHIVE] on Nostr: 📅 Original date posted:2015-08-16 📝 Original message:Since it was a game theory ...
📅 Original date posted:2015-08-16
📝 Original message:Since it was a game theory analysis. I will not address your other comments.
On 17/8/2015 7:22 AM, Andrew LeCody wrote:
>> 4. Setup a fork of Bitcoin XT that allows people to easily make a
> transaction only on the XT fork (while leaving the original BTC coins
> untouched).
>
> I doubt this is even possible.
Trivial.
There are a few ways: here is my favorite (for the moment).
1. Spam the 8mb blocks with 1 Satoshi outputs to the brainwallet 'BitcoinXT'
2. Let these spam tx be in BitcoinXT, however not Bitcoin (easily done).
3. Let the forked XT client includes a unspent dust output with any
transaction. Let the this client create 100 dust outputs for other
people to use in the same transaction.
This transaction will only be possible to confirm with Bitcoin XT. -
Leaving your Bitcoin coins untouched.
I particularly like this approach, as it is ironic as the spam is more
cheaply done with larger blocks.
Cam.
A quick political note:
https://en.wikipedia.org/wiki/Abstentionism
Hard forks are not something that is a democratic process. Thus
frustrating a false-democratic process is completely legitimate.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 213 bytes
Desc: OpenPGP digital signature
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150817/3b5b455b/attachment.sig>
📝 Original message:Since it was a game theory analysis. I will not address your other comments.
On 17/8/2015 7:22 AM, Andrew LeCody wrote:
>> 4. Setup a fork of Bitcoin XT that allows people to easily make a
> transaction only on the XT fork (while leaving the original BTC coins
> untouched).
>
> I doubt this is even possible.
Trivial.
There are a few ways: here is my favorite (for the moment).
1. Spam the 8mb blocks with 1 Satoshi outputs to the brainwallet 'BitcoinXT'
2. Let these spam tx be in BitcoinXT, however not Bitcoin (easily done).
3. Let the forked XT client includes a unspent dust output with any
transaction. Let the this client create 100 dust outputs for other
people to use in the same transaction.
This transaction will only be possible to confirm with Bitcoin XT. -
Leaving your Bitcoin coins untouched.
I particularly like this approach, as it is ironic as the spam is more
cheaply done with larger blocks.
Cam.
A quick political note:
https://en.wikipedia.org/wiki/Abstentionism
Hard forks are not something that is a democratic process. Thus
frustrating a false-democratic process is completely legitimate.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 213 bytes
Desc: OpenPGP digital signature
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150817/3b5b455b/attachment.sig>