This is a proposal on minimizing the impact of the consensus-breaking changes which may be scheduled for the v0.9 release.
Introduce a hardcoded fix performing mapping from existing schema IDs (RGB20 and RGB21) with the old consensus to a new schema source fixing issues and using new encoding and rules (global state, metadata determinism, consensus ordering, non-constant field/state types etc).
Do a web service which will accept stash in the old format and will re-issue all tokens under it with the new format returning an "upgraded stash". Existing software on a first launch must contact this web service and perform an upgrade of the stash to use the new consensus.
dr-orlovsky
commented
1 year ago
This is a proposal on minimizing the impact of the consensus-breaking changes which may be scheduled for the
v0.9release.Introduce a hardcoded fix performing mapping from existing schema IDs (RGB20 and RGB21) with the old consensus to a new schema source fixing issues and using new encoding and rules (global state, metadata determinism, consensus ordering, non-constant field/state types etc).
Do a web service which will accept stash in the old format and will re-issue all tokens under it with the new format returning an "upgraded stash". Existing software on a first launch must contact this web service and perform an upgrade of the stash to use the new consensus.