Feature request: Integrate TezEdge into test network descriptions

[jdsika]

Dear Team,

as a Tezos "heavy user" the integrity and stability of the network is imperative to our operations. Protocol upgrades are the most exciting and also most dangerous events for our business. The days of protocol transition are often ones of sweat and staring at the node hoping everything goes smooth. What can be done to ease this experience?

Making the participation more accessable to the Tezos ecosystem with teztnets.xyz is great we at StakeNow fully embrace and is in our opinion the first and most important step to onboard more testers for broader test coverage and test networks closer to reality.

At Tezos we currently have two node implementations with Octez and TezEdge where the latter is only used by specialist teams with specific needs. The shell implementation is rather young but incredible!

We think that a network with a wider variaty of node implementations (ideally 50/50) would be extremely benificial for the robustness of the network. We have seen round >60 in the current Tenderbake testnet due to node crashes through TPS tests. With the 1/3 requirement of nodes to be responsive for the chain to progress a set of TezEdge baker would have come handy!

Feature Request:
Please include the instructions for TezEdge bakers and nodes into the descriptions and also try to be a good example in running them by yourself. The first "retail users (bakers)" do reveal the child diseases of the implementation which will help the developers and eventually the network.
In our opinion the core protocol developers should only inject a new proposal if at least the two implementations of TezEdge and Octez are successfully tested in the test networks. Please help us to bring this debate to the table and get into contact with us about it!

Best regards
Your StakeNow Team