Ethereum: is a public message at blockchain.info embedded in a real block chain?
In interacting with Ethereum, one of the most convenient features is the ability to add a public message to each event. This feature allows users to share more information about their events, such as details of sending or receiving. However, many people may wonder if this public message is embedded in the actual block chain itself.
To understand the answer to this question, let us dive into Ethereum’s internal activity and how to deal with messages in the Block Chain.
how ethereum is working
Ethereum blockchain is a decentralized, decentralized main book that records all the events in the network. It consists of blocks containing a list of events known as “Block”. Each Block has its own unique tag (also called “hash”) and is linked to previous blocks “merging” by the process.
Public Messages: Key Feature
One of the key features of ethereum to share users for more information about their events is the ability to add public messages. These messages can be up to 1024 characters long and are connected to each block as a “event hall”. The message itself has no specific restrictions on length or content.
is a public message embedded?
The question of whether Ethereum’s Blockchain -Up Public Message is really embedded instead of just attaching, has sparked Debate Among Developers and Users. To understand this better, let’s see how the messages are Shaped in the Block:
`Solidity
{
“Transactionhash”: Sha256 (
“0x … Event hash …”, // itself an event hash.
“Blocknumber”, // number of the quarryed block.
“Gaslims”, // a gas threshold specified in a transaction request.
“Value”, // the value sent at this event, which is expressed as a hexadecimal number.
“Nonce”, // A Random Integer used to prevent king -Selection Attacks
),
“Blockhash”: Sha256 (
“0x … Hash Block …”, // Hash Block Self.
“Time Stamp”, // Time Stamp on which the block was MINED.
“Gasprice”, // gas price for this trade.
“Nonce”, // Random Integer Used to Prevent King -Selecting Attacks
),
“TransactionCount”: 1,
“Txhash”: Sha256 (
“0x … transaction hash …”,
“Blocknumber”,
“Timestamp”,
“Gasprice”,
“sex offender”
In
}
`
From this output, it is clear that “transactionhash” includes not only the hash of the event, but also more information such as block number and timestamp. This includes gas price and nont values.
Conclusion
While some may claim that there is no direct, embedded location in the block chain (as it is connected to each block), others claim that it is truly “embedded” in the sense that its content is part of the transaction data structure. The content of the message may be seen greatly and is usually not encoded in the block chain, but Rather is only included in the field of the addition.
The actual implementation may depend on how the messages are Shaped into the Blocks, but at the basic level, for the additional information given to users through this feature should indeed be immersed in some form inside the block structure.