Repository navigation
Troubleshooting
- Check that the selected wallet-daemon connection method is intentional.
- For a remote daemon, verify the host and port with the endpoint operator. Re-select or update the saved profile if necessary.
- For a local daemon, make sure the wallet's bundled/local daemon can start and is not blocked by security software or firewall rules.
- Restart the wallet after correcting connection settings, then check the connection and synchronization indicators again.
Do not enter wallet passwords or recovery information into an unfamiliar remote service while troubleshooting.
Distinguish daemon synchronization from the wallet's scan of its own transaction history. A wallet scan start height controls the wallet's scan range; it does not set the blockchain download starting point for the daemon. A later wallet scan height can cause older activity to be absent from the current wallet history.
Network availability, daemon configuration, and the amount of data to process can affect progress. If the problem persists, record the application version, operating system, connection method (local or remote), and a description of the visible status. Do not include wallet files, passwords, recovery phrases, private keys, or unredacted personal data.
Check that synchronization is current and that the activity search/filter is not hiding the transaction. Verify the transaction hash or address using information from a trusted source. A QR code or send proof alone does not confirm that a payment is received.
Confirm that the image is clear and contains a Bytecoin payment QR code. The send view reads a QR from an image file; it does not use a live camera. Unsupported or malformed request fields may be rejected. Review the recipient and amount manually if you enter them instead.
The community MSI is not code-signed. Download it from the project's official release and compare its SHA-256 value to the release manifest. If you cannot verify the checksum, do not install it.
Report the wallet version, operating system, connection type, and exact error text. Redact addresses or transaction details if you do not want them public. Never post wallet files, passwords, recovery words, private keys, or unredacted logs that contain sensitive information.