You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The resulting databases contain the entire blockchain (all blocks, all uncles, all transactions), every transaction receipt and generated logs, and the entire state trie of the head 1024 blocks. This allows a fast synced node to act as a full archive node from all intents and purposes.
Actual behaviour
Logs from blocks that were imported via the "fast" method are not available.
This is a major disadvantage to fast sync. Can it be made an option?
Thanks
The text was updated successfully, but these errors were encountered:
@ethernomad in #3563 (comment), you linked to a reddit post claiming that logs are missing after fast sync. Did you open this issue speculatively? Can you verify that running geth --fast imports logs correctly on your machine?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
System information
Geth
Version: 1.5.5-stable
Git Commit: ff07d54
Protocol Versions: [63 62]
Network Id: 1
Go Version: go1.7.3
OS: linux
GOPATH=
GOROOT=/usr/lib/go-1.7
Expected behaviour
After performing a fast sync old logs should be available.
In the original pull request #1889 says:
Actual behaviour
Logs from blocks that were imported via the "fast" method are not available.
This is a major disadvantage to fast sync. Can it be made an option?
Thanks
The text was updated successfully, but these errors were encountered: