Blockchain Technology

The cryptocurrency industry is plagued by fake information. There is too much noise, too much hype, and not enough facts. This makes it difficult for people to learn about the technology and make informed investment decisions.

There are a number of things that can be done to stop the spread of fake information in crypto. First, we need to be more critical of the information that we consume. Not everything that we read on the internet is true. We should always check the source of the information and verify it with other sources before we believe it. 👌

Second, we need to be more responsible with the information that we share. If we see something that is false, we should not share it. We should also be careful about making price predictions or expressing our opinions about specific projects. This can lead to people making bad investment decisions.

Finally, we need to support the organizations that are working to combat fake information in crypto. There are a number of organizations that are working to educate people about the technology and to provide accurate information. We can support these organizations by donating our time or money. 💰

By working together, we can stop the spread of fake information in crypto and help to build a more sustainable and trustworthy industry.

👉 Here are some additional tips for stopping the spread of fake information in crypto:

✅ Be skeptical of information that comes from anonymous sources.
✅ Do your own research before investing in any cryptocurrency.
✅ Only trust information from reputable sources.
✅ Report fake information to the appropriate authorities.

By following these tips, you can help to make the cryptocurrency industry a more informed and trustworthy place.

Connect with me ( Md. Mashiur Rahman ) for more updates 😊

The next Ethereum fork - Cancun - will be huge.

It is the first fork to pave the road toward sharding. There are many novelties proposed, so let's delve into the expected awesomeness.

First of all, the changes in this fork are not yet finalized and the inclusion of certain EIPs is still being discussed. Nevertheless, I can tell you what is decided for sure to build a solid ground for your further research.

- The biggest of all upgrades included is EIP-4844
EIP-4844 is a proposal that opens the gates for the future Ethereum data sharding. The proposal introduces a new type of transaction, blob transaction, that is used to anchor L2 rollups data. Blob transactions consist of 2 parts: a signed blob and a network wrapper. Signed blobs are regular transactions with an additional field, blob_versioned_hashes, that represents the hashes of KZG polynomial commitments to rollups data that are stored in blobs in a network wrapper. These hashes can be read by EVM via a new opcode DATAHASH (0x49), while the actual rollup data is inaccessible, as it is validated and stored in the consensus client alone.

In addition, the proposal presents a separate gas auction for blobs, which does not interfere with a conventional calldata gas auction. This enables much lower gas prices for rollups to be sent as blobs, not calldata, as they are sent right now.

In order to verify rollups, smart contracts will use a new cryptographic precompile (address(0x14)) that is designed to attest KZG proofs. Given points A and B, a KZG commitment, and a KZG proof, the precompile verifies that Polynomial(A) == B. This mechanism is similar to Merkle proofs, but much more powerful. It can be used to ensure that certain pieces of rollup blob data exist, without disclosing anything else. Point A will be equal to the index of the rollup data element and B to its actual bytes32 value.

- Another great upgrade is EIP-1153
The EIP introduces a new EVM data location - transient storage. Transient storage works like regular storage, however, it is erased after the transaction ex*****on. It can be accessed via 2 new opcodes TSTORE (0xb4) and TLOAD (0xb3) which both cost 100 gas. Transient storage is a long-awaited feature because it enables many amazing use cases to be implemented. For example, ultra-cheap reentrancy guards and single transaction ERC20 approvals.

- SELFDESTRUCT behavior changes in EIP-6780
SELFDESTRUCT opcode remains deprecated and its functionality gets reduced. If the contract destruction occurs separately from the transaction it is created in, SELFDESTRUCT will only send the remaining ether without actually destroying the contract (deleting bytecode, storage, and resetting nonce). Otherwise, the opcode functionality is unvaried. This change is crucial for the upcoming state Verkle trees, where the deletion of contract storage won't be possible.

© Artem Chystiakov