Typescript SDK

Development ╰ Funding | Submissions
1

Hey fellow alienz, long time no hear. We’ve participated some time ago in Warpdrive to start building a Typescript SDK.

For those who don’t know, Typescript is the programming language for application-scale JavaScript. Basically, Typescript simplifies JavaScript code, making it easier to read and debug. The SDK will streamline the overall front-end development for any sort of products futurely developed within NoM.

3 months of development later, me and my amazing dev team managed to get this Typescript SDK done. I have to admit that it wasn’t easy because it required a quite profound understanding of both Typescript, Go and also some cryptography knowledge, but it was a great learning journey.

I’ve just created a dedicated Github: GitHub - DexterLabZ/znn.ts: Zenon TypeScript SDK
I’ll publish soon the open-sourced repos and we’re also prepping a Hyperspace submission.

Thanks in advance!

19 Likes
2

Thank you sir!! Look forward to the new submission.

3

@alien-valley.io wanted to make sure you saw this one.

1 Like
4

Hi @dexter703

I wasn’t aware that another JS SDK was being developed.
I’ve created a Telegram group specific for JS development, if you’d like to join in on the discussion. I’m working closely with PDfust to develop an extension-wallet similar to metamask.

Also, feel free to build on top of the work I’ve done so far. The repo can be found here @ znn.js

5

That’s great news!
Could you announce the status in the warpdrive channel on discord as well, please?
We’ve been using that for progress updates and to organize payouts.
@dexter703

6

Fantastic! Thank you for all of your hard work.

7

Why submitting another A Z proposal if you were part of wrapdrive? Also we got a Rust sdk for 1430 ZNN and 100 QSR just to let you know.

3 Likes
8

Yes I was also expecting a proposal that builds on this sdk

1 Like
9

Did this project receive compensation for the SDK under warpdrive?

Also, @dexter703 can you please give us a sense of the number of hours spent on the project?

2 Likes
10

need more details when asking for this much

4 Likes
11

I’m not sure. We have a channel for coordination of that on discord; they did not use that yet. @Sigli did they receive wd funding already?

13

Thank you.

125 qsr isn’t really worth mentioning, that’s true

1 Like
14

I agree, a break-up of the amount of hours it would take to build this SDK would be really helpful. I believe the community agreed on a 100$ per hour for the Rust SDK, so once @dexter703 list’s his phases out we can better assess how much zennies and qsr this SDK deserve?

@devs would it be fair to have a standard cost for developing an SDK (such as the 1430 zennies for the Rust SDK)? Or does the development of each SDK have to be assessed individually due to difficulty? (non-developer here :P)

15

The amount of hours is a vague metric as this heavily depends on the qualification of the submitter.
I like the current rust sdk proposal not only because it is well justified and articulated, but also because he puts a fair price on his own labor: he knows rust and he knows cryptography. So that reduces the hours he needs to get it done but it justifies a price tag of $1k/10h.

4 Likes
16

And for reference, here’s the proposal template by @romeo
https://forum2.zenon.org/t/zenon-network-accelerator-z-proposal-template/228?u=7nzalh

17

Just wanted to let everyone know that I’m holding my vote until we get some feedback from @dexter703 on open questions.

2 Likes
18

I’m still holding my vote until we get some of these outstanding questions answered. I posted an issue on Github asking for some interaction with us.

1 Like
19

For now I voted no due to the applicants unwillingness to answer questions about the proposal. If they start to engage on Github or the forum I’d be happy to reconsider my vote.

3 Likes
20

Same here. People submitting proposals need to realize the majority of projects launched in early days were by people w/ a good idea and little to no community involvement (starl, apsis online, etc etc). Their ideas approved then they never check back in. We need engagement not just from pillars / community but from those submitting proposals. I will always factor that into my decisions.

7 Likes
21

Greetings everyone!

I know you have many questions, so I’ve decided to compile a summary of everything that’s been going on in hope to answer them and hopefully future ones also.

So let’s begin!

Who am I?

You may call me Dexter and in my lab, I’ve got a special place dedicated to the Zenon ecosystem, just as I have a special place in my heart dedicated to the Zenon community.

I’ve been around since the Public Incentivized Testnet, got caught in the hype it created. I’ve been mostly quiet since I’m more used to talking to computers rather than people, but I’ve been following everything that’s been happening.

As soon as the znn_sdk_dart repo has been published, I knew that the TS SDK has to be next. Web3 is truly amazing and it will bring a ton of opportunities and possibilities. I’ve been working with it a lot and my past experience has allowed me to understand the impact it can bring to an ecosystem.

How did it start?

This project has started during the warpdrive. I thought it would be possible to have a PoC during that time, but man was I wrong.

It turned out to be quite a bit more complex than I initially thought and it involved hours and hours of research and testing to figure out all the quirks:

  • Hierarchical-deterministic wallet

  • Cryptography

  • User/contract address derivation

  • Node connection

  • APIs

  • ABIs

  • Contract interaction (staking, delegating, fusing, sentinel/pillar creation, zts creation and management)

  • Plasma mechanism

  • Powlinks mechanism

…and many more.

Also, keep in mind that the Syrius code was released just recently, so I only had the Dart SDK and CLI available.

Was it difficult?

Overall, I am estimating an investment of around 400 hours over the past 6 months. There were days when I’ve managed to go full-time and days when my attention was needed elsewhere, but I’ve managed to average around 3h/day.

The Zenon codebase is vast and porting an sdk requires a very good understanding of the code that makes everything tick:

  • go-zenon (huge repo)

  • znn_sdk_dart (beautifully structured, it helped!)

  • znn_cli (came in handy for tinkering with every little functionality)

What’s the progress?

This is something I’m really excited to share, the SDK is complete, it is a full port of the znn_sdk_dart!

Where’s the code?

I put some thoughts into this. At first I wanted to publish the repo, which I can’t wait to do, however, I didn’t want to risk someone else applying and getting the credit for my sweat and tears (of joy, of course). Therefore, for that matter, I’ve decided to publish the code after the project is approved with the community. The phases will come after I’ve published the code.

What’s next?

The znn_sdk_ts is just the first piece of the puzzle and I’m already working on the next big thing: a browser extension that works with chrome and firefox. I believe this will really push the zenon ecosystem forward, providing anyone with fast and easy access and giving us Web3 superpowers.

Moving forward, I’ll make myself available to the community and do my best to keep in touch. I prefer to focus on my work as I think that will bring the best results.

3 Likes