The server that powers the Natrium and Kalium applications.
Natrium and Kalium are mobile wallets written with Flutter. NANO and BANANO are cryptocurrencies.
| Link | Description |
|---|---|
| natrium.io | Natrium Homepage |
| kalium.banano.cc | Kalium Homepage |
| appditto.com | Appditto Homepage |
GOLang
Install the latest version of GO
NANO/BANANO Node with RPC enabled.
Configured by the environment variable RPC_URL and NODE_WS_URL
e.g.
export RPC_URL=http://localhost:7076
export NODE_WS_URL=ws://localhost:7078
Redis server
Configured with env variables:
REDIS_HOST # default localhost
REDIST_PORT # default 6379
REDIS_DB # default 0
PostgreSQL
Configured with:
DB_HOST # The host of the database
DB_PORT # The port to connect to on the database
DB_NAME # The name of the database
DB_USER # The user
DB_PASS # The password
Other Configuration
FCM_API_KEY # For push notifications
BPOW_KEY # To use BoomPoW for work generation
Compile with go build -o natrium-server
Then run ./natrium-server or ./natrium-server -banano for banano mode.
Configuring a service for work is required. You have two options.
WORK_URLcan be set in the environment to a work server (either the same asRPC_URL) or something like nano-work-serverBPOW_KEYcan be set in the environment to use BoomPoW, BANANO's distributed proof of work system.
If both are set, BPOW will be preferred, followed by WORK_URL in the event of failure.
You can also override BPOW_URL, you would never want to do this, unless you are using a forked or self-hosted version of the service.
The HTTP callback is required for push notifications. This can be configured in the node's config.json as follows:
"callback_address": "::ffff:127.0.0.1",
"callback_port": "3000",
"callback_target": "\/callback",
The websocket on the node is used for other types of notifications, like for connected clients.
This is only so the app can easily be deployed with multiple replicas in production, we want only 1 instance to send push notifications at a time.