Update data stores for v1.9.15 #7035
Conversation
|
@alvasw @HenrikJannsen @jmacxx Could anyone of you ACK this PR? Thanks! |
There was a problem hiding this comment.
Please also consider setting PROPOSAL_412_ACTIVATION_DATE which should be set to a few weeks after release date. See bisq-network/proposals#412 (comment)
As both traders need to have the exact same distribution for the delayed payout transaction we would need to roll that change out with a activation blockheight sufficiently far in the future so that we can be sure to release and enforce the updated version.
| @@ -45,7 +45,7 @@ public class Version { | |||
| */ | |||
| public static final List<String> HISTORICAL_RESOURCE_FILE_VERSION_TAGS = Arrays.asList("1.4.0", "1.5.0", "1.5.2", | |||
| "1.5.5", "1.5.7", "1.6.0", "1.6.3", "1.6.5", "1.7.2", "1.7.4", "1.8.0", "1.8.1", "1.8.3", "1.9.0", "1.9.3", | |||
| "1.9.5", "1.9.6", "1.9.7", "1.9.10", "1.9.11", "1.9.13"); | |||
| "1.9.5", "1.9.6", "1.9.7", "1.9.10", "1.9.11", "1.9.13", "1.9.15"); | |||
There was a problem hiding this comment.
VERSION = "1.9.15"
HISTORICAL...TAGS would have 1.9.14 (the prior version) appended.
There was a problem hiding this comment.
This is correct! 1.9.14 was a hotfix release without data store updates.
|
I can confirm that my hashes on a light node are the same. |
Light node in light mode and full node in dark mode
