📅 Original date posted:2015-08-17 📝 Original message:Or can’t you create a ...

Eric Lombrozo [ARCHIVE] /

npub1azv…2krq

2023-06-07 17:35:30

in reply to nevent1q…89pv

📅 Original date posted:2015-08-17
📝 Original message: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
>>> '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 at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150817/b131b04c/attachment.sig>;

Author Public Key

npub1azvhdrf9fu6n0tm7yez4j6zcxcedp2ct6nrcq3z74naqs7kgpk8s5t2krq

Show more details

Published at

2023-06-07 17:35:30

Kind type

1 Short Text Note

Event JSON

{ "id": "e4fb5d75a120faa5567fc2ae54cf92ba2c57bc59682d8dea153a9f91ea5d570c", "pubkey": "e899768d254f3537af7e26455968583632d0ab0bd4c780445eacfa087ac80d8f", "created_at": 1686159330, "kind": 1, "tags": [ [ "e", "c8deaa0aeee1e5d915e04ef7baf8b8074172a310b656820cd8767442ca514e56", "", "root" ], [ "e", "f9e1b6b0ce3105e7537e8d4a0b7e2baadbe98d86b14d080a56a4f318c3545173", "", "reply" ], [ "p", "7805cba4d18a8b44ba47c80fa67d382e69bb0a54f8841c3af251004ee632cac9" ] ], "content": "📅 Original date posted:2015-08-17\n📝 Original message:Or can’t you create a transaction that’s still within the op count and sig ops limits but is larger than 1MB?\n\n\u003e On Aug 17, 2015, at 5:29 AM, Andrew LeCody via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \n\u003e Wouldn't that require a fork that lasts for more than 100 blocks?\n\u003e \n\u003e On Mon, Aug 17, 2015, 01:43 Peter Todd \u003cpete at petertodd.org\u003e wrote:\n\u003e \n\u003e\u003e -----BEGIN PGP SIGNED MESSAGE-----\n\u003e\u003e Hash: SHA256\n\u003e\u003e \n\u003e\u003e \n\u003e\u003e \n\u003e\u003e On 16 August 2015 17:03:35 GMT-07:00, Cameron Garnham via bitcoin-dev \u003c\n\u003e\u003e bitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\u003e\u003e There are a few ways: here is my favorite (for the moment).\n\u003e\u003e\u003e \n\u003e\u003e\u003e 1. Spam the 8mb blocks with 1 Satoshi outputs to the brainwallet\n\u003e\u003e\u003e 'BitcoinXT'\n\u003e\u003e \n\u003e\u003e Even more direct: use coinbase outputs of XT blocks to create those\n\u003e\u003e outputs, as they can't by definition be on the Bitcoin chain.\n\u003e\u003e \n\u003e\u003e If you can't get those, using coinbase outputs of Bitcoin blocks to create\n\u003e\u003e \"definitely Bitcoin-only\" outputs, and then spend the inputs to those\n\u003e\u003e transactions again on the XT chain. This isn't quite as good, as a big\n\u003e\u003e reorg on the XT chain could in theory spend them, but it's a close second.\n\u003e\u003e -----BEGIN PGP SIGNATURE-----\n\u003e\u003e \n\u003e\u003e iQE9BAEBCAAnIBxQZXRlciBUb2RkIDxwZXRlQHBldGVydG9kZC5vcmc+BQJV0YIS\n\u003e\u003e AAoJEMCF8hzn9Lnc47AH/R9EaGaa0xmD7qBODGUwX3SsDde7DMgO4t8X5GQ9uoaq\n\u003e\u003e qcjdnnvdeXjy5S39QdZFJjlH5bGn+BJy2wIxn0lMciKhEGIFOGeCUsMYEbgnOc03\n\u003e\u003e cLuyYpxdfXe4Amoxf2mqADgBqkAckf4cX6bMm3XXg+v3XAby2llydIGIydTwGWYq\n\u003e\u003e 2KwXl9U9zm7UV8b5tJ7WmItCAcZAvTcSoX5SerOmPjjrmLtPTHThj8SfLTGAoWfT\n\u003e\u003e EXsSGkDBJ/9rJMms56FjciWsXHlB9pYK0a1sxh88PJluebqh99imDisJvATCVp2Z\n\u003e\u003e kZX1keZ1nyfG45jibgt6dlY97wU0n919SmQz0Tg6g90=\n\u003e\u003e =OD56\n\u003e\u003e -----END PGP SIGNATURE-----\n\u003e\u003e \n\u003e\u003e \n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 842 bytes\nDesc: Message signed with OpenPGP using GPGMail\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150817/b131b04c/attachment.sig\u003e", "sig": "8a23e1bb7c4bd25f3e8334be07b532d220f25aa6066c142b2b11d09cf7e98abb5bf96535423ad9ce6c92667f0ffe4332d55814481c22982a0e31e09d0b60d22c" }