Timeline for Persistent "deep transaction reorg" whilst syncing full geth node
Current License: CC BY-SA 3.0
12 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Dec 30, 2018 at 3:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
Nov 19, 2018 at 9:56 | answer | added | Gokul Alex | timeline score: 1 | |
Nov 14, 2018 at 15:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
Oct 14, 2018 at 18:00 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
Sep 9, 2018 at 15:00 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
Aug 5, 2018 at 8:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
Jun 30, 2018 at 13:29 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
May 29, 2018 at 22:55 | answer | added | DenisM | timeline score: 1 | |
Dec 5, 2017 at 6:35 | history | protected | eth♦ | ||
Dec 5, 2017 at 1:56 | comment | added | Ismael♦ | Perhaps you are synchronizing closer to a fork in the blockchain and some of the peers are in the wrong chain, it should fix itself given some time. You can try restarting geth so it will try to connect with a new sets of peers. | |
Dec 2, 2017 at 1:30 | review | First posts | |||
Dec 2, 2017 at 11:38 | |||||
Dec 2, 2017 at 1:25 | history | asked | AnotherGethUser | CC BY-SA 3.0 |