Timeline for Does ethereum clients return false data if someone manipulate local blockchain data?

Current License: CC BY-SA 3.0

8 events

when toggle format	what		by	license	comment
Aug 15, 2016 at 16:15	comment	added	T9b		@SatoshiNakanishi This is another question, but to answer it, you cannot read corrupt file data and get anything meaningful back. You are over-thinking the problem. This is a low level file read and save issue.
Jul 30, 2016 at 10:47	history	bounty ended	CommunityBot
Jul 29, 2016 at 9:48	vote	accept	Satoshi Nakanishi
Jul 25, 2016 at 3:44	comment	added	Paul S		Maybe someone is going to have to write a patch to geth or other ethereum client to prove that you an lie to an RPC client about the state of the network. It's entirely possible to do, therefore, you shoulde NEVER trust one node or one node technology. The truly paranoid (e.g. exchanges, anyone dealing with large amounts of ether) should be setting up multiple nodes in multiple security domains with different node technology and verifying large value transactions with multiple RPC calls. Alas, nobody has published such code yet AFAICT
Jul 23, 2016 at 6:03	comment	added	Satoshi Nakanishi		>if the database is properly corrupted (ie stored bits are missing or inaccessible) you will get read errors, How does the client check if the data is incorrect? Each time the geth is asked the data via JSON-RPC API, does the geth check if the data which the geth tries to return is correct/valid?
Jul 22, 2016 at 22:34	vote	accept	Satoshi Nakanishi
Jul 29, 2016 at 9:48
Jul 22, 2016 at 13:17	comment	added	Richard Horrocks		Do you know the mechanism by which local `.db` files are checked for validity/consistency, and how often this occurs? Presumably only when they're read, but how often does that happen? (I had a quick look in the code but it wasn't immediately obvious.)
Jul 22, 2016 at 9:33	history	answered	T9b	CC BY-SA 3.0