{"type":"rich","version":"1.0","author_name":"npub1g6vxlp4e0nyhs2dqxxcryztyf5f5hyuaq93nw4r87zcnv0sdsa0qqsl5wd","author_url":"https://nostr.ae/npub1g6vxlp4e0nyhs2dqxxcryztyf5f5hyuaq93nw4r87zcnv0sdsa0qqsl5wd","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-07-20\n📝 Original message:On Mon, Jul 20, 2015 at 8:10 PM, Gavin Andresen via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e After deployment, the maximum serialized size of a transaction allowed\n\u003e in a block shall be 100,000 bytes.\n\u003e\n\nThis could render transactions with a locktime in the future as unspendable.\n\nIt is pretty low probability that someone has created a \u003e100kB locked\ntransaction though.\n\nIt violates the principle that no fork should render someone's coins\nunspendable.\n\nAt the cost of weakening the protection, the rule could be made to only\napply to version 2 transactions.\n\n\n*Specification*\n\n    The transaction version is increased to version two.\n\n    All coinbase transactions must be version two or higher.\n\n    If any of its parent transactions are version two or higher\n    then the transaction must be version two or higher.\n\n    The maximum serialized size of a version two transactions allowed in\n    a block is 100,000 bytes.\n\n\nAs time passes more and more of the UTXO set will be from version two\ntransactions.  To launch the attack, the attacker needs an historical UTXO\nentry.\n\nStandard software would create version two transactions even if all inputs\nwere version one.\n\nThe rule could be applied to all transactions most of the time, and have\ndaily blocks that allow legacy transactions.\n\n    This rule shall apply to version 1 transactions too unless the block\nheight is\n    a multiple of 100.\n\nAt the risk of encouraging feature creep, if the transaction size is being\nlimited, it would be useful to also limit the size of all its inputs.\n\nThis helps with fraud proofs and offline signing.\n\n\n*Specification*\n    The transaction version is increased to version two.\n\n    All coinbase transactions must be version two or higher.\n\n    If any of its parent transactions are version two or higher\n    then the transaction must be version two or higher.\n\n    The maximum serialized size of a version two transactions allowed in\n    a block is 100,000 bytes.\n\n    The maximum of the total serialized size of a version two transaction\nand all\n    of its parents allowed in a block shall be 200,000 bytes.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150720/ff1d1869/attachment.html\u003e"}