I am using scripts provided by IOHK to help build a private testnet. I have been told (during discussions in the white/blue/purple testnet development) that best practice is to start the network in byron and move through the era's until Alonzo is reached. This is what IOHK seems to do when they launch a new testnet (from part of their new purple testnet announcement, "Please allow ten hours for the network to be ready to test against. This will mean we have made the network move through all the eras to Alonzo correctly".
I have tried to reach out to IOHK for an answer to this but have not received a response back yet - I understand that they are pretty busy right now so i figured I would ask here...
The reason I would like to know is because I am working with one of the IOHK partners and we are trying to create an in-house, automatic, private blockchain tool - similiar to Ganache for Ethereum. We CAN currently start a private network in Alonzo which would make this task relatively simple but with the current best practice to start from Byron and progress to Alonzo, I would like to know what exactly we are giving up in functionality (or anything else) by directly starting in Alonzo instead?
-
1Please clarify your specific problem or provide additional details to highlight exactly what you need. As it's currently written, it's hard to tell exactly what you're asking.– Community BotCommented Aug 27, 2021 at 21:46
-
Simply, What functionality do you loose by starting a private network in the Alonzo era vs starting a private network in the Byron era and updating to Alonzo through update proposals?– anthony stachowitzCommented Aug 28, 2021 at 15:15
Add a comment
|
1 Answer
I received a message from Samuel Leathers about this issue. I am re-posting his response but if anyone would like to add additional information, please feel free to expand on the idiosyncrasies that Sam is talking about:
2 things:
db-sync doesn't work with the shortcut fork all eras in epoch 0 (yet, there's an open PR adding this finally)
The protocol version will still be 2 if you fork everything at once. This is something we've reported to the devs to get fixed later, but essentially, even if you do have the config fork all eras (in 0 or sequentially) you still need to submit update proposals every epoch to get it updated to 5. There are some weird idiosyncrasies that can happen if era is Alonzo but protocol version is less than 5.