Web UI
The dashboard built into the node: its eight tabs and their routes, the theme switch, the live indicator, and the options that expose or trim it.
Every lotusd carries a web interface in its binary: nothing to install, no other server. It is served on the node's RPC and web port, 10604 on mainnet.
Open it on the machine that runs the node:
http://127.0.0.1:10604/dashboardA public node shows the same pages: givelotus.org/dashboard.
The eight tabs #
| Tab | Route | What you find there |
|---|---|---|
| Explorer | /dashboard | Blocks, Mempool, Rich list, Charts, and the block, transaction and address pages. See Explorer |
| Tokens | /dashboard/tokens | SLPv1 (/dashboard/tokens/slp) and ALP (/dashboard/tokens/alp): overview, tokens, activity, burns |
| Social | /dashboard/social | RANK votes on profiles and posts: overview, activity, trending, profiles |
| Protocols | /dashboard/protocols | eMPP, BLOB, POKR and Contracts, under /dashboard/protocols/empp, /blob, /pokr and /contract |
| Pool | /dashboard/pool | Overview, How to mine, ASIC and merged mining, Miners, Blocks, Balances, Mine in your browser, Decode. See Pool |
| Network | /dashboard/network | Connected peers, Known nodes, Network map, Add nodes, Upgrades |
| Developers | /dashboard/docs | Documentation, REST API, Contract tools, Script trace, UTXO snapshots, Glossary |
| Wallet | /wallet/ | The browser wallet, a separate app with the same header. See Wallets |
Every view has its own URL, so a page can be bookmarked or shared. Older URLs such as /dashboard/mining redirect to their new place.
Tokens, Social and Protocols depend on the node's chain modules. A tab is hidden when none of its modules runs on the node: Tokens needs slp or alp, Social needs rank, Protocols needs empp, blob, pokr or the contract index. The dashboard reads the list from /api/v1/modules:
curl -s http://127.0.0.1:10604/api/v1/modulesconst { modules } = await (await fetch('http://127.0.0.1:10604/api/v1/modules')).json();
console.log(Object.keys(modules).filter(m => modules[m].loaded));The top of every page #
- Search bar. One field for a block height or hash, a transaction id, an address, a token id, or a social handle. The syntax is on the Explorer page.
- Upgrade banner. Appears in the 60 days before a network upgrade, with its date and a link to Network, Upgrades. You can dismiss it, except in the last 48 hours and while the node is syncing. For 14 days after the activation it says the upgrade is active.
- Sync banner. Shown while the node is syncing, refreshed every 5 seconds.
The live indicator #
The pill at the right of the top bar says how fresh the data on screen is:
- Live: the node computed the answer for this request, or cached it less than 2 seconds ago.
- Cached N ago: the answer came from the node's response cache. The pill turns to a warning tone at 10 seconds and to an alert tone at 30 seconds.
The age comes from the X-Cached-At header the REST API puts on a cached answer; any client can read it.
The Explorer home refreshes every 10 seconds and the Mempool page every 2 seconds.
Theme #
The theme button sits next to the live indicator. It offers three choices: System (follow the device), Dark and Light. Dark is the default.
The choice is saved in the browser, under the key lotus-ui-theme, and the wallet at /wallet/ on the same site uses the same key: change it in one and the other follows.
Options #
There is no option to switch the dashboard on: a running lotusd serves it. What you control is who can reach it and how much it shows.
| Option | Default | Effect on the web UI |
|---|---|---|
-rpcport=<port> | 10604 | The port of the dashboard, the wallet, the REST API and JSON-RPC |
-rpcbind=<addr> with -rpcallowip=<ip> | localhost only | Listen on another address and accept other clients. Each is ignored without the other |
-rpcallowforwarded | 0 | Keep 0 behind a reverse proxy: JSON-RPC then refuses requests that came through it, while the public pages and the REST API keep working |
-modules=<list> | all | Run only the listed chain modules (empp, pool, rank, pokr, blob, slp, alp, or none). The tabs of the others disappear and their routes answer 503 module_disabled |
-explorerindex | 1 | With 0 the explorer tables are not kept and the explorer routes that need them answer 503 explorer_disabled |
-contractindex | 0 | With 1, index contracts: Protocols, Contracts and /api/v1/contracts |
-scripttrace | 0 | With 1, enable POST /api/v1/script/trace, used by Developers, Script trace |
-httpcompression | 1 | gzip the dashboard and REST answers for clients that ask for it |
-rpcbind and -rpcallowip open JSON-RPC on the same port as the dashboard. To publish the web UI, put a reverse proxy in front that passes only the public paths. See Security and Configuration.
lotusd serves these paths: /dashboard and its assets, /wallet/, /api/v1/, /sitemap, /robots.txt, /favicon.svg and /favicon.ico.
While the node starts or syncs #
- During startup a browser gets a "node is starting" page with the stages, fed by
/api/v1/startup/status. It opens the dashboard when the node is ready. - During a first sync, the views that need indexes built at the end (the rich list, the unspent outputs of an address) say that they are being built. The rest works.
