As a side note: having a c++ sdk means that a c-sdk is easy to add. Having a C sdk means support for most languages is easy to add because most languages have support for ffi with C libraries.
The C++ sdk I began is at a point where it’s trivial to complete the rpc part of api.
I welcome every help; but note that it’s under gplv3 license and I won’t submit it as an az application.
I would like to do a throw at a C# implementation of the sdk. I’ve setup a repository at GitHub - hypercore-one/znn_sdk_csharp: Zenon SDK for .NET. Will commit initial work when basic functionalities are working and I’ll try to follow the dart implementation as much as possible.
Will keep a close eye on other sdk Interpretations as I go along. Feel free to join if you want to help out.
I’ve made the top post a wiki post which means anyone should be able to edit, so feel free to update with ETAs or completion status as you see fit @devs
@devs don’t forget to jump into the main post here and edit the details and status of your SDK when appropriate and please reach out to the forum community if you need any assistance
Implemented 100% functionality of the Zenon .NET SDK. Will try to work towards 100% code coverage and eliminate remaining bugs. All major functions are tested and working.
Quick update: Added python repo link. Got through one of the difficult parts of the package, wallet key management. Ensured that my testcases passed the testcases from znn.js and znn_sdk_rust repos.
Quick update: Most of the non-trivial core functionalities are done in Python SDK. Working on the right way to create ABI class (playing with eth-abi package) right now to make contract calls.
I edited the Golang’s section linking MoonBaZe’s github since he picked up from where Georgie left off. @MoonBaZe is the SDK complete? Could you edit the post here if/when you’re done?