# Beta 1.5
1. This release is primarily a maintenance release for Beta 1.4. There was a regression in Chia Proof of Space (chiapos) that came from our efforts to speed up plotting on Windows native. Now k>=32 plots work correctly. We made additional bug fixes and corrected limiting small k size generation.
2. We have implemented a workaround for the `chia start` issues some were having upon crash or reboot. We will be rebuilding start and stop to be robust across platforms. This release re-includes `chia-start-harvester`.
3. Coloured coins now have a prefix to help identify them. When sending transactions, the new prefix is incompatible with older clients. Additionally, the user interface now refers to chia coins with their correct currency code of XCH.
4. We have made significant changes to the full node database to make it more reliable and quicker to restart. This requires re-syncing the current chain. If you use `chia init` then sync on first start will happen automatically. "$CHIA_ROOT" users will need to delete `$CHIA_ROOT/db/*` before starting Beta 1.5. This also fixes the simulation issue in Beta 1.4 where tips could go "back in time."
5. We have added an option to `chia-create-plots` to specify the second temporary directory. Creating a plot is a three step process. First a working file ending in `.dat.tmp` is created. This file is usually 5 times larger than the final plot file. In the later stages of plotting a second temp file is created ending in `.dat.2.tmp` which will grow to the size of the final plot file. In the final step, the `.dat.2.tmp` is copied to the final `.dat` plot file. You can now optionally set the directory for the `.dat.2.tmp` file with the `-2` flag. An example use case is plotting on a ramdisk and writing both the second temp file and the final file out to an SSD - `chia-crate-plots -n 1 -k 30 -t /mnt/ramdisk -2 /mnt/SSD -d /mnt/SSD`.
6. There was a bug in Timelord handling that could stop all VDF progress.
7. `chia init` properly migrates from previous versions including the k>=32 workaround. Additionally, the farming target key is checked to make sure that it is the valid and correct public key format.
## Known issues
1. uPnP support on Windows may be broken. However, Windows nodes will be able to connect to other nodes and, once connected, participate fully in the network.
2. Currently, there is no way to restore a Coloured Coin Wallet.
* Fix create plot issue, do not recreate plots that exist on another drive
* Fix double harvester handshake with farmer
* Full node sends ping to wallet
* Async constructor for harvester, and instance threadpool
wjblankeandGitHub
Gene HoffmanandGene Hoffman
Bill BlankeandGene Hoffman
Matthew HowardandGene Hoffman
Mariano SorgenteandGene Hoffman
fchirica
cryptonoob42andGene Hoffman
Yostra
Richard Kiss