Mainnet is the live Aventus network, where your nodes earn rewards. Testnet is for testing only.
While the dashboard is on testnet it does not send heartbeats for your mainnet nodes, so they can miss rewards.
Switching reloads the app, and your config file will need to be loaded again.Switching reloads the app.
Activity Log
Initialising…
Memory Management
hours
Never
Resets all chain subscriptions while keeping the smoldot connection alive. Use if memory usage grows after many hours of running.
Display Preference
Node Table
Hidden by default — fetching per-node registry data (stake, serial, compounding) only when shown.
Connection
Current endpoint
-
Custom RPC endpoint
A WebSocket URL (wss://…) used to connect to the chain. Saved per environment; leave empty to use the default. Applying a change reloads the app.
Privacy
Anonymous usage statistics
What is sent: app type (desktop or web), app version, operating system,
environment, connection mode, read-only flag, and bucketed node and CPU core
counts (the desktop app also sends a bucketed RAM size). The server derives a
country and connection type (residential or data centre) from the request's IP
address, then discards the IP.
What is never sent: node IDs, owner addresses, keys, exact counts, or any
identifier tied to you. A random ID rotates every day, so instances cannot be
tracked across days.
Aggregate, anonymized statistics may be published to describe the network
(for example, machines per country or total cores). The Reset menu item
restores all defaults, including re-enabling this setting.
Aventus Node Dashboard — User Guide
Everything you need to know to monitor and manage your nodes.
1. Getting Started — Loading Your Config File
Before anything else, you need to load your configuration file so the dashboard knows which nodes to monitor and which account to use.
Click the green ⬆ Load Config File button at the top of the screen.
Browse to your config file (a .json file provided by your node operator or Aventus).
The dashboard will automatically fill in your owner address and begin loading your nodes.
Tip: If the dashboard shows a yellow warning banner after loading, it means there is a mismatch between the nodes in your config file and the nodes registered on-chain. Check that your config file is up to date.
Important: The dashboard does not keep your config file. After an update, or any time the app restarts or reloads, load your config file again: until you do, the dashboard still shows your nodes but does not send heartbeats for them, so they miss rewards. To check heartbeats are being recorded, click Show node table and watch each node's heartbeat count in the Current Period column: it should go up about once an hour until it reaches the threshold, then stay there for the rest of the period. If it doesn't, open View logs and look for red error lines.
1. Getting Started — Looking Up Your Nodes
This dashboard is read-only. It shows your account and nodes using data from the blockchain, but it does not load a config file or send heartbeats.
Enter your owner address in the Owner Address field at the top of the screen.
Click Load.
The dashboard will fetch your account and begin loading your nodes.
Important: This dashboard is read-only. It shows your nodes and the heartbeats recorded for them on-chain, but it never sends heartbeats itself. Heartbeats are sent by the AVN Node Dashboard desktop app that has your config file loaded, so keep that app running and load your config file again whenever it restarts or updates. To check heartbeats are being recorded, click Show node table here and watch each node's heartbeat count in the Current Period column: it should go up about once an hour until it reaches the threshold, then stay there for the rest of the period. If it doesn't, check the desktop app's logs for red error lines.
2. The Dashboard Cards
The dashboard is organised into several sections, each showing different information about your account and nodes.
Monitoring Panel (top)
Owner Address
Enter or confirm your account address here, then click Load to fetch your data from the blockchain. Loading a config file will automatically fill in this field and fetch your data from the blockchain.
Node Health Summary
A row of coloured dots — one per node — giving you an at-a-glance picture of how all your nodes are performing. Click any dot to copy that node's ID.
Activity Log
A live feed of everything the dashboard does automatically: heartbeat submissions, connection events, errors, and more. The latest lines show in the Activity & health card; View logs opens the full log. Errors (red) and warnings (amber) stay highlighted in the card, with a count on the button, until you open the log.
Summary Cards (row of 5)
Actual / Virtual Nodes
How many physical nodes you own, and how many virtual nodes your total stake represents on the network.
Free Balance
The amount of AVT sitting freely in your account — not currently staked anywhere.
Total Staked
The total AVT you have staked across all your nodes. Use the Add Stake and Remove Stake buttons here to manage your stake.
Total Rewards
Your all-time lifetime rewards earned on the Aventus network. A pulsing green dot here means a reward period is currently active.
Recent Rewards
Rewards earned in the last 24 hours, updated automatically.
Info Cards (row of 4)
Next Payment
A countdown showing how many blocks remain until the next reward is distributed, along with an estimated time.
Reward Pot
The total pool of AVT available to be shared as rewards in the current period.
Reward Period
The current period number and network-wide statistics — total heartbeats submitted and total network weight.
Rewards Per Node
The last 5 reward entries for each of your nodes, so you can see recent earning history at a glance.
Node Table (bottom)
A detailed table listing every node you own. Each row shows:
Node ID — the unique identifier for this node (click to copy).
Serial / Genesis — the node's serial number and whether it has a genesis bonus.
Stake — how much AVT is staked on this node and any pending unlocked amount.
Compounding Enabled — whether rewards are automatically re-staked on this node.
Auto-staking Period — whether automatic staking is currently Active or has Expired.
Unstake Status — whether and how you can remove stake (see Staking States below).
Current Period — a progress bar showing how many heartbeats this node has submitted versus the required threshold.
3. Node Health Status
Each node's health compares the heartbeats recorded on-chain for it in the current reward period with the number it needs (the threshold). It shows what has been recorded so far, not whether heartbeats are currently being sent. There are four health states:
Healthy — The node has reached the heartbeat threshold for this period. No action needed.
On Track — The node has at least as many heartbeats as expected at this point in the period. Early in a period few or none are expected, so nodes show as On Track for the early part of each period even before any heartbeats have been sent.
Lagging — The node is behind where it should be at this point, but it can still reach the threshold if heartbeats continue for the rest of the period.
Unhealthy — The node can no longer reach the threshold this period, even if every remaining heartbeat is sent.
Tip: If a node is Lagging or Unhealthy while the app is open, check that your config file is loaded (see section 1). Without it, the dashboard shows your nodes but sends no heartbeats. Click Show node table and check that the node's heartbeat count in the Current Period column is going up.
Tip: This dashboard only displays heartbeats; it doesn't send them. If a node is Lagging or Unhealthy, check that the desktop app sending heartbeats for it is running and has your config file loaded (see section 1). Click Show node table and check that the node's heartbeat count in the Current Period column is going up.
Note: The coloured dots in the Node Health Summary panel each represent one node. Click any dot to copy that node's ID to your clipboard.
4. Staking States — When Can You Unstake?
Each node's Unstake Status column tells you whether — and under what conditions — you can remove stake from that node.
🔓 FreeNo restrictions. You can remove stake from this node at any time.
🔒 LockedFully locked. The stake on this node cannot be removed at this time. You must wait until the lock expires.
⌛ PeriodicPartial withdrawals allowed. A portion of your stake can be removed each reward period. The row shows how much you can remove per period and when the restriction expires.
5. Adding and Removing Stake
You can manage stake on any of your nodes using the Add Stake and Remove Stake buttons on the Total Staked card.
Click + Add Stake (blue) or − Remove Stake (amber) on the Total Staked card.
In the popup, confirm the action (Add or Remove Stake) from the dropdown.
Use the search box to find the node you want, then select it from the list.
Enter the amount in AVT. For Remove Stake, you can leave the amount blank to remove everything (subject to your unstake status).
Click Open in browser → — your default web browser will open a signing page.
Choose your wallet (Polkadot.js, Talisman, or SubWallet), select your account, and approve the transaction.
The dashboard will confirm once the transaction is finalised on-chain.
Important: You can only remove stake up to the amount permitted by your node's Unstake Status. If the status is Locked, the Remove Stake option will not succeed.
Not enough balance to pay the transaction fee: Every transaction you sign — adding or removing stake, and linking or unlinking an Ethereum account — costs a small transaction fee in AVT. The fee is paid from the free balance of the account you sign with; AVT that is staked or locked can't be used. If that account has no free AVT, you'll see “You do not have enough free balance to pay the transaction fee” and the dashboard stops before your wallet asks you to sign.
To fix it, top up the account with AVT and try again. If you don't have AVT on the Aventus Network, you can buy AVT on Ethereum and lift it to your account using the Aventus bridge. Once the AVT has arrived, the warning clears on its own and you can try again.
6. Exporting the Activity Log
The Activity Log records a timestamped history of everything the dashboard has done — heartbeat submissions, connection events, warnings, and errors. This is useful for troubleshooting or sharing with the Aventus support team.
Find the Activity & health card below the owner address.
Click its ⬇ Export button (next to View logs).
A file will be downloaded to your computer containing the full log history.
7. Advanced
The Advanced menu in the top-right corner holds settings you rarely need: the network, Ethereum account linking, display preferences, the connection, privacy and memory management.
Network
Mainnet or Testnet
The header shows which network the dashboard is on (Testnet in amber). To change it, use Advanced → Network. Stay on Mainnet to earn rewards: while the dashboard is on Testnet it does not send heartbeats for your mainnet nodes.
Memory Management
Auto-reset interval
The dashboard automatically recycles its light-client worker on a schedule to free memory that accumulates over time. The default is every hours. You can change this to any value between and hours and click Apply.
Reset now
It immediately recycles the smoldot worker — the new worker initialises using the saved chain database so no resync is needed, and the old worker stays alive until the new one is ready so there is no gap in connectivity. All subscriptions are then rebuilt against the new client. The button is disabled while the reset is in progress. The Last reset time updates after each reset.
Node Table
The detailed node table (showing serial number, stake, compounding status, and heartbeat progress per node) is hidden by default to reduce memory usage. The Node Health Summary dots are always visible and give you an at-a-glance view without loading the full table.
Show node table
Click Show node table to load and display the full per-node breakdown. The dashboard will fetch registry data (stake, serial, compounding) for all your nodes. Click Hide node table to stop loading that data and collapse the table again.
Why is it hidden?
Running the dashboard with the table visible uses more memory. Hiding it is less memory intensive, which makes a noticeable difference when the dashboard is left running for long periods.
Tip: If you only need to check on your nodes occasionally, leave the table hidden. Open it when you want detail, then hide it again to keep memory low.
8. Privacy & Anonymous Usage Statistics
To understand the network's footprint (which countries machines run in, what platforms and hardware they use), the dashboard periodically sends a small, anonymous statistics ping: app type and version, operating system, environment, connection mode, read-only flag, and bucketed node/CPU-core counts (the desktop app also sends a bucketed RAM size). The receiving server derives a country and a connection type (residential or data centre) from the request's IP address and then discards the IP.
It is anonymous by design: no node IDs, owner addresses, keys, exact counts, or persistent identifiers are ever sent. A random ID rotates every day, so the same instance cannot be tracked from one day to the next. Aggregate, anonymized statistics may be published to describe the network.
Opting out
Open Advanced → Privacy and untick Share anonymous usage statistics. Self-hosted web deployments can disable it for all users with the container env var TELEMETRY_DISABLED=true.
Reset re-enables it
The Reset item in the Advanced menu clears all saved settings, which restores the defaults — including turning these statistics back on.
9. Contact Us
If you need help or want to report an issue, you can reach the Aventus support team through the following channels: