git / moonbite-network / docs/WALLET.md · raw

# Using the BigCoin WalletBigCoin ships two wallet front-ends over the same wallet engine:- **`bigcoin-qt`** — graphical (GUI) wallet, good for everyday use.- **`bigcoind` + `bigcoin-cli`** — headless daemon plus command-line client, good  for servers, integrations, and scripting.Both use the standard Bitcoin/Litecoin Core JSON-RPC interface.---## Address formatsBigCoin supports two address styles:| Type              | Looks like                    | Notes                          ||-------------------|-------------------------------|--------------------------------|| Base58 (legacy/P2SH) | starts with `M` (e.g. `M7f...`) | address prefix is `M`       || Bech32 (native SegWit) | `moon1...`                 | bech32 HRP is `moon`, lowercase |Prefer `moon1...` (bech32) addresses where supported — they are cheaper to spendand have better error detection. Legacy `M...` addresses remain valid.---## Installing and running### GUIDownload/build `bigcoin-qt`, then launch it. On first run it creates a datadirectory and (optionally) a wallet. Just run:```bashbigcoin-qt```### Daemon + CLIStart the background daemon:```bashbigcoind -daemon -server \  -rpcuser=youruser -rpcpassword=yourpass```Then talk to it with the CLI:```bashbigcoin-cli getblockchaininfo```(For a persistent config file instead of command-line flags, see[NODE_SETUP.md](NODE_SETUP.md).)---## Creating a new address```bashbigcoin-cli getnewaddress# -> moon1qexampleaddressxxxxxxxxxxxxxxxxxxxx```You can label addresses and request a specific type:```bashbigcoin-cli getnewaddress "savings"            # labeledbigcoin-cli getnewaddress "" "bech32"          # force bech32 (moon1...)bigcoin-cli getnewaddress "" "legacy"          # force legacy (B...)```In the GUI, use **Receive -> Request payment** to generate an address.---## Checking your balance```bashbigcoin-cli getbalance            # confirmed spendable balancebigcoin-cli getbalances           # detailed: trusted / untrusted / immaturebigcoin-cli getwalletinfo         # wallet-wide info```- **Immature balance** = mined coinbase rewards still waiting for 100  confirmations.- **Untrusted pending** = incoming unconfirmed transactions.---## Sending BIG```bashbigcoin-cli sendtoaddress "<address>" <amount>```Example:```bashbigcoin-cli sendtoaddress "moon1qrecipientxxxxxxxxxxxxxxxxxxxxxxxxx" 12.5```Useful options:```bash# subtract the fee from the amount sent (recipient receives amount - fee)bigcoin-cli sendtoaddress "<addr>" 12.5 "" "" true# set a specific fee rate (BIG/kvB) for one sendbigcoin-cli -named sendtoaddress address="<addr>" amount=12.5 fee_rate=0.0001```Always double-check the destination address before sending. **Transactions areirreversible** once confirmed.---## Backing up your walletBigCoin (like modern Bitcoin/Litecoin Core) can use either legacy `wallet.dat`BerkeleyDB wallets or newer **descriptor** wallets. Back up whichever you have.### Safe on-disk backup (works for any wallet type)```bashbigcoin-cli backupwallet "/secure/path/bigcoin-wallet-backup.dat"```This produces a consistent copy even while the wallet is in use. Store itsomewhere safe and offline.### Descriptor / private-key exportFor descriptor wallets you can export the descriptors (which contain the keys):```bashbigcoin-cli listdescriptors true    # includes private keys — handle with care!```Keep any exported descriptors or keys **encrypted and offline.** Anyone with themcan spend your coins.### GUI backup**File -> Backup Wallet...** writes a `wallet.dat` copy you can store safely.---## Encrypting your walletEncrypt the wallet so a passphrase is required to spend:```bashbigcoin-cli encryptwallet "a-long-strong-passphrase"```After encrypting:- The wallet daemon restarts and the old unencrypted keys are gone.- **Make a fresh backup after encrypting** (the keypool changes).- To spend, unlock temporarily:```bash# unlock for 60 secondsbigcoin-cli walletpassphrase "a-long-strong-passphrase" 60# change the passphrase laterbigcoin-cli walletpassphrasechange "old-pass" "new-pass"```In the GUI, use **Settings -> Encrypt Wallet**.> If you forget your passphrase, **there is no recovery.** The coins are lost.---## CRITICAL: seed and backup safety**Your keys, your coins. Lost keys = lost coins forever.**There is no company, admin, or "forgot password" link that can restore access toa BigCoin wallet. The rules that make BigCoin trustless also mean **you** arefully responsible for your keys.Follow these rules:1. **Back up immediately** — right after creating (and again after encrypting)   your wallet. Use `backupwallet` or the GUI backup.2. **Keep multiple copies** in separate physical locations (e.g. an encrypted USB   drive and a printed/handwritten copy in a safe).3. **Never store keys or backups in plaintext** in cloud storage, email, chat, or   screenshots.4. **Guard your encryption passphrase** as carefully as the wallet itself — losing   it is the same as losing the wallet.5. **Test your backup** by restoring it on a spare/offline machine before you rely   on it.6. **Beware malware and phishing.** Anyone who obtains your `wallet.dat`,   descriptors, or private keys can drain your funds instantly and irreversibly.If in doubt, assume that a lost or leaked backup means lost or stolen coins. Actaccordingly.