ZNNplayground - play around with the API endpoint


Here’s some info related to the ZNN playground. This is my first ZNN related project to get a better understanding on the NoM process. I am using the Alien Valley JS SDK and added all the API end-calls to the source. Currently it only works on HTTP as secure calls to the public nodes are not available currently. (so HTTPS and WSS doesn’t work)

Most of the functions can be called with only a node configured, some need to have your personal address so you would need to upload the key JSON file with the password used. (you can also create a test wallet and/or download the project locally)

If a message contains JSON then you can click on it to have a fullscreen popup with the JSON formatted in a better way.


API endpoint info:

ZNN.js github:


Hope you guys find it useful, good luck with A/Z ^^


saw this when you posted it on the Telegram, very cool

This is a great way to learn about the API. Thanks for building this!

1 Like

@DrunkenMoose I used this in anger today to dump a list of all pillars, we are using the ownerAddress to validate Pillar owners via signed messages. Very helpful

Yea I can make python scripts etc. but it’s hard for me to understand what is handy and how the overal structure is. So if you need anything like that then let me know and how it should work ^^

One of the ideas I had is to make a custom wallpaper in “Wallpaper Engine” that displays all the real-time nodes as an interactive network map with their status and how the peers are connected with each other. Would be funny to implement the znn.js SDK to have NoM data inside a wallpaper i.e.

You have the function “stats.networkInfo” that shows all the peers, so I guess you can connect to each peer and call the function again to make a data structure. But currently I don’t know how it’s structured. I just want to make any kind of structure, perhaps I can do a pillar overview or something like that.