Replies: 2 comments
|
@ameetdesh here are my two cents. Protocol is the foundation of the beautiful buildings that will get built on it. The reason we have rebuilt the foundation (from v2-rc to v2-lts) is to enable even taller buildings to be built... but it is hard to justify more concrete & deeper trenches & stronger rebar without having a blueprint of the tower we could build on it. It is indeed important to articulate such blueprint. I foresee these future benefits will include:
@ravi-prakash-v, @abhimail, @anandp504 , @pramodkvarma could you add other points here? NBSL was asking for this as an internal justification for why everyone should move to LTS. This articulation will help them. |
|
This is like asking why I should adopt final release of software and not stay with beta!! LTS is the final long-term supported version and all adopters should move there for stability and support. Also, many schemas have been enhanced, advanced catalog and discovery capabilities built in, network rules and SDKs updated, new APIs (for settlement and disputes) are being added, and most importantly ensures adjacent sectors are interoperable. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Articulating this will help network operators motivate/persuade their participants and ensure a smooth transition. They need all the help they can get, when we are asking them to change engines on a running plane. As an example, a transformer plugin that we can make available can allows an NP to do migration at their own timeline. But they need to understand why first, in order to plan the transition.
All reactions