haveno/pricenode
2022-03-06 10:45:18 -05:00
..
docker Bisq 2021-05-04 20:20:01 -04:00
src update price node from upstream, fix XMR price, default port 8078 2022-02-16 11:59:21 -05:00
collectd.conf.snippet Bisq 2021-05-04 20:20:01 -04:00
haveno-pricenode.env converted bisq pricenode install to haveno install (#31) 2021-05-04 22:50:24 -04:00
haveno-pricenode.service settings for pricenodes and add our pricenodes 2022-03-06 10:45:18 -05:00
install_hsversion_debian.sh Bisq 2021-05-04 20:20:01 -04:00
install_networksize_debian.sh Bisq 2021-05-04 20:20:01 -04:00
install_pricenode_debian.sh settings for pricenodes and add our pricenodes 2022-03-06 10:45:18 -05:00
journalscraper_hsversion.sh Bisq 2021-05-04 20:20:01 -04:00
journalscraper.sh Bisq 2021-05-04 20:20:01 -04:00
Procfile converted bisq pricenode install to haveno install (#31) 2021-05-04 22:50:24 -04:00
README-HEROKU.md Bisq 2021-05-04 20:20:01 -04:00
README.md settings for pricenodes and add our pricenodes 2022-03-06 10:45:18 -05:00
torrc Bisq 2021-05-04 20:20:01 -04:00
uninstall_hsversion_debian.sh Bisq 2021-05-04 20:20:01 -04:00

Haveno-pricenode

Overview

The Haveno pricenode is a simple HTTP service that fetches, transforms and relays data from third-party price providers to Haveno exchange clients on request. Available prices include:

  • Bitcoin exchange rates, available at /getAllMarketPrices, and
  • Bitcoin mining fee rates, available at /getFees

Pricenodes are deployed in production as Tor hidden services. This is not because the location of these nodes needs to be kept secret, but rather so that Haveno exchange clients do not need to exit the Tor network in order to get price data.

Anyone can run a pricenode, but it must be discoverable in order for it to do any good. For exchange clients to discover your pricenode, its .onion address must be hard-coded in the Haveno exchange client's ProvidersRepository class. Alternatively, users can point explicitly to given pricenode (or set of pricenodes) with the exchange client's --providers command line option.

Pricenodes can be deployed anywhere Java and Tor binaries can be run. Instructions below cover deployment on localhost, and instructions how to deploy on Heroku are also available.

Pricenodes should be cheap to run with regard to both time and money. The application itself is non-resource intensive and can be run on the low-end of most providers' paid tiers.

A pricenode operator's main responsibilities are to ensure their node(s) are available and up-to-date. Releases are currently source-only, with the assumption that most operators will favor Git-based "push to deploy" workflows.

Prerequisites for running a pricenode

To run a pricenode, you will need:

  • JDK 8 if you want to build and run a node locally.
  • The tor binary (e.g. brew install tor) if you want to run a hidden service locally.

How to deploy for production

Install

Run the one-command installer:

curl -s https://raw.githubusercontent.com/haveno-dex/haveno/master/pricenode/install_pricenode_debian.sh | sudo bash

This will install the pricenode under the user pricenode. At the end of the installer script, it should print your Tor onion hostname.

Test

To manually test endpoints, run each of the following:

curl http://localhost:8080/getAllMarketPrices
curl http://localhost:8080/getFees
curl http://localhost:8080/getParams
curl http://localhost:8080/info

Monitoring

If you run a main pricenode, you also are obliged to activate the monitoring feed by running

bash <(curl -s https://raw.githubusercontent.com/haveno-dex/haveno/master/monitor/install_collectd_debian.sh)

Furthermore, you are obliged to provide network size data to the monitor by running

curl -s https://raw.githubusercontent.com/haveno-dex/Haveno/master/pricenode/install_networksize_debian.sh | sudo bash

Updating

Update your Haveno code in /Haveno with git pull

Then build an updated pricenode:

./gradlew :pricenode:installDist -x test

How to deploy elsewhere

Bitcoin mining fee estimates

The pricenode exposes a service API to Haveno clients under /getFees.

This API returns a mining fee rate estimate, representing an average of several mining fee rate values retrieved from different mempool.space instances.

To configure which mempool.space instances are queried to calculate this average, see the relevant section in the file application.properties.