New draft proposal:
Deploy new BAM contract on ethereum.
Move liquidity form BSC to ethereum, pair BAM 2.0 to ETH
Airdrop tokens to all holders on ETH
Enable staking
(Optional) Wrap BSC token (note - anyone can do this, do we want to do this as a DAO? Think this is a separate proposal/discussion)
Because the above - the contract is not renounced and the liquidity pool is unlocked, this is fairly “easy” compared to the last migration, and requires zero interaction from the token holder.
We have a developer that has already deployed a test contract successfully, so we think we are ready to move on this.
Old discussion:
Correct the contract issue (token/ticker name switch) and do the following:
- Create a duplicate smart contract on ETH (minor differences just based on the chain)
- Deploy 1/2 of BAM liquidity on ETH and 1/2 on BNB (we’d lose some gas fees along the way but it should be fairly nominal post merge)
- For every 2 tokens that exist right now on BNB, there will be 1 on eth, and 1 on BNB - we would do a “flash airdrop” in a very narrow window
Still have to work out how an audit would work. We are going to contact Certik and see if they aren’t wiling to give us a hand given the fact they…really didn’t do a very good job…
Discuss…poke holes
I’ve reviewed this conceptually with Keith and a few others and it’s radically simple, just requires precise execution.
This would create an amazing opportunity however to get $BAM onto ETH quickly, and then scale down the transaction tax fairly quickly, and leave us with an ERC20 compliant token/smart contract on both ETH and BNB rather than wrapping tokens…
Net result: 50M supply on ETH, 50M supply on BNB, ERC20 compliant smart contracts on both chains…opens many doors for web 3 integrations.