Spritely is collaborating with Agoric and Cap’n Proto to build an interoperable standard for an Object Capability Network (OCapN). This gives you remote objects with a capability-based security model; a transport-agnostic message passing protocol that can run on multiple transports, including TOR; and acyclic GC. The goal is to release a standard that is already being used by 3 notable players in the peer-to-peer field. That has more value than just releasing a library and then trying to convince others to use it.
Veilid provides two things: Private routing like TOR, only faster. A distributed hash table, like the DHT in bittorrent and IPFS, but multi-writer. Nodes can communicate by leaving messages for each other in the DHT. VeilidChat uses this. The library is multi-platform, mobile friendly, with multiple language bindings.
The two projects seem to be complementary. Presumably OCapN could use Veilid private routing as a transport.
These technologies do not use a blockchain, or other kind of distributed transactional layer. Unlike many other “web3” platforms for peer-to-peer distributed applications. I think this avoids a technical tarpit, as well as the social opprobrium associated with blockchain and web3.
I’m watching the OCapN work. I’ve previously read the description of it in the old ERights site, but it’s somewhat hard to follow. It would be good to have a solid clear spec.
I agree that the two projects described here seem complementary. For a P2P RPC system the big problem is peer discovery. (After which comes NAT traversal!) A DHT would help with that. I know there are existing systems like Yggdrasil, but they act as system services, not just a tool for a single app to use, so they’re awkward for this purpose.
This is cool.
Spritely is collaborating with Agoric and Cap’n Proto to build an interoperable standard for an Object Capability Network (OCapN). This gives you remote objects with a capability-based security model; a transport-agnostic message passing protocol that can run on multiple transports, including TOR; and acyclic GC. The goal is to release a standard that is already being used by 3 notable players in the peer-to-peer field. That has more value than just releasing a library and then trying to convince others to use it.
Veilid provides two things: Private routing like TOR, only faster. A distributed hash table, like the DHT in bittorrent and IPFS, but multi-writer. Nodes can communicate by leaving messages for each other in the DHT. VeilidChat uses this. The library is multi-platform, mobile friendly, with multiple language bindings.
The two projects seem to be complementary. Presumably OCapN could use Veilid private routing as a transport.
These technologies do not use a blockchain, or other kind of distributed transactional layer. Unlike many other “web3” platforms for peer-to-peer distributed applications. I think this avoids a technical tarpit, as well as the social opprobrium associated with blockchain and web3.
I’m watching the OCapN work. I’ve previously read the description of it in the old ERights site, but it’s somewhat hard to follow. It would be good to have a solid clear spec.
I agree that the two projects described here seem complementary. For a P2P RPC system the big problem is peer discovery. (After which comes NAT traversal!) A DHT would help with that. I know there are existing systems like Yggdrasil, but they act as system services, not just a tool for a single app to use, so they’re awkward for this purpose.