Author

Topic: Is there any limitation of P2SH? (Read 224 times)

legendary
Activity: 2870
Merit: 7490
Crypto Swap Exchange
January 12, 2020, 02:24:54 PM
#8
1. Maximum Bitcoin script is 40000 weight (or 10000 bytes before SegWit activiation)


If i remember right, P2SH redeem script is just 520 byte of space.

According to https://en.bitcoin.it/wiki/BIP_0016#520-byte_limitation_on_serialized_script_size, looks like 520 byte is maximum size of data that allowed to be pushed to the stack, not maximum script size.

I might be wrong since i'm not a developer.
sr. member
Activity: 377
Merit: 282
Finis coronat opus
January 12, 2020, 11:00:51 AM
#6
Could P2SH be quantum safe? As it is NOT based on public keys, which are weak with QC.

Not, this is not quantum safe the same as P2PKH. Because it based on public keys, you provide them in your scriptsig of redeem script.

1. Maximum Bitcoin script is 40000 weight (or 10000 bytes before SegWit activiation)


If i remember right, P2SH redeem script is just 520 byte of space.
sr. member
Activity: 279
Merit: 435
January 12, 2020, 10:35:53 AM
#5
Antiquated? I thought that P2SH is still the only way to do your own "creative" scripts that will be accepted by the network. Like the first implementation of segwit showed.
It's P2WSH, hence the point about BC1 addresses.
full member
Activity: 378
Merit: 197
January 12, 2020, 01:49:08 AM
#4
I just got this thought experiment in my head: can we live only with P2SH?

I like the succinct P2SH approach. It sounds perfect if all the scripts could be done in this way.

That made me have an interesting thought.
Could P2SH be quantum safe? As it is NOT based on public keys, which are weak with QC.

P2SH is antiquated now, not the best place to look for novel functionality.

Antiquated? I thought that P2SH is still the only way to do your own "creative" scripts that will be accepted by the network. Like the first implementation of segwith showed.
staff
Activity: 4326
Merit: 8951
January 11, 2020, 03:32:05 PM
#3
Multisigs with more than 15 participants is the most common...

But BC1 addresses don't have this limit, and if you're doing something big you'll want that in any case for efficiency sake.

P2SH is antiquated now, not the best place to look for novel functionality.

newbie
Activity: 8
Merit: 3
January 11, 2020, 06:42:06 AM
#2
Let's start with something obvious,
1. Maximum Bitcoin script is 40000 weight (or 10000 bytes before SegWit activiation)
2. Non-turing complete Opcode

I meant to compare P2SH with all other possible Bitcoin scripts. My bad, I did not express it clear enough.

The first point about script size still stands. Is there any good&useful example on-chain that uses many bytes close to the limits?

Thanks!
newbie
Activity: 8
Merit: 3
January 11, 2020, 03:26:06 AM
#1
I just got this thought experiment in my head: can we live only with P2SH?

I like the succinct P2SH approach. It sounds perfect if all the scripts could be done in this way.

Let's ignore segwit for this experiment Smiley
Jump to: