Sunday update:
This week, we published the first code of the new Veltor client. The network component. It manages bootstrapping of a node, peer discovery and keep-alive between peers. A user can send messages to a specific peer or broadcast them to the network. The package follows the Veltor design philosophy of being minimalist, extensible and efficient.
You can customize the logging, the peer address management strategy, the serialization used to encode & decode messages and the connection parameters of the node. You can subscribe to network messages to use them in your own code, which makes it straight forward to build a second layer.
The library serializes data using JSON by default, but it includes a highly efficient capnproto implementation which will be used for Veltor. All messages are compressed using lz4, a compression algorithm that is extremely fast and reduces bandwith usage by around 50%.
With this package, it is easy to handle many wallets with a single network node. It's also trivial to wrap a Veltor node into RPC and make it remotely accessible. A company could build its own redundant & geographically distributed network of Veltor nodes, similar to CDN servers, to guarantee reliable connectivity for its wallets.
If you are able to make sense of the code, feel free to contribute and grab an issue on Github.
https://github.com/veltor/veltor-network
J.V.
This week, we published the first code of the new Veltor client. The network component. It manages bootstrapping of a node, peer discovery and keep-alive between peers. A user can send messages to a specific peer or broadcast them to the network. The package follows the Veltor design philosophy of being minimalist, extensible and efficient.
You can customize the logging, the peer address management strategy, the serialization used to encode & decode messages and the connection parameters of the node. You can subscribe to network messages to use them in your own code, which makes it straight forward to build a second layer.
The library serializes data using JSON by default, but it includes a highly efficient capnproto implementation which will be used for Veltor. All messages are compressed using lz4, a compression algorithm that is extremely fast and reduces bandwith usage by around 50%.
With this package, it is easy to handle many wallets with a single network node. It's also trivial to wrap a Veltor node into RPC and make it remotely accessible. A company could build its own redundant & geographically distributed network of Veltor nodes, similar to CDN servers, to guarantee reliable connectivity for its wallets.
If you are able to make sense of the code, feel free to contribute and grab an issue on Github.
https://github.com/veltor/veltor-network
J.V.
Code is looking great Jason great work!
shut the fuck up you shill.
but yeah, great work Mr Connor.
Just don't go crazy on us again.
PS: Hey ICO, you let the Humaniq scammers get away with things. I thought you were going to stick a fork up Alex's ass.
You obviously didn't read my due diligence for Humaniq.
Some of us actually care about codebases.
i did read your due diligence.
did you see their reply?
Yes, I certainly did and I'm still considering it.
, also a bounty whore. And you are right about not bothered, i am not interested