Are big capacity mutli-sig transactions still non-standard

[yakuza699]

Well the topic's name is kinda weird(was not sure how to form it) but what I meant is. Does x out of y mutli-sig transactions are still non-standard where's x is more than 2 and y is more than 3? If they are still non-standard when they will be standard?

[1538088786]

1538088786

[1538088786]

1538088786

[1538088786]

1538088786

[1538088786]

1538088786

[1538088786]

1538088786

[CIYAM]

Yes - I think that currently you can't do more than 2 out of 3 and still be a standard tx (and I have no idea when if ever that might change).

[yakuza699]

Yes - I think that currently you can't do more than 2 out of 3 and still be a standard tx (and I have no idea when if ever that might change).

Well that was sure a fast response(1 minute and 7 seconds) thank you. Also is Eligius,f2pool and BitcoinAffiliateNetwork are the only pools that mines those transactions?

[DannyHamilton]

Most multisig is now accomplished with P2SH.

As long as you are using compressed keys and using P2SH for your multisig, I believe Bitcoin 0.9 supports as "standard" up to 1-of-12, 2-of-10, 3-of-8 or 4-of-6 (due to a limitation of 500 bytes).

If on the other hand you are using the outdated OP_CHECKMUTISIG, then I think you are limited to a maximum 'y' of 3, and 'x' cannot exceed 'y'.

Yes - I think that currently you can't do more than 2 out of 3 and still be a standard tx (and I have no idea when if ever that might change).

Are you sure about that?  For some reason I though 3-of-3 was supported.

Also, as I pointed out you can exceed x-of-3 and still be "standard" as long as you use P2SH.

- snip -
If they are still non-standard when they will be standard?

Because larger multisig combinations can be accomplished with P2SH, I don't think there is any plan to increase the scope of OP_CHECKMULTISIG. I think the plan is to encourage multisig users to use P2SH transactions instead, and increase the size of the standard P2SH script.

The last I heard, they were looking into allowing "standard" P2SH multisig up to 15-of-15 for Bitcoin 0.10

[CIYAM]

Most multisig is now accomplished with P2SH.
...
The last I heard, they were looking into allowing "standard" P2SH multisig up to 15-of-15 for Bitcoin 0.10

If that is the case then I think there should be no issues.

[btchris]

The last I heard, they were looking into allowing "standard" P2SH multisig up to 15-of-15 for Bitcoin 0.10

There was an issue opened on the bitcoin.org repo (to update the increasingly impressive developer docs) stating that 15-of-15 P2SH transactions have been standard since 0.9.0, and it included this link to the bitcoin repo as evidence of a 1650 maximum byte scriptSig: https://github.com/bitcoin/bitcoin/blob/0.9/src/main.cpp#L543

So it appears that they're already standard unless something else is in the way (in which case I'm sure the bitcoin.org folk would want to know so they can correct the developer docs)...