MultiBit Documentation

Procedure

1. 01

   Check the software source

   Identify the exact release and its publisher. Match its supported operating system and architecture to your computer; a platform logo alone does not establish compatibility.

2. 02

   Preserve existing wallet data

   If a wallet already exists on this device, make a separate backup using the procedure for that wallet format. Do not replace or delete wallet files during setup.

3. 03

   Create or restore

   Creating a wallet establishes new signing keys. Restoring requires recovery material compatible with the wallet software. Follow the actual release’s instructions; do not enter secrets on this website.

4. 04

   Complete the backup and synchronize

   Record the required recovery material privately, check that it is complete, and allow synchronization to catch up before relying on the balance.

Reference

Release identity

Match the version, filename, operating system, and architecture with an authenticated release announcement.

Checksum

A matching hash establishes that the file matches the published hash. It does not establish who published it if both came from a compromised source.

Signature

A valid signature connects the file to a signing key. Authenticate that key independently; a key downloaded beside the file is not sufficient by itself.

Procedure

1. 01

   Obtain the package

   Use an identified publisher destination rather than a search advert, unsolicited message, or recovery-service link.

2. 02

   Check the verification material

   Compare the published hash or verify the signature with a trusted verification tool. If the publisher provides neither, do not treat an arbitrary third-party hash as proof of authenticity.

3. 03

   Install without deleting data

   Close any running wallet before changing application files. Preserve wallet data and backups, then follow the platform instructions supplied with the package.

Reference

Application files

The software that opens a wallet. Copying these files alone does not back up the keys.

Wallet file

May include keys and other wallet data, depending on the format. Preserve the file and any credentials needed to open it.

Recovery material

Recovery words, keys, or other data required by the wallet format. Never assume recovery words cover a wallet that uses a different backup method.

Local password

Protects access to local wallet data where encryption is used. A password is not a substitute for missing recovery material.

Procedure

1. 01

   Identify the format

   Use the backup procedure documented for the exact wallet. Record which files or recovery details are required, without putting secrets in public notes.

2. 02

   Keep a separate copy

   Store the backup away from the running computer. Avoid cloud documents, screenshots, shared drives, and sending secrets through messages.

3. 03

   Check recovery safely

   Use the format’s documented verification or restore procedure. Keep the original intact until you have confirmed access to the expected addresses and funds.

Procedure

1. 01

   Obtain the destination

   Use the wallet’s receiving workflow. Confirm the address is for Bitcoin and belongs to the intended wallet. A public address can be shared; its private key cannot.

2. 02

   Share the payment request

   Copy the complete address or its QR code. If an amount is included in a payment request, confirm the unit and amount with the sender. Keep invoice or contact notes private.

3. 03

   Inspect the received transaction

   Compare destination and amount against the request. A payment may appear before it is included in a block; check its confirmation count.

Reference

Amount

The value paid to the recipient. Verify the displayed unit rather than assuming it is BTC.

Network fee

The fee offered for transaction inclusion. Fee rate and transaction size affect the total fee.

Total

The recipient amount plus the network fee. Review both before signing.

Procedure

1. 01

   Enter the destination

   Use the complete address and compare it with the recipient’s request. Clipboard substitution can change a pasted destination; do not check only an abbreviated display.

2. 02

   Review amount and fee

   Confirm units, recipient amount, network fee, and total. A fee estimate indicates network conditions, not a guaranteed confirmation time.

3. 03

   Authorize once and record the transaction

   Review again before signing. After broadcast, keep the transaction ID and monitor its status. Do not create a second payment just because the first remains pending.

Reference

Synchronizing

The wallet is catching up with network data. The displayed history or balance may be incomplete.

No peers connected

Saved data may remain available, but new network information and broadcast require connectivity.

Pending / unconfirmed

No block inclusion is established yet. Network demand, fee levels, and transaction policy affect the wait.

One confirmation

The transaction is included in a block. In SPV, an inclusion proof is checked against the header chain.

Additional confirmations

Following blocks increase the transaction’s depth in the chain. The amount does not change.

Transaction ID

Identifies the transaction. Sharing it may reveal payment history, so use public explorers with that privacy trade-off in mind.

Procedure

1. 01

   Check synchronization first

   Confirm that the wallet has caught up before interpreting a missing payment or unexpected balance.

2. 02

   Identify the transaction

   Match the transaction ID, recipient, amount, and status. Distinguish an unconfirmed transaction from one that has not been broadcast.

3. 03

   Preserve data while investigating

   Do not delete wallet files, resend automatically, or install an unsolicited recovery tool. Record the visible state and seek issue-specific assistance.