Bitcoin Forum>Bitcoin>Development & Technical Discussion
Pages:
Author

Topic: Is this 16-of-16 multisig tx redeemable under current bitcoin implementation? - page 2. (Read 3294 times)

uminatsu
jr. member
Activity: 55
Merit: 2
Re: Is this 16-of-16 multisig tx redeemable under current bitcoin implementation?
March 24, 2014, 11:23:21 AM
#14
Quote from: piotr_n on March 24, 2014, 02:11:34 AM
You have "fd 04 a1", while it should be LSB: "fd a1 04"

Thanks! Unfortunately this means the signature will be invalid because the same endianness problem exists in my TX serialization code (for the prev tx scriptPubKey).

I'll go back fuddling my script a bit and try again (if nobody else claims it).
piotr_n
legendary
Activity: 2053
Merit: 1356
aka tonikt
Re: Is this 16-of-16 multisig tx redeemable under current bitcoin implementation?
March 24, 2014, 02:11:34 AM
#13
You have "fd 04 a1", while it should be LSB: "fd a1 04"

try this:
Code:
01000000010c0ff2174a66d60bc4316d6ceb07f4301bf076a8db2e887580
113e22ead8e62e00000000fda10400493046022100c9d96032febdad642b
e00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a774022100cc448b05
46ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf0149
3046022100c9d96032febdad642be00284ddfe71d9c42ee8b1111cecbb30
86bcbfd756a774022100cc448b0546ba2a7f7fc454d743a213ce7afd771d
fc7ef4d9456790fcb9af5ecf01493046022100c9d96032febdad642be002
84ddfe71d9c42ee8b1111cecbb3086bcbfd756a774022100cc448b0546ba
2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf01493046
022100c9d96032febdad642be00284ddfe71d9c42ee8b1111cecbb3086bc
bfd756a774022100cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7e
f4d9456790fcb9af5ecf01493046022100c9d96032febdad642be00284dd
fe71d9c42ee8b1111cecbb3086bcbfd756a774022100cc448b0546ba2a7f
7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf014930460221
00c9d96032febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd7
56a774022100cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9
456790fcb9af5ecf01493046022100c9d96032febdad642be00284ddfe71
d9c42ee8b1111cecbb3086bcbfd756a774022100cc448b0546ba2a7f7fc4
54d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf01493046022100c9
d96032febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a7
74022100cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d94567
90fcb9af5ecf01493046022100c9d96032febdad642be00284ddfe71d9c4
2ee8b1111cecbb3086bcbfd756a774022100cc448b0546ba2a7f7fc454d7
43a213ce7afd771dfc7ef4d9456790fcb9af5ecf01493046022100c9d960
32febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a77402
2100cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fc
b9af5ecf01493046022100c9d96032febdad642be00284ddfe71d9c42ee8
b1111cecbb3086bcbfd756a774022100cc448b0546ba2a7f7fc454d743a2
13ce7afd771dfc7ef4d9456790fcb9af5ecf01493046022100c9d96032fe
bdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a774022100
cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af
5ecf01493046022100c9d96032febdad642be00284ddfe71d9c42ee8b111
1cecbb3086bcbfd756a774022100cc448b0546ba2a7f7fc454d743a213ce
7afd771dfc7ef4d9456790fcb9af5ecf01493046022100c9d96032febdad
642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a774022100cc44
8b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf
01493046022100c9d96032febdad642be00284ddfe71d9c42ee8b1111cec
bb3086bcbfd756a774022100cc448b0546ba2a7f7fc454d743a213ce7afd
771dfc7ef4d9456790fcb9af5ecf01493046022100c9d96032febdad642b
e00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a774022100cc448b05
46ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf01ff
ffffff01d0dd0600000000001976a9147140b351f972295e98759a02c8f0
74bb7fd0c84b88ac00000000
uminatsu
jr. member
Activity: 55
Merit: 2
Re: Is this 16-of-16 multisig tx redeemable under current bitcoin implementation?
March 24, 2014, 12:57:29 AM
#12
So here's my solution to the 16-of-16 multisig... I know it is non-standard but the signature check should pass... but I'm simply getting "TX decode error" even from the Lightfood Hosting's node.

Anyone can tell what's wrong with this?

JSON:
{
    "hash": "51cbbcb7cf833b1406661d29f0c1a5f80c544b3bb1c28a9abba1881fd42f2df7",
    "ver": 1,
    "vin_sz": 1,
    "vout_sz": 1,
    "lock_time": 0,
    "in": [
        {
            "prev_out": {
                "hash": "2ee6d8ea223e118075882edba876f01b30f407eb6c6d31c40bd6664a17f20f0c",
                "n": "0"
            },
            "scriptSig": "OP_FALSE 3046022100c9d96032febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a77402210 0cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf01 3046022100c9d96032febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a77402210 0cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf01 3046022100c9d96032febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a77402210 0cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf01 3046022100c9d96032febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a77402210 0cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf01 3046022100c9d96032febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a77402210 0cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf01 3046022100c9d96032febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a77402210 0cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf01 3046022100c9d96032febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a77402210 0cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf01 3046022100c9d96032febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a77402210 0cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf01 3046022100c9d96032febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a77402210 0cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf01 3046022100c9d96032febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a77402210 0cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf01 3046022100c9d96032febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a77402210 0cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf01 3046022100c9d96032febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a77402210 0cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf01 3046022100c9d96032febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a77402210 0cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf01 3046022100c9d96032febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a77402210 0cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf01 3046022100c9d96032febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a77402210 0cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf01 3046022100c9d96032febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a77402210 0cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf01",
            "sequence": 4294967295
        }
    ],
    "out": [
        {
            "value": "0.00450000",
            "scriptPubKey": "OP_DUP OP_HASH160 7140b351f972295e98759a02c8f074bb7fd0c84b OP_EQUALVERIFY OP_CHECKSIG"
        }
    ]
}


Raw TX: 

01000000010c0ff2174a66d60bc4316d6ceb07f4301bf076a8db2e887580113e22ead8e62e00000 000fd04a100493046022100c9d96032febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbf d756a774022100cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf0 1493046022100c9d96032febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a77402 2100cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf01493046022 100c9d96032febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a774022100cc448b 0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf01493046022100c9d9603 2febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a774022100cc448b0546ba2a7f 7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf01493046022100c9d96032febdad642 be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a774022100cc448b0546ba2a7f7fc454d743 a213ce7afd771dfc7ef4d9456790fcb9af5ecf01493046022100c9d96032febdad642be00284ddf e71d9c42ee8b1111cecbb3086bcbfd756a774022100cc448b0546ba2a7f7fc454d743a213ce7afd 771dfc7ef4d9456790fcb9af5ecf01493046022100c9d96032febdad642be00284ddfe71d9c42ee 8b1111cecbb3086bcbfd756a774022100cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4 d9456790fcb9af5ecf01493046022100c9d96032febdad642be00284ddfe71d9c42ee8b1111cecb b3086bcbfd756a774022100cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fc b9af5ecf01493046022100c9d96032febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd 756a774022100cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf01 493046022100c9d96032febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a774022 100cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf014930460221 00c9d96032febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a774022100cc448b0 546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf01493046022100c9d96032 febdad642be00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a774022100cc448b0546ba2a7f7 fc454d743a213ce7afd771dfc7ef4d9456790fcb9af5ecf01493046022100c9d96032febdad642b e00284ddfe71d9c42ee8b1111cecbb3086bcbfd756a774022100cc448b0546ba2a7f7fc454d743a 213ce7afd771dfc7ef4d9456790fcb9af5ecf01493046022100c9d96032febdad642be00284ddfe 71d9c42ee8b1111cecbb3086bcbfd756a774022100cc448b0546ba2a7f7fc454d743a213ce7afd7 71dfc7ef4d9456790fcb9af5ecf01493046022100c9d96032febdad642be00284ddfe71d9c42ee8 b1111cecbb3086bcbfd756a774022100cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d 9456790fcb9af5ecf01493046022100c9d96032febdad642be00284ddfe71d9c42ee8b1111cecbb 3086bcbfd756a774022100cc448b0546ba2a7f7fc454d743a213ce7afd771dfc7ef4d9456790fcb 9af5ecf01ffffffff01d0dd0600000000001976a9147140b351f972295e98759a02c8f074bb7fd0 c84b88ac00000000

uminatsu
jr. member
Activity: 55
Merit: 2
Re: Is this 16-of-16 multisig tx redeemable under current bitcoin implementation?
March 24, 2014, 12:03:53 AM
#11
Quote from: amaclin on March 23, 2014, 11:56:11 PM
here is 20-of-20 solved (not by me unfortunately)

https://blockchain.info/tx/c4aaf7fbec7a9a079e670e50f6a672315451c7618814494ab1f89cf3fd97b3bb

WTH this is obviously way above the max scriptSig size... not even eligius accepts it  Huh
amaclin
legendary
Activity: 1260
Merit: 1019
Re: Is this 16-of-16 multisig tx redeemable under current bitcoin implementation?
March 23, 2014, 11:56:11 PM
#10
here is 20-of-20 solved (not by me unfortunately)

https://blockchain.info/tx/c4aaf7fbec7a9a079e670e50f6a672315451c7618814494ab1f89cf3fd97b3bb
uminatsu
jr. member
Activity: 55
Merit: 2
Re: Is this 16-of-16 multisig tx redeemable under current bitcoin implementation?
March 23, 2014, 11:52:39 PM
#9
Quote from: smooth on March 23, 2014, 11:37:14 PM
https://en.bitcoin.it/wiki/Free_transaction_relay_policy

Thank you very much!!! I've been able to relay non-standard raw tx to eligius.

Just got this 2-in-16 multisig solved:  Grin Grin

https://blockchain.info/tx/18f4c7059be729fb48d014d2a4a0658a8ba1d35798d42274691a117da91643b5
smooth
legendary
Activity: 2968
Merit: 1198
Re: Is this 16-of-16 multisig tx redeemable under current bitcoin implementation?
March 23, 2014, 11:37:14 PM
#8
https://en.bitcoin.it/wiki/Free_transaction_relay_policy
uminatsu
jr. member
Activity: 55
Merit: 2
Re: Is this 16-of-16 multisig tx redeemable under current bitcoin implementation?
March 23, 2014, 11:33:24 PM
#7
Quote from: piotr_n on March 23, 2014, 11:33:34 AM
except that non-standard does not mean unredeemable

well isn't it effectively unredeemable if no nodes will relay your tx?

of course if I control a pool or own some significant hashrate maybe that isn't such a problem.
piotr_n
legendary
Activity: 2053
Merit: 1356
aka tonikt
Re: Is this 16-of-16 multisig tx redeemable under current bitcoin implementation?
March 23, 2014, 11:33:34 AM
#6
except that non-standard does not mean unredeemable
uminatsu
jr. member
Activity: 55
Merit: 2
Re: Is this 16-of-16 multisig tx redeemable under current bitcoin implementation?
March 23, 2014, 09:55:32 AM
#5
Quote from: malevolent on March 23, 2014, 06:56:41 AM
https://github.com/bitcoin/bitcoin/blob/master/src/main.cpp#L519
https://github.com/bitcoin/bitcoin/blob/master/src/main.cpp#L3962

Are you going over the size limits?

Thanks! Yes each signature requires 0x49 (105) bytes of scriptSig. 16 copies would exceed the limit.

On the other hand the 16 signatures are identical. But OP_DUP is disallowed in scriptSig.

So it looks like that tx is unredeemable.
malevolent
legendary
Activity: 3472
Merit: 1724
Re: Is this 16-of-16 multisig tx redeemable under current bitcoin implementation?
March 23, 2014, 06:56:41 AM
#4
https://github.com/bitcoin/bitcoin/blob/master/src/main.cpp#L519
https://github.com/bitcoin/bitcoin/blob/master/src/main.cpp#L3962

Are you going over the size limits?
kjj
legendary
Activity: 1302
Merit: 1026
Re: Is this 16-of-16 multisig tx redeemable under current bitcoin implementation?
March 23, 2014, 06:48:46 AM
#3
Error messages from those services tend to suck badly.

Speaking from experience, I will say that writing a varint handler for a parser is easy, and I'd be amazed if more than one of those sites got it wrong.  More likely, they are passing it to bitcoind, which is rejecting it based on the IsStandard() check, and they simply report all errors as "parsing error"s.

But please post the raw transaction here so that we can check it.
piotr_n
legendary
Activity: 2053
Merit: 1356
aka tonikt
Re: Is this 16-of-16 multisig tx redeemable under current bitcoin implementation?
March 23, 2014, 02:45:32 AM
#2
can you post the raw transaction here?
uminatsu
jr. member
Activity: 55
Merit: 2
Re: Is this 16-of-16 multisig tx redeemable under current bitcoin implementation?
March 23, 2014, 02:08:18 AM
#1
I'm referring to this tx: https://blockchain.info/tx/2ee6d8ea223e118075882edba876f01b30f407eb6c6d31c40bd6664a17f20f0c

The problem I see is that the scriptSig necessary to redeem it must contain 16 identical copies of signatures. The result will be over 1KB and thus the scriptSig length field (a varint) will be using the 3-byte long format ("fd 04 90").

I tried to push such a tx to a few places such as blockchain.info, coinb.in, and webbtc.com/relay_tx, but all of the report "parsing error".

I'm pretty sure the parsing error is caused by the 3-byte varint format for scriptSig length (for example if I only include 3 copies of signatures then the scriptSig will be shorter than 0xfd bytes and thus using the 1-byte short varint format, then I'll get "invalid signature" error instead of a parsing error).
Pages:
Bitcoin Forum>Bitcoin>Development & Technical Discussion
Jump to: