Blockchain-Grundlagen
Nodes, clients and RPC providers
An app can use a chain without independently verifying all the data it displays.
Rechercheartikel und Referenzeinträge erscheinen auf Englisch. Die Navigation ist in sieben Sprachen verfügbar.
Verification and access
A node runs client software to participate in a network and handle chain data. In Ethereum's architecture, execution and consensus clients perform different roles. Running suitable node software allows independent validation under the protocol's rules.
Many applications instead send requests to an RPC provider. That is useful access infrastructure, but it adds a dependency between the application and the chain. Availability, response freshness and service policy can affect what the application shows.
A result needs a reference point
A wallet balance queried at one block can differ from a later response without either being fabricated. An investigation should retain the network and block reference wherever possible. Historical queries may require capabilities that a provider does not offer.
Compare the interface's claimed status with the underlying request and returned state. A failed RPC call does not prove the blockchain stopped, and an operating chain does not make every frontend usable. Continue with application dependencies and snapshot methods.