I’m very interested in seeing the plans for BitcoinOS develop.
About token migration, I have stated my preferences earlier, and they have not changed. Let SovrynLayer/BitcoinOS be without its own token. Let SOV =rSOV and let it remain on Rootstock. Define a set of roles and privileges on BitcoinOS (such as the role of securing the layer, governing the layer, being a market maker, and so on) some or all of which are accessible by burning rSOV on Rootstock. rSOV can continue to accrue value on Rootstock as more roles get defined or the roles come to be in increasing demand; making rSOV scarcer and vehicle for fresh demand.
Having two tokens, migrating, it’s liable to create confusion and its unnecessary. There will be zillions of rollups that need to have a token to fund their development; Sovryn has an advantage by being a first mover but the advantage is precisely that it doesn’t need to have a token on the new layer; let’s make use of that advantage or risk becoming just one of many.