Integration Guide
This guide is aimed at developers willing to integrate their software with Witnet and the Wit coin in such a way that they can manage addresses, balances, and create and verify transactions.
Last updated
Was this helpful?
This guide is aimed at developers willing to integrate their software with Witnet and the Wit coin in such a way that they can manage addresses, balances, and create and verify transactions.
Last updated
Was this helpful?
The Witnet Foundation-supported reference implementation of the Witnet protocol is .
Witnet-Rust can be easily run:
Witnet-Rust contains two different components that provide different degrees of wallet functionality:
node
, which implements a Witnet full node with an internal single-account, single-address wallet and a .
wallet
, which implements a compliant, multi-account, multi-address wallet, and a .
node
componentThe Witnet-Rust node
component is standalone — you can run it on its own and it will provide full-node functionality: syncing up the Witnet block chain, validate transactions and blocks in real time, and (optionally) propose blocks.
Once a node
instance is fully synced, its offers a minimal single-account, single-address wallet.
Here is a quick guide on how to interact with a node using the JSON-RPC interface and any TCP client:
wallet
componentThe Witnet-Rust wallet
component is NOT standalone. It requires a connection to an instance of the node
component that will act as its "backend":
For users looking for the maximum degree of privacy, it is recommended that they run their own instance of the node
component, because otherwise they may be disclosing their addresses and balances to 3rd parties, as the queries between the wallet
and node
components need to be sent over the Internet.
Running a Witnet-Rust node with the exposed on local port 21338
can easily be achieved with this Docker one-liner:
The full list of supported JSON-RPC methods is available in the :
There is also a that exposes all the node functionality and uses the JSON-RPC API under the hood:
Witnet Foundation operates a cluster of publicly available node
instances that act as the backend for the wallet
component contained within the , which follows exactly the same architecture:
The of the wallet
component is different than the one from the node
not because it has much more advanced wallet functionality, and uses a WebSockets transport instead of plain TCP (this is to enable web wallets and similar apps).
A full reference of the can be found here: