@gozala Open Wireless Link looks really interesting, thanks for that link! Connectivity in general is a low-priority for me now that I've worked enough on it that it's good (not perfect!) while there are other parts that certainly not good (such as initial sync UX and performance), those are high-priority.

For some inspiration on how to expose something as a transport, check:

• https://gitlab.com/staltz/multiserver-rn-channel
• https://github.com/staltz/multiserver-dht

If there's native code in C (that's the case for Open Wireless Link), then we would need to create Node.js native bindings for that, see https://github.com/staltz/utp-native-nodejs-mobile and https://github.com/mafintosh/utp-native for an example.