Re: [Bitcoin-development] Proposal: relax the IsStandard rules for P2SH transactions
On Thu, Jun 19, 2014 at 09:54:31AM -0400, Gavin Andresen wrote: > RE: soft-forks bumping version numbers: > > Yes, we have consensus that is the way we will do it. I should probably > turn https://gist.github.com/gavinandresen/2355445 into an informational > BIP. Sounds like it could turn EvalScript() into a mess over time, but that's a long way away. Anyway a BIP will be useful. > RE: malleability: > > Orthogonal (but related) issue to IsStandard. > > Detecting Scripts that leave extra items on the stack will be done in a > different part of the code than the code addressed by this pull reques. No > need to execute the Script twice to figure out if it leaves extra stuff, > and the idea behind IsStandard is to get to a quick yes/no before running a > potentially expensive Script execution. Yeah, that's what I implemented in https://github.com/bitcoin/bitcoin/pull/4311 -- 'peter'[:-1]@petertodd.org 4f73d48c972aa30493526191aa009f95e4a71dcfbdca08b2 signature.asc Description: Digital signature -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems___ Bitcoin-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] Proposal: relax the IsStandard rules for P2SH transactions
RE: soft-forks bumping version numbers: Yes, we have consensus that is the way we will do it. I should probably turn https://gist.github.com/gavinandresen/2355445 into an informational BIP. RE: malleability: Orthogonal (but related) issue to IsStandard. Detecting Scripts that leave extra items on the stack will be done in a different part of the code than the code addressed by this pull reques. No need to execute the Script twice to figure out if it leaves extra stuff, and the idea behind IsStandard is to get to a quick yes/no before running a potentially expensive Script execution. -- -- Gavin Andresen Chief Scientist, Bitcoin Foundation https://www.bitcoinfoundation.org/ -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems___ Bitcoin-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] Proposal: relax the IsStandard rules for P2SH transactions
On Wed, Jun 18, 2014 at 08:52:22AM -0400, Gavin Andresen wrote: > RE: most of Peter Todd's comments: > > All of that should be separate pull requests. Big Honking Pull Requests > are harder to review and are more likely to be bike-shedded to death. Well, just doing one and not the rest isn't necessarily a good idea. The malleability protection definitely seems like a good idea, and has had quite a bit of review. > RE: not relaying/mining transactions with OP_NOPs so miners don't mine > up-version transactions that are invalid under future-new-rules: I'm not > convinced it is worth adding more code (more potential for bugs) to protect > against something that isn't going to happen because up-version > transactions are non-standard (due to version check) in any case. Do we have consensus that future soft-forks to add new opcodes will always be done in conjunction with a transaction nVersion bump? If so, then that's ok, if not, then we should have a whitelist. The code to restrict the opcodes to the softfork-safe subset is trivial, a GetOp() loop and a switch statement. It can always be removed later. Something that comes to mind is if we do always bump nVersion then OP_NOPx always will have a parallel "do-nothing" behavior, which means EvalScript() will always have to have code enabling that backwards compatible behavior. -- 'peter'[:-1]@petertodd.org 04e51d8d00eedb31ec1505d245f48960896b79f0e7193c2a signature.asc Description: Digital signature -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems___ Bitcoin-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] Proposal: relax the IsStandard rules for P2SH transactions
RE: most of Peter Todd's comments: All of that should be separate pull requests. Big Honking Pull Requests are harder to review and are more likely to be bike-shedded to death. RE: not relaying/mining transactions with OP_NOPs so miners don't mine up-version transactions that are invalid under future-new-rules: I'm not convinced it is worth adding more code (more potential for bugs) to protect against something that isn't going to happen because up-version transactions are non-standard (due to version check) in any case. In any case, lets make that a separate pull request. I'm going to take the lack of immediate "That's a Terrible Idea!" as rough consensus... -- -- Gavin Andresen Chief Scientist, Bitcoin Foundation https://www.bitcoinfoundation.org/ -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems___ Bitcoin-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] Proposal: relax the IsStandard rules for P2SH transactions
On Tue, Jun 17, 2014 at 9:40 PM, Gavin Andresen wrote: > Assuming there is rough consensus, I'll make this a pull request (see > https://github.com/gavinandresen/bitcoin-git/tree/relax_isstandard for code > changes). > > > > Now that we are finally starting to see the use of multi-signature and other > more complicated transaction forms in applications I think it is time to > open up the "IsStandard" transaction rules on the main Bitcoin network. Agreed! > Discussion > -- > Allowing any P2SH Script would allow an attacker to craft a single standard > transaction output that requires on the order of 200 ECDSA signature > checking operations to validate-- an order of magnitude more than is > currently allowed. Therefore I am proposing that we keep the current > 15-signature-checking-operations-per-transaction-output limit in place, but > allow any combination of enabled Script opcodes. So, for example, you might > have a P2SH Script that is redeemed with 2-of-2 OR 2-of-3 using: Soungs good to me - to lift the restrictions and increase flexibility, but also to be a careful and keep the DoS limits. > The reference implementation's wallet will still only recognize P2SH > transactions that use one of the standard transaction forms. To actually USE > a new transaction form will require specialized wallets or specialized > applications. That's of course completely separate. As we all know, most wallet innovation doesn't happen in the reference implementation wallet, and it should not be used as the guide here. Wladimir -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ Bitcoin-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] Proposal: relax the IsStandard rules for P2SH transactions
On Tue, Jun 17, 2014 at 03:40:36PM -0400, Gavin Andresen wrote: > Assuming there is rough consensus, I'll make this a pull request (see > https://github.com/gavinandresen/bitcoin-git/tree/relax_isstandard for code > changes). I'm also working on a very similar patch with some additional protections to ensure forwards compatibility during soft-fork upgrades and provide protections against transaction malleability. > Now that we are finally starting to see the use of multi-signature and > other more complicated transaction forms in applications I think it is time > to open up the "IsStandard" transaction rules on the main Bitcoin network. Agreed. > There are two main risks to doing this: > > 1. The risk that one of the seldom-used opcodes has a not-yet-discovered > chain-forking bug. I believe that risk to be very low; we have never seen > such a bug on the test network (where all transaction forms are allowed) > and have never found a bug after writing extensive unit tests. Agreed. The script execution code is probably in the 99.9th percentile of open source code in terms of code review. > 2. The risk of opening up a denial-of-service attack (either bloat the > blockchain or use an excessive amount of CPU time) via a very > expensive-to-store-or-verify transaction. This proposal does not entirely > eliminate IsStandard checks to mitigate the potential for DoS attacks. 3. The risk that non-upgraded miners produce invalid blocks after a soft-fork due to them mining transactions that are now invalid. 4. Transaction malleability. > Proposal > > Allow any Script containing 15 or fewer signature operations as a > pay-to-script-hash (P2SH) Script to be relayed and mined by the reference > implementation. > > This should be a simple change to the AreInputsStandard() method in the > reference implementation. In addition to these changes the soft-fork-safe patch I'm working on would do the following: a) Define an opcode whitelist of soft-fork-safe opcodes. This whitelist includes every opcode but the invalid opcodes, and most importantly, the OP_NOPx opcodes that may be redefined in a future soft-fork with new behavior. This rule, along with rejecting transations with unknown nVersion's, ensures that a miner still running an old version of Bitcoin Core will only mine transactions that the new version of Bitcoin Core considers valid. b) Consider scripts that leave extra items on the stack after execution to be non-standard. As per Pieter Wuille's BIP62 "Dealing with malleability" extra scriptSig pushes are a malleability source. If adding extra pushes causes a transaction to be invalid, scriptPubKeys will in most cases be automatically non-malleable. This change I've already submitted as a separate pull-req: https://github.com/bitcoin/bitcoin/pull/4311 I'd be happy to add the above to your existing patch and submit the pull-req for you. -- 'peter'[:-1]@petertodd.org 407e409a626b01bfb275cb88768ca74f3ea9bd87b2e7e1d9 signature.asc Description: Digital signature -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems___ Bitcoin-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bitcoin-development

