- What is the purpose of the .onion domain?
- A way to go to Mars and come back
- how to do I make the battery part of this camera?
- How to rid of “seams” from texture?
- Find center of geometry of a set of objects
- BGE Animated Fireball Group
- Importing multiple movie clips inside one directory via script
- Blender 2.79 Issues importing Collada (DAE)
- How to efficiently find graphic design opportunities
- Traffic duplication for dynamic consumers
- Sustainable Exterior Siding
- Rough cost-benefit of stopping car to recycle batteries
- Meaning of the word “else”
- Jane and Mark's and my house
- Grid Serializer Magento 2.2 In product edit page - adminhtml
- Why All Might could handle the power of One for All at once and Midoriya couldnt?
- Did Kishimoto kill Itachi because he was too strong to fight in the Fourth Great Ninja War?
- controlling 6-axis robotic arm with raspberry pi, what instructions can do this?
- Submitting web-to-leads with AJAX instead of embedded form
- Upload large ContentVersion records
Full node sync only preserve the last 128 history states
While researching on the different sync modes and their behaviors, I learned that geth full sync will replay all transactions from the genesis and preserve all history states, while fast sync will only download block data without statedb until around 100 blocks before the latest block head, and then perform as a full node.
I decided to verify these behaviors in this way:
I started a private network, and mined 2000 blocks with no transactions (but the balance of the miner should keep increasing because of the coinbase transactions).
Then I started other geth instances with different dirs and ports. Connected them to the private network node in full and fast sync.
Here's what I discovered:
In full sync geth instance, I'm able to query the state(by calling eth.getBalance(eth.accounts,
In fast sync geth instance, I'm able to query the state only for the last 64 blocks.
In both cases, querying states from old