2 geth nodes on private network lose blocks when they synchronize

I have been running a private network with two machines connected in various ways - that's not the issue. But they were just running along separately for a few weeks, and each had its own transactions - some contracts were deployed and then were updated on each node while not in contact with the other. When I then turned on both machines and they connected, the resulting consensus just threw away three contracts from one of the nodes. What happened to immutability?? How can that be a proper synchronization result? The contracts are lost even on the machine that originally deployed them. This is not okay.


  • islandBillyislandBilly Member Posts: 15
    From the utter lack of response, I conclude that this is a feature of the ethereum blockchain synchronization. Probably intended to prevent double-spend kinds of things, but it renders my voting system completely unreliable. :^( It was a nice idea, but looks like blockchain is not the right foundation for this kind of application.
Sign In or Register to comment.