Is it possible to “mark” the output scenarios of Segwit with arbitrari bytes?
The Bitcoin network has separated the upgrade (segwit) network to improve the scaling and reduction of the operating time. However, as part of this implementation, for some features, such as P2SH-P2WPKH and SCRIPUBKEy operations will make specific bytes.
An area in which arbitrariness can cause problems is the release of output scripts, using Segwit scenarios. In this article, we will investigate whether it is possible to generate such labels with bytes arbitrari and discuss the potential consequences of bitcoin and security.
What is the scripubkey output?
Scripubkey (SPK) outputs are a way to withdraw data from Blockchain Bitcoin without creating a new operation. Instead, they are designed to be used as an entry into subsequent operations. To create a SK output, developers must generate a script that can be performed on the network.
What is p2sh-p2wpkh surgery?
There are two types of Bitcoin operations (Pay-Hash) and P2WPKH (private private private sector key). The first uses the script to confirm the operation, and the second is based on a private key to allow the operation.
Scenarii segwit
To install Segwit scenarios, developers must generate specific bytes models that can be used as SC output label. These labels help the net to determine what scripubkey exit should be considered to be launched and where it is intended to include in a new operation.
Bytes and arbitrary labeling
Let’s say we want to create an SPK output with byte arbitrari ready for its label. For example:
`C.
OP_UPUSHBYTES_8 41206162656C2E OP_DROP OP0 OP_UPUSHBYTES_20 <20 ...
`
In this case, OP_pushbytes_8 OPCode pushes the 8 -byte bytes model in a pile (in this example, a single byte), followed by the label 41206C6162656C2E, followed by other OP_DRO instructions to eliminate the current exit; The final instruction “OP_PUPUSTES_20 <20 ..." pushes 20 extra bytes at the top of the pile.
To generate this arbitrary label with arbitrari bytes, we must create a personalized scenario that can be used as a P2sh-P2WPKH operating tag. However, this will require significant changes in the Bitcoin basic code and the scenario.
Challenge
As you can see, the generation of arbitrary labels, as above is quite complicated, so you must be aware of the models, labels and bytes to generate Bitcoin scripts. This complexity results from the need to ensure that the label corresponds to the P2SH-P2WPKH surgery model, while compatible with various scenarios (for example, OP_PUPUS).
Potential consequences
Although theoretically it is possible to generate such arbitrary labels, there are several reasons why this approach is not practical in most scenarios:
- Network compatibility : Bitcoin scrip generation mechanisms and label manipulation ensure that outputs can only be noted according to specific models. Arbitrary labels can cause discrepancies and conflicts with existing transactions.
۲.
- Scaling : Trying to mark each SKK output with arbitrari would have a major impact on Bitcoin scales, as this will require additional processing and memory for each surgical output.
Conclusion
Although theoretically it is possible to generate labels as above, using arbitrari bytes, the complexity of this task exceeds any potential benefit.