Categories
- 17.3K All Categories
- 9.5K Mining
- 574 Pool Discussion
- 378 Promotional
- 1.4K General Project Discussion (non-technical)
- 485 Education
- 811 Protocol and Client discussion
- 170 web3-js
- 29 Whisper
- 16 Swarm
- 3 RLP
- 303 IoT & Hardware
- 1.2K Smart Contracts and Dapps
- 28 Serpent
- 359 Solidity
- 664 Projects
- 1.2K Reference clients code and builds
- 249 Eth & AlethZero- Cpp Implementation
- 471 Geth - Go Implementation
- 242 Mist
- 15 Node.js Implementation
- 36 Python Implementation
- 49 Mix
- 36 Other Implementations
- 170 Meetups
- 40 Other Events
- 226 Jobs & Skills
- 281 Press and Articles
- 75 Audio/Video
- 296 Ether Sale
- 1.2K Other Languages
- 96 Chinese
- 255 German
- 33 Italian
- 111 French
- 3 Hebrew
- 42 Japanese
- 75 Portugese
- 46 Romanian
- 185 Russian
- 231 Spanish
- 47 Turkish
- 125 Watercooler
Blockchain forks !!! (+ideas)
Due to several Ethereum blockchain resets by developers, it is important to note we now have at least 2 forks of chains.
One has about ~4000 blocks, the other 10,000+ blocks.
On my PC and on http://etherchain.org/ I see the longer chain.
Solution for developers:
But if the dev team wants to flush and really reset the chain, here is the procedure:
1. announce it in advance (transparency is important!)
2. release team (core developers) must generate a new genesis block
3. hard code the new genesis block hash into a new client, such as new BETA/POC or an actual release.
(+you can have an optional-command line to enter a different genesis block hash, just in case you wanna work on a forked chain to test things)
Solution for end-users:
1. Install same version of client (such as POC3, C++ version, Alethzero)
2. Make peer connection to each other.
This will replace short chains with the longest one.
This way, the older (longer) chain will no longer over-ride the short chain.
-Technologov, 07.Mar.2014.
One has about ~4000 blocks, the other 10,000+ blocks.
On my PC and on http://etherchain.org/ I see the longer chain.
Solution for developers:
But if the dev team wants to flush and really reset the chain, here is the procedure:
1. announce it in advance (transparency is important!)
2. release team (core developers) must generate a new genesis block
3. hard code the new genesis block hash into a new client, such as new BETA/POC or an actual release.
(+you can have an optional-command line to enter a different genesis block hash, just in case you wanna work on a forked chain to test things)
Solution for end-users:
1. Install same version of client (such as POC3, C++ version, Alethzero)
2. Make peer connection to each other.
This will replace short chains with the longest one.
This way, the older (longer) chain will no longer over-ride the short chain.
-Technologov, 07.Mar.2014.
Comments
developers could use command-line and use own genesis block (devnet).