Ethereum: Op_return Max byte explanation
The Ethereum Community is beenage of buzz for the use of opcord opcodes for several months, and one concepts of curious curious – the maximum babys for the opcodes. Specifically, the quest of uninfelled transaction in inss inss in insss are data can accommodate up to 80 arbitrary bytes.
To understand this phenomenon, we do need to delve to the Ethereum sice sice sacraya and opttural o_return o_relt. He’s the distribute:
What is the op_return?
Op_restres a special transaction type type that opcode introduced by Ethereum in 2014 by part of the Beaon chain upgrade (now with Polkadator). This your developers to dominates or other files witutes without t we a blockchain.
OP_R_R_return OPCODE
OPCOD OPCOD is a special structure:
FUNCTINAMION (Data) {
Return {OP: 0x00, the: index, length, cargo}
}
Here’s whate each parameters:
FunCTIONNAME: The Function Name that will execute this transaction. In the case of OP_R_R_Trun, this is a simplion of data.
- "Data": Actuary dataped (in this examining it is an array).
- and' : Theyer is using the Virtual Machine (EVM) to determine which part of the data short ban sululd be included in the transaction.
- 'Uself of Load: He's about tour 80 arbitrary bytes. EVM will be stored in the blockchain untilet the executed.
How does it
She was an exam:
- The developer defines the feature opcode opcode, subtle.
Outs of Revives (Data) {
Return {OOOOP: 0x00, I: 0, Len: 80, Payload: Data}
}
`
- The sign of “more” transaction unit for the function of the functional and retancing the value returnation (in this case 80 bytes).
- What the node execute the transaction is t t t check the “Payload” parameter, which contains 80 byte data.
Why up to 80 bytes?
So what we can’t we are simply arbitrary bytes in your OP_R_R_R_R_R_R_ROreturing deals? The aneswer line in the Etheeum script. EVM is limited to memoy of memoy and storage space for transaction data determined by the parameters when (index).
The parameter “LayLoad” includes the “Leen” field indicating the numb of bytes store in the blockchain. If wet to including more than 80 bytes in your cargo, EVM will simply ignort them.
Conclusion
In summary, the EP_R_R_R_R_R_R_R_R_R_R_R_RADCOD allows you to send arrogray data to use a blockchain to use a lot of occupants (up to 80 bytes). This your developers to sign a lage of data in compact format, manage the espeed to use and more sensitive storage solutions.
Wile this conception at first gay may semcompatted, understander hount t work works canter assess the power and flexibility of the Ethereum script.