Added the genesis_address in the validation_stamp. It's written on disk only on IO transaction, because the chain storage is written in a file named by the genesis, so there's no point to duplicate the data there.
There's a migration script to run on all legacy IOs
[ ] Update migration version when decided which version it'll be
Fixes #1562
Type of change
New feature (non-breaking change which adds functionality)
How Has This Been Tested?
Updated the code to store every tx also as IO then run a release upgrade on 4 nodes.
Chain & IO storage both returned the genesis address on legacy and new transactions
Checklist:
My code follows the style guidelines of this project
I have performed a self-review of my own code
I have commented my code, particularly in hard-to-understand areas
I have made corresponding changes to the documentation
My changes generate no new warnings
I have added tests that prove my fix is effective or that my feature works
New and existing unit tests pass locally with my changes
Any dependent changes have been merged and published in downstream modules
Description
Added the genesis_address in the validation_stamp. It's written on disk only on IO transaction, because the chain storage is written in a file named by the genesis, so there's no point to duplicate the data there. There's a migration script to run on all legacy IOs
Fixes #1562
Type of change
How Has This Been Tested?
Updated the code to store every tx also as IO then run a release upgrade on 4 nodes. Chain & IO storage both returned the genesis address on legacy and new transactions
Checklist: