Pages:
Author

Topic: Old P2SH debate thread - page 7. (Read 19705 times)

legendary
Activity: 2940
Merit: 1090
January 14, 2012, 04:50:48 AM
#37
SInce Gavin apparently does not have time to explain why Luke's solution is bad, can someone else maybe do so?

Or is everyone still flailing around trying to find something bad about it and maybe not having much success in doing so?

-MarkM-
rjk
sr. member
Activity: 448
Merit: 250
1ngldh
January 13, 2012, 10:04:06 PM
#36
finway, spam much? Lay off the crack, dude. That was like 5 posts in as many minutes.
legendary
Activity: 2576
Merit: 1186
January 13, 2012, 10:01:37 PM
#35
Gavin write OP_EVAL, you oppose.
Hmm, what? I didn't/don't oppose OP_EVAL.
You propose CHC, where's the code?
A few posts above yours.
Well, luke, if you implement your CHC idea before 1st Feb, maybe you'll get that monarchial powers .  Wink
I don't want monarchial powers. If people wanted a monarchial currency, they'd be using USD. I just don't want Bitcoin broken in a rush to get a new feature.
hero member
Activity: 714
Merit: 500
January 13, 2012, 09:20:34 PM
#34
While I disagree strongly with the monarchial powers being given to Gavin, that is not the basis for my objection to BIP 16 specifically.

Well, luke, if you implement your CHC idea before 1st Feb, maybe you'll get that monarchial powers .  Wink
hero member
Activity: 714
Merit: 500
January 13, 2012, 09:15:47 PM
#33
And piuk, implement your idea, and make a pull request.
hero member
Activity: 910
Merit: 1005
January 13, 2012, 09:14:11 PM
#32
I still haven't figured out how OP_CODEHASHCHECK is intended to work, so I wouldn't say that I'm a convert exactly.

Here is my explanation of luke's proposal as I understand it. Standard script template for a single key would be:

Quote
scriptPubKey: OP_CHECKHASHVERIFY
scriptSig: OP_CODESEPARATOR OP_CHECKSIG

1) Combine ScriptSig & ScriptPubKey

    OP_CODESEPARATOR OP_CHECKSIG OP_CHECKHASHVERIFY

2) is pushed onto the stack
   
   OP_CODESEPARATOR OP_CHECKSIG OP_CHECKHASHVERIFY

3) OP_CODESEPARATOR marks the beginning of the data to be hashed

    OP_CHECKSIG OP_CHECKHASHVERIFY

4) is pushed onto the stack

   OP_CHECKSIG OP_CHECKHASHVERIFY

5) OP_CHECKSIG validates and as normal

    OP_CHECKHASHVERIFY

6) is pushed onto the stack

   OP_CHECKHASHVERIFY

7) Everything from the marker that was set at OP_CODESEPARATOR up to stack -1 is hashed and compared with the top stack item e.g. . If equal the script is valid.

Advantages
- Like P2SH hash enables "pay to script" functionality - transfers multiSig fees from sender to receiver & reduces muliSig blockchain bloat.
- The script interprets as a script, no magic code path based on template matching.
- Static analysis without deserializing anything.
- Fairly simple, should be just as fast to get it in use as P2SH. Luke has coded it already.

Disadvantages
- Old clients validate almost nothing, with P2SH they at least check the matches the