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 wrote: > > Wouldn't that require a fork that lasts for more than 100 blocks? > > On Mon, Aug 17, 2015, 01:43 Peter Todd wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA256 >> >> >> >> On 16 August 2015 17:03:35 GMT-07:00, Cameron Garnham via bitcoin-dev < >> bitcoin-dev@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 >>> 'BitcoinXT' >> >> 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----- >> >> iQE9BAEBCAAnIBxQZXRlciBUb2RkIDxwZXRlQHBldGVydG9kZC5vcmc+BQJV0YIS >> AAoJEMCF8hzn9Lnc47AH/R9EaGaa0xmD7qBODGUwX3SsDde7DMgO4t8X5GQ9uoaq >> qcjdnnvdeXjy5S39QdZFJjlH5bGn+BJy2wIxn0lMciKhEGIFOGeCUsMYEbgnOc03 >> cLuyYpxdfXe4Amoxf2mqADgBqkAckf4cX6bMm3XXg+v3XAby2llydIGIydTwGWYq >> 2KwXl9U9zm7UV8b5tJ7WmItCAcZAvTcSoX5SerOmPjjrmLtPTHThj8SfLTGAoWfT >> EXsSGkDBJ/9rJMms56FjciWsXHlB9pYK0a1sxh88PJluebqh99imDisJvATCVp2Z >> kZX1keZ1nyfG45jibgt6dlY97wU0n919SmQz0Tg6g90= >> =OD56 >> -----END PGP SIGNATURE----- >> >> > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev