Repository navigation
Security and Privacy
- Use a strong, unique wallet password where supported.
- Keep wallet files and any recovery information in secure, separate backups.
- Never share passwords, recovery words, private keys, or wallet files with anyone.
- Do not store recovery information in screenshots, public cloud folders, chat messages, or this wiki.
- Download wallet binaries only from the project's official GitHub releases and verify their SHA-256 checksums.
Password confirmation before sending is available for supported local wallet configurations. Behavior can differ by wallet and daemon type; follow the prompts shown by the application. A password prompt is not a reason to reveal the password to another person.
Use the wallet's own backup or export options for the wallet type you use. Keep a copy in a secure location separate from the computer running the wallet, and make sure you know how that wallet type is restored before relying on a backup. Do not assume a wallet file alone is sufficient for every wallet type.
Never upload a wallet file or recovery material to GitHub, issue trackers, public file-sharing services, or support chats.
The wallet can connect through a configured wallet daemon. If you use a remote daemon, that service may observe connection metadata and wallet-related requests. Choose an endpoint you trust; using a remote endpoint does not make it equivalent to running your own node.
The send form exposes a transaction privacy/anonymity-level choice. Higher values may increase transaction size and fee; a setting is not a guarantee of complete anonymity. Fee levels influence the fee rate, not a guaranteed confirmation time.
Payment IDs, transaction hashes, and send proofs can disclose information when shared. Share only what is needed with the intended party.
Bytecoin Wallet — bytecoin.world Community Edition is independently maintained by the community. The Windows MSI is not code-signed; verify its checksum and source before installation.