Refactor: Easier support for chains with multiple genesis assets #164
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some POC chains may be interested in having more than one genesis asset for spiking the additional step of issuing a second asset (or more) for a particular demonstration. Presumably they would copy and modify CElementsParams to create their own chain.
For the 2 way peg, as a next step, a multiasset chain can support pegs to the same parent chain with different federation scripts, or even pegged to different parent chains. We don't support that yet, but in the same way this makes testing that kind of extension easier to test without needing to issue new pegged assets during the tests. Issuing them on the fly can be a next step.
Intentionally, the new "feature" isn't tested, for that would require either a "genesis block id HF" or a new chain. I would prefer if that is done in a later PR (see jtimon/elements@e13-multi-genesis...jtimon:e13-multi-genesis-test for a WIP) and this is merged without testing first purely on the grounds that the behavior should remain perfectly equivalent and if at any point this is not the case for this PR, it should be nacked by reviewers.
Dependencies: