Agrarian operator guide · Core 2.0.1
Run an Agrarian masternode
Keep the keys that control your AGR in your desktop wallet. Run a separate, always-on server that uses only a masternode operator key to announce the node and send its regular network pings.
Before you start
Early operator documentation. Registration, activation, and payouts were exercised in an isolated staging network. This is not evidence of working mainnet payouts. Practice with test funds in an isolated environment before committing real collateral. Neither activation nor a payout schedule is guaranteed.
Mainnet configuration
Set up and register the node
1. Prepare the controller wallet
Use a dedicated desktop wallet. Before funding it, close Qt and set the following in agrarian.conf in its data folder (normally %APPDATA%\Agrarian on Windows or ~/.agrarian on Linux):
txindex=1
staking=0
enablezeromint=0
Restart, finish syncing, and back up the encrypted wallet. If you are enabling the transaction index on an existing data directory, back it up first and start once with -reindex. Do not delete or move your wallet file to build the index.
2. Create the collateral and operator key
Create a new receiving address in the controller and send exactly 10,000 AGR to it in one transaction output. Pay the fee separately; do not subtract it from the recipient amount. Wait for at least 15 confirmations and do not spend that output while the masternode is running.
On the controller, open the Qt debug console and run:
getmasternodeoutputs
createmasternodekey
Match the output to your collateral transaction and record its txhash and outputidx. Store the operator key securely. It is not the spending key; do not post it or send it to anyone offering setup help.
3. Configure the always-on server
Extract the verified Ubuntu release. Run the daemon as a dedicated, non-root user with a fresh data directory. In that account’s ~/.agrarian/agrarian.conf, use the following, replacing both placeholders with your public IPv4 address and operator key:
server=1
listen=1
port=51336
txindex=1
staking=0
masternode=1
externalip=YOUR_PUBLIC_IP:51336
masternodeaddr=YOUR_PUBLIC_IP:51336
masternodeprivkey=YOUR_OPERATOR_KEY
Make the file owner-readable only (chmod 600 ~/.agrarian/agrarian.conf). Leave RPC at its default loopback binding and do not expose TCP 51335. Allow TCP 51336 through both the server and hosting firewalls. Do not copy the controller wallet or any spending key to this server.
From the folder where you extracted the release, start the daemon and check sync using commands like these. For day-to-day operation, run it under a service manager so it starts again after a reboot.
./agrarian/bin/agrariand -daemon
./agrarian/bin/agrarian-cli getblockchaininfo
./agrarian/bin/agrarian-cli mnsync status
Confirm the server is on mainnet, its tip matches an independent synced node or the explorer, and the advertised port is reachable from a different network.
4. Register from the desktop wallet
Close Qt and add one line to masternode.conf in the controller’s data folder. Replace the placeholders with your actual endpoint, operator key, collateral transaction hash, and the output index returned by getmasternodeoutputs:
mn1 YOUR_PUBLIC_IP:51336 YOUR_OPERATOR_KEY COLLATERAL_TXID OUTPUT_INDEX
Protect this file too: it contains the operator key. Reopen Qt, enable Show Masternodes Tab in wallet options if needed, then select mn1 under your masternodes and choose Start alias. If Qt prompts to unlock the wallet, do so locally and lock it again after registering.
Registration success means the announcement was sent, not that the node is enabled. Keep the server online, allow at least 10 minutes for activation pings, and check these commands on the server:
./agrarian/bin/agrarian-cli getmasternodestatus
./agrarian/bin/agrarian-cli listmasternodes COLLATERAL_TXID
Look for ENABLED for your collateral in the list. The strongest check is to run the same list query from a second synced node and confirm it sees your entry as enabled as well.
Masternode FAQ
ACTIVE label with rank zero in the list can be a pending entry, not a fully enabled node.
Core 2.0.1 release and verification · Masternode RPC source · Staging evidence and limitations