Comparison of transaction sizes Bech32 and P2SH
When it comes to the size of the transaction in the Ethereum block chain, two popular alternatives have been used: BECH32 addresses and P2SH addresses. Both systems have their own strengths and weaknesses, which we will explore in this article.
What are Bech32 and P2SH?
BECH32 is a new standard to generate transactions that combine the benefits of BIP32 (Biproposal 32) and BIP27 (Biproposal 27). Use a compact format to represent addresses, making them smaller than their P2SH counterparts. In contrast, P2SH is another popular approach to reduce the transaction size.
P2SH vs Bech32: A technical comparison
| | P2SH | Bech32 |
| — | — | — |
|
Transaction size (bytes) | Typically around 200-250 | Smaller than 200-250, up to 30% smaller |
|
Merkle root generation | More complex process due to the largest Merkle tree size | Simpler process with less Merkle root calculations |
|
Limitation of block size | Limited by block size restriction | There is no direct limit imposed on BECH32 transactions |
As you can see, P2SH generally requires 200-250 bytes for a complete transaction. In contrast, the BECH32 addresses are significantly smaller, they usually vary from 30% to 100% less size. This reduction is due to the use of the BIP27 compact management format, which eliminates unnecessary data and reduces transmission overload.
What happens to the complexity of the transaction?
Bech32 transactions often require less Merkle root calculations than P2SH transactions, since they generate a single “address” instead of multiple directions (that is, script hashes). However, BECH32 can still incur some additional computing compact management format due to BIP27 compact format.
Conclusion:
While both BECH32 and P2SH are aimed at reducing the size of the transaction, Bech32 generally exceeds P2SH in terms of reduced transmission size. This makes it an attractive option for applications that prioritize speed over complexity. However, BECH32 can also incur additional computational overloads, which could be consideration for users with high performance networks.
In conclusion:
The next time you plan to send or receive Ethereum transactions, consider compensation between the BECH32 and P2SH addresses. Although BECH32 offers significant improvements in reducing the transaction size, its slightly more complex Merkle root generation process can compensate for some of these benefits.