Freedom Coin
============
Command Reference

Sound money. Quantum proof. No masters.

This document collects the commands most people actually need: verifying a
download is genuine, building from source, using a wallet, and running a
node. Every command below is shown for both Windows and Linux/Whonix.

A few commands that exist in the software are deliberately left out of this
guide -- specifically anything that weakens a node's default security
posture (such as enabling raw block or transaction submission over RPC) or
touches the genesis/consensus parameters directly. Those are not things an
ordinary user, miner, or exchange integrator should need, and leaving them
out here is intentional, not an oversight.


1. Verify your download
------------------------
Before extracting or running anything, confirm the file you have matches
the published hash exactly.

Windows:
    certutil -hashfile freedom-coin-source.zip SHA256

Linux / Whonix:
    sha256sum freedom-coin-source.zip

Compare the result against the hash published alongside the release. If it
does not match exactly, do not extract or run the file -- get a fresh copy
instead.


2. Verify a signed binary
--------------------------
Every published binary is signed. The full public key and its fingerprint
are in the README; import it once, then verify any binary against it.

Windows and Linux (same command, once GPG is installed and the key is
imported):
    gpg --verify frqc-node.exe.asc frqc-node.exe
    gpg --verify frqc-node.asc frqc-node

A "Good signature" confirms the file is genuine and unmodified since it was
signed.


3. Build from source
----------------------
Requires the Rust toolchain at the version pinned in rust-toolchain.toml.

Windows:
    cd freedom-coin
    cargo build --release

Linux / Whonix:
    cd freedom-coin
    cargo build --release

Resulting binaries are in target\release\ (Windows) or target/release/
(Linux).


4. Run the automated tests (optional)
----------------------------------------
Not required to use the software, but useful if you want to confirm
everything checks out on your own machine before trusting it.

Windows and Linux:
    cargo test --release


5. Create a wallet
---------------------
Windows:
    frqc-wallet.exe new mywallet --network mainnet

Linux / Whonix:
    ./frqc-wallet new mywallet --network mainnet

This generates a 24-word recovery phrase. Write it down immediately, by
hand, offline. It is the only way to recover your funds if the wallet file
is ever lost, and there is no other recovery method.


6. Get your receiving address
---------------------------------
Windows:
    frqc-wallet.exe address mywallet

Linux / Whonix:
    ./frqc-wallet address mywallet

Add a number at the end (for example, address mywallet 1) to see additional
addresses from the same wallet.


7. Check your balance
-------------------------
Requires a running node to check against.

Windows:
    frqc-wallet.exe balance mywallet --rpc http://127.0.0.1:9932

Linux / Whonix:
    ./frqc-wallet balance mywallet --rpc http://127.0.0.1:9932


8. Send FRQC
---------------
Windows:
    frqc-wallet.exe send mywallet --rpc http://127.0.0.1:9932 --to <address> --amount <FRQC>

Linux / Whonix:
    ./frqc-wallet send mywallet --rpc http://127.0.0.1:9932 --to <address> --amount <FRQC>

Double-check the recipient address before confirming. Transactions cannot be
reversed once broadcast.


9. Run a node
----------------
Basic node, mainnet, no mining:

Windows:
    frqc-node.exe --network mainnet

Linux / Whonix:
    ./frqc-node --network mainnet

Node with mining enabled, rewards paid to a specific address:

Windows:
    frqc-node.exe --network mainnet --mine --mine-address <your-address>

Linux / Whonix:
    ./frqc-node --network mainnet --mine --mine-address <your-address>

Useful additional flags, safe to combine with either command above:

    --datadir <path>       use a custom data directory instead of the default
    --threads <n>          number of mining threads to use
    --intensity <0-100>    how much CPU to devote to mining
    --prune <n>            keep only the most recent n blocks of full data
    --tor                  route all node traffic through Tor
    --txindex              keep a full index for looking up any past transaction


10. Check node and network status
-------------------------------------
With a node running, open in any browser:

    http://127.0.0.1:9932/dashboard
    http://127.0.0.1:9932/explorer

Both work identically on Windows and Linux -- they are served by the node
itself, not platform-specific tools.


11. Confirm the build is reproducible (optional, technical)
----------------------------------------------------------------
For anyone who wants to independently confirm that a published binary
genuinely matches the published source -- build it twice, from two separate
fresh extractions, and compare.

Windows:
    certutil -hashfile target\release\frqc-node.exe SHA256

Linux / Whonix:
    sha256sum target/release/frqc-node

If two independent builds from the same source produce the same hash, the
build is confirmed reproducible on your machine, exactly as it was
confirmed during development.


Sound money. Quantum proof. No masters.
