[bitcoin-dev] Bitcoin XT 0.11A
elombrozo at gmail.com
Mon Aug 17 12:33:14 UTC 2015
Or can’t you create a transaction that’s still within the op count and sig ops limits but is larger than 1MB?
> On Aug 17, 2015, at 5:29 AM, Andrew LeCody via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> wrote:
> Wouldn't that require a fork that lasts for more than 100 blocks?
> On Mon, Aug 17, 2015, 01:43 Peter Todd <pete at petertodd.org> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>> On 16 August 2015 17:03:35 GMT-07:00, Cameron Garnham via bitcoin-dev <
>> bitcoin-dev at lists.linuxfoundation.org> wrote:
>>> There are a few ways: here is my favorite (for the moment).
>>> 1. Spam the 8mb blocks with 1 Satoshi outputs to the brainwallet
>> Even more direct: use coinbase outputs of XT blocks to create those
>> outputs, as they can't by definition be on the Bitcoin chain.
>> If you can't get those, using coinbase outputs of Bitcoin blocks to create
>> "definitely Bitcoin-only" outputs, and then spend the inputs to those
>> transactions again on the XT chain. This isn't quite as good, as a big
>> reorg on the XT chain could in theory spend them, but it's a close second.
>> -----BEGIN PGP SIGNATURE-----
>> -----END PGP SIGNATURE-----
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
More information about the bitcoin-dev