I’m happy to see this revised proposal with new details. Here is some “guidance” from the official medium post regarding SDK projects. Maybe some of the devs who are working on SDK projects @georgezgeorgez can provide additional clarity on how best to move forward.
SDK port project:
Create an open source repository and implement core functionalities
Showcase working demo and implement the remaining functionalities
Code coverage (unit tests) for the functionality & showcase final product
Thanks for revisiting your proposal. I think this is totally reasonable now in total.
Two points: You have 3 days for the crypto primitives and you say in your bio that you are an expert in that field. So maybe that’s possible, that would impress me. Anyway, I would hope you don’t actually do it that way - quick search shows that there are existing crates for all the primitives you mentioned. I would rather see you use existing libraries that are widely used and maybe keep these days as a buffer or add them to testing. I guess that also would be common practice. (After checking your code I see you’re already importing some.)
Second, just a hint. You probably have the endpoints from the api documentation. These aren’t complete (and not in all cases correctly documented). It’s certainly helpful as an overview, but there are a few more endpoints (at least accelerator is missing from your list) or they deliver slightly different results or require slightly different arguments in some cases.