Right now the legacy code for activation is all commented out so we can run testnet builds in our own way, if we uncomment it and keep the history of the legacy Omni, we can imitate the activations for their history of features and get up chronologically to ours, and test it out on testnet. To make it professional, we could remove the old Omni code and legacy layers of activations, and have a new history, threading through the code base to remove old stuff as we go, but this is fraught with booby traps and a lot of work. To get a good testnet release out that could preceed the launch of mainnet functionality, we need to get this working in a short-cut form.
Right now the legacy code for activation is all commented out so we can run testnet builds in our own way, if we uncomment it and keep the history of the legacy Omni, we can imitate the activations for their history of features and get up chronologically to ours, and test it out on testnet. To make it professional, we could remove the old Omni code and legacy layers of activations, and have a new history, threading through the code base to remove old stuff as we go, but this is fraught with booby traps and a lot of work. To get a good testnet release out that could preceed the launch of mainnet functionality, we need to get this working in a short-cut form.