How To Start with Bitcoin Core

This guide walks you through installing Bitcoin Core, enabling its JSON‑RPC server, configuring authentication via bitcoin.conf or cookie file, connecting your Bitcoin Core node to HodlDesk by supplying RPC host, port, and credentials (or cookie‑based auth), then loading and verifying a wallet in HodlDesk’s portfolio dashboard. By following these steps, you’ll securely integrate your full node into the HodlDesk ecosystem and start tracking balances, generating addresses, and executing commands directly from the app.

Prerequisites

• Operating System: Windows 10/11 (64‑bit) or macOS 10.14+

• Bitcoin Core: Downloaded and installed

• HodlDesk: Installed and updated to the latest version

---

1. Install and Launch Bitcoin Core

1.1 Download Bitcoin Core

1. Go to the official download page and choose your OS installer:

   • Windows/macOS/Linux installers are available

2. (Optional but recommended) Verify the PGP or SHA256 signatures as documented on bitcoin.org.

1.2 Initial Run

• Launch Bitcoin Core for the first time. It will perform an initial blockchain synchronization. Ensure you have at least 350 GB free and a stable Internet connection.

---

2. Enable JSON‑RPC and Configure bitcoin.conf

2.1 Locate bitcoin.conf

• macOS: ~/Library/Application Support/Bitcoin/bitcoin.conf

• Windows: %APPDATA%\Bitcoin\bitcoin.conf

If the file does not exist, create it in the above directory.

2.2 Add RPC Settings

Open bitcoin.conf in a text editor and add the following lines:

iniنسختحرير# Enable RPC server
server=1

# Authentication: either username/password…
rpcuser=your_rpc_username
rpcpassword=your_strong_random_password

# …or cookie-based auth (comment out rpcuser/rpcpassword)
# cookieauthentication=1

# Allow only local connections
rpcallowip=127.0.0.1

# Default RPC port (8332) is used unless overridden
# rpcport=8332

• The server=1 line turns on RPC for both bitcoind and bitcoin-qt .

• Cookie‑based authentication is enabled by default if no rpcpassword is set; it reads credentials from .cookie file.

2.3 Restart Bitcoin Core

• After saving bitcoin.conf, restart Bitcoin Core to apply changes. The node will now listen for RPC on port 8332 by default.

---

3. Connect Bitcoin Core in HodlDesk

3.1 Launch HodlDesk

• Open the HodlDesk application and wait for the main dashboard to appear.

3.2 Add a New Wallet

1. Click Add Wallet in the sidebar.

2. Choose Connect Bitcoin Core from the wallet list.

3. In the connection dialog, enter:

   • Host: 127.0.0.1

   • Port: 8332

   • RPC User/Password: If you set rpcuser/rpcpassword, enter those; otherwise leave blank for cookie auth.

4. Click Test Connection. HodlDesk sends a getblockchaininfo RPC to verify the node is reachable and synced.

---

4. Load and Sync Your Wallet

4.1 List Available Wallets

• HodlDesk invokes the listwallets RPC to retrieve currently loaded wallets. If your wallet isn’t loaded, proceed to load it.

4.2 Load an Existing Wallet

• Use the loadwallet RPC within HodlDesk to specify your wallet file (e.g., wallet.dat), which loads it into the node’s memory.

4.3 Fetch Wallet Info

• Once loaded, HodlDesk calls getwalletinfo to obtain balance, name, and other metadata.

---

5. Verify and Explore

5.1 Generate a New Address

• In the wallet view, click New Receive Address. HodlDesk calls getnewaddress and displays the fresh address for receiving funds Getting Started — Bitcoin.

5.2 View Balances and Transactions

• Your Bitcoin balance, recent transactions, and on‑chain analytics will populate the HodlDesk dashboard automatically.

---

6. (Optional) PSBT / Cold‑Storage Workflow

1. Create PSBT: In HodlDesk, select Create Unsigned Transaction to call walletcreatefundedpsbt, exporting a PSBT file.

2. Sign Offline: Load the PSBT into a hardware wallet or offline Bitcoin Core instance to sign.

3. Broadcast: Use Import PSBT in HodlDesk, which calls walletprocesspsbt (for final signing) and broadcast to send the raw transaction.

---

Troubleshooting

• Connection Refused: Verify Bitcoin Core is running, server=1 is set, and port 8332 is open.

• 401 Unauthorized: Double‑check rpcuser/rpcpassword or switch to cookie auth.

• Wallet Not Listed: Ensure your wallet is created and located in the node’s walletdir; then reload the connection flow.