VextaProject/ Vexta
Vexta Vexta-CPU-Miner Vexta-Android-Wallet
Watch
1
0
Fork
You've already forked Vexta
 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Initial Vexta Core v0.1.0 release

Browse source
This commit is contained in:
Capri 2026-07-15 14:07:28 +00:00
commit 25c454329d
2481 changed files with 689289 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

38
doc/release-notes/release-notes-0.4.1.md Normal file
View file

@ -0,0 +1,38 @@
DigiByte version 0.4.1 is now available for download at:
http://sourceforge.net/projects/digibyte/files/DigiByte/digibyte-0.4.1/
This is a bugfix only release based on 0.4.0.
Please report bugs by replying to this forum thread.
MAJOR BUG FIX (CVE-2011-4447)
The wallet encryption feature introduced in DigiByte version 0.4.0 did not sufficiently secure the private keys. An attacker who
managed to get a copy of your encrypted wallet.dat file might be able to recover some or all of the unencrypted keys and steal the
associated coins.
If you have a previously encrypted wallet.dat, the first time you run wxdigibyte or digibyted the wallet will be rewritten, DigiByte will
shut down, and you will be prompted to restart it to run with the new, properly encrypted file.
If you had a previously encrypted wallet.dat that might have been copied or stolen (for example, you backed it up to a public
location) you should send all of your digibytes to yourself using a new digibyte address and stop using any previously generated addresses.
Wallets encrypted with this version of DigiByte are written properly.
Technical note: the encrypted wallet's 'keypool' will be regenerated the first time you request a new digibyte address; to be certain that the
new private keys are properly backed up you should:
1. Run DigiByte and let it rewrite the wallet.dat file
2. Run it again, then ask it for a new digibyte address.
wxDigiByte: new address visible on main window
digibyted: run the 'walletpassphrase' RPC command to unlock the wallet, then run the 'getnewaddress' RPC command.
3. If your encrypted wallet.dat may have been copied or stolen, send all of your digibytes to the new digibyte address.
4. Shut down DigiByte, then backup the wallet.dat file.
IMPORTANT: be sure to request a new digibyte address before backing up, so that the 'keypool' is regenerated and backed up.
"Security in depth" is always a good idea, so choosing a secure location for the backup and/or encrypting the backup before uploading it is recommended. And as in previous releases, if your machine is infected by malware there are several ways an attacker might steal your digibytes.
Thanks to Alan Reiner (etotheipi) for finding and reporting this bug.