The Story of SovereignChain SDK
$EGLD #MultiversX
We have started developing the SovereignChain SDK in summer of 2023 and presented a really basic version of it on xDay 2023, that was only a proof of concept, put together as a demo only.
In May 2024 we have launched the alpha version of SovereignChain SDK with >70K TPS, and with some bugs. Summer of 2024 was about bugfixing and configuration of the SDK. It was also about researching different models of launching, and offer those as possibilities to the community. Like reStaking, settlement layer, different type of bridging, cross chain interoperability.
Since May we have started multiple discussions with different teams who showed interest in building on top of SovereignChain SDKs. Explaining the vision, explaining the possibilities, and asking the teams what is the most important features they want to have, most important metrics. But it was the job of each such project to ask/request for features. The status of the code in June 2024 on the SDK made it possible for anyone to start working on their own solution, ask questions, try out things and report back with bugs.
In September 2024, we have fixed all the known major bugs, since then the SDK is stabilised, every day/week we have non stop testing on the SDK with super complex scenarios. The last months were about adding more customisability to the base code, more components which can be swapped in and out from a simple configuration file. On top of that we were working on optimising the built-in cross chain composability component, making it faster, safer, work for all type of assets, have all integration into all the tools.
So in the end, since the end of May, any project could start to develop their custom solutions on top of the SDK, get feedback and help from the foundation and apply for grants as well. If we look for any L2 built on top of Optimism SDK / Cosmos SDK, we see that they start coding at least 6 months before a testnet, and they have around 6 months on the testnet before going to mainnet. Wrote this to manage the expectations.
What are we doing next? As we finished the beta version of the SDK, the code will enter into an audit phase from middle of January.
And in the meantime we are going to code further the next features and the next customisability components. We will add native settlement layer, native exit tries, also native interoperability with other chains as well (integrating general interoperability solution directly to the SDK).
These are the plans. Time to build.