Ethereum: Understanding where transactions are stored during confirmation
When the Bitcoin customer begins the transaction and sends it to full connection nodes, the transaction undergoes a number of controls to guarantee his ID and validity. One of these controls provides for verification that the transaction has been confirmed in all participating nodes before they can be considered «confirmed» or «recognized». But where is this confirmation exactly? In this article, we will deepen the world of Ethereum and examine how transactions are stored during the confirmation process.
Ethereum architecture
The architecture of the Ethereum network consists of a decentralized peer-to-peer protocol, which allows nodes to communicate with each other. This P2P network consists of many types of nodes, including:
- Complete nodes : These are in every respect the nodes that store the entire blockchain Ethereum, including all transactions and past data.
- Light nodes
: These nodes maintain only a small part of blockchain, generally for specific purposes, such as mining or interaction with the applications of the third part (APPS).
- Infura
Nodes: Infura is a complete node service on demand that allows programmers to access Blockchain Ethereum in real time.
Confirmation process
When the Bitcoin customer begins the transaction and sends it to full connection nodes, the following steps follow:
- Hash transaction : Bitcoin customer generates an abbreviation for a transaction that acts as a unique identifier.
- Check transactions : Bitcoin client verifies that the sender has a sufficient balance of coins (currently 6 BTC) to cover the cost of the transaction.
- Transaction transaction : Bitcoin customer sends a transaction to all participating nodes on the network.
Where are the transactions archived during confirmation?
Now let’s face it: where exactly are the transactions stored during the confirmation process?
In Ethereum, transactions are archived in the network of complete nodes that maintain a copy of blockchain. Especially:
* Complete nodes : When the Bitcoin customer starts the transaction and sends it to full connection nodes, the transaction is stored on a local blockchain.
* Blockchain’s condition : The internal state also has complete nodes, which represents their current understanding of blockchain ethereum. This condition includes all transactions, sales and past data.
During the confirmation process, these nodes verify mutual nodes using a mechanism called «chain validation». When two or more nodes agree to the state of the chain, they can be considered «united» in one representation of an updated chain.
insight key
The key intuition is that the architecture of the Ethereum network enables decentralized memory and validation. While complete nodes store copies of local blockchain transactions during confirmation, the whole state of blockchain is also distributed through the network via the channels
Ethereum (ESCS) .
Ethereum (ESCS) state channels
ESC is a mechanism that allows many Ethereum nodes to agree the same data without the need for archiving in the local state. Instead, ESC allows nodes to update their internal status, sending updates to other nodes via the warranty agent network. This approach guarantees that any changes introduced in blockchain can be repeated via the network.
To sum up, when the Bitcoin customer begins the transaction and sends it to full connections in the Ethereum architecture, the transactions are stored in full nodes during the confirmation process. However, due to decentralized storage and validation mechanisms, such as ESC, the entire blockchain state is also distributed through the network, ensuring that all changes introduced can be effectively repeated.