The Oxen blockchain forms the basis of all tools discussed above, and a number of other tools based on the Oxen stack. For developers, Oxen provides an instant private payments layer, routing, storage, and a shared consensus mechanism. Session and Lokinet are built on these primitives, and represent case studies in the potential for building on the Oxen tech stack. Anyone can develop applications based on these foundations.
Connor is a developer building an online marketplace which sells religious texts. Some of these texts are considered sensitive in Connor’s host country, meaning traditional payment providers are refusing to process payments for his store. Connor wants his customers to be able to pay for his religious texts, and he also wants a customer's identity to be protected when they make a purchase. Connor can accomplish this goal by integrating his website with an Oxen wallet and the Oxen Wallet RPC.
Jason is building a decentralised storage protocol which requires a number of nodes to come to consensus to split up some data and each store a piece of that data. He has been using an HTTP-based protocol to allow communication between nodes, but this protocol doesn't provide encryption and uses slow, CPU-intensive polling to fetch information. Jason can use OxenMQ to provide an encrypted socket-based connection between all nodes, which will improve performance, security, and responsiveness.
Developers can programmatically interact with a running Oxen wallet using the Oxen Wallet RPC. For example, calls can be made to track incoming payments or generate new subaddresses (used to reconcile customers/orders with specific payments).
The Oxen Wallet RPC call guide can be found here.