Quique, let’s make sure ani and you aren’t working on the same thing, are both of you working on the backend contract?
We could mint a billion wHNY on Mainnet or 10,000. Both don’t mater as they will be locked (I lean towards 10k since it’s temporary anyway and Without 100% knowing of how the contract works I don’t want the risk of 1B tokens getting hacked). There shouldn’t be a token supply confusion. calling it wHNY should help (because most everyone knows wETH & wBTC) and secondly this is temporary and a work around until done the right way.
@willjgriff This brings up next point, how do we ensure we don’t have 2 tokens on Mainnet. This does not mater as wETH and ETH are both on Mainnet so we too will have wHNY and HNY.
But if we absolutely needed to remove 2nd token at Omnibridge golive couldn’t we safely leave it in the code the ability to “turn off” the wrapping feature and burn remaining wHNY still left in contract. Meaning you will always be able to exchange wHNY for HNY but at Omni go live you will no longer be able to exchange HNY for wHNY. This would eliminate wHNY over time. As wHNY is exchanged for HNY the wHNY is burned.
It is possible wHNY could be valued higher than HNY due to scarcity but it won’t have a use case.