AMMOcoin Security Guide

1. Back Up Your Wallet

Your wallet.dat file contains your private keys. If it is lost, your coins are gone forever. Copy wallet.dat to at least two separate locations (e.g., an encrypted USB drive and a cloud backup). After every significant transaction or address generation, create a fresh backup.

2. Use Strong RPC Credentials

The ammocoin.conf file should contain a unique rpcuser and a long, random rpcpassword. Never use defaults or short passwords. Example:

rpcuser=myuniqueuser
rpcpassword=a-very-long-random-string-here

3. Run Behind a Firewall

Only expose port 37020 (the P2P port) to the internet. The RPC port (51473) should never be accessible from outside your machine. On a VPS, use ufw or equivalent firewall rules to restrict access.

4. Verify Download Checksums

Before running any AMMOcoin binary, verify its SHA-256 checksum against the values published on the official GitHub Releases page; for v1.1.1 that is AMMOcoin-v1.1.1-ALL-PLATFORMS-CHECKSUMS.txt (see Verify your download). On Linux/macOS use sha256sum or shasum -a 256; on Windows use certutil -hashfile <file> SHA256.

5. Keep Software Updated

Always run the latest version of AMMOcoin. Updates may contain critical security patches. Watch the GitHub Releases page for new versions and follow the Upgrade Guide when updating.

6. Don't Keep Spending Keys on a Server

A server that is online 24/7 is the easiest place for an attacker to reach. To stake on a server, use cold staking: the server holds only a staking key that cannot send your coins, while the spending keys stay in your own wallet. See AMMOnode. On your own wallet, unlock for staking only (walletpassphrase "..." 0 true) rather than fully unlocking it.

7. Beware of Migration Scams

v1.0 balances will be airdropped to the same addresses on v1.1. You never need to send coins anywhere, and the team will never email you an address to send coins to. See the Migration page.