-
Notifications
You must be signed in to change notification settings - Fork 5
How Orchard Works
Orchard is divided into two parts: the daemon, and the interface.
A program written in Python using the Python part of libctree to handle filesystem access, constant availability to other M/ECP nodes for consensus, local HTTP and Websocket hosting, talking to GPG and routing messages to all interested peers. It's a fairly multipurpose tool, thanks to its reliance on the BCP.ServerPool architecture from libctree.
Uses the JS part of libctree and communicates with the daemon with BCP over websocket. It's hosted with the HTTP server and Websocket server in the daemon - essentially, a website you host and use locally. Websites that use CTree technology can easily adapt this setup and code to their own hosting, for example, using only the websocket portion and using Apache for HTTP.
Currently the interface is not very stable or complete, as it's mostly a debugging platform for the underlying technologies, like libctree. As it develops, it will become a more and more useful tool, not just for end-users but for developers reverse-engineering it to see how to make their own CTree tools.