Following results of latest Snapshot here the DAO has chosen to forego facilitating the launch of AKITA on Solana, and has stated that it only wants to explore adding more support for Avalanche network based AKITA (a-AKITA). Below is some research I have done for the DAO on this topic.
- Note for future Solana discussion: I was successful in using Wormhole to wrap AKITA and send it to Solana and back to Ethereum as unwrapped AKITA, so the function of a bridge is existing. Liquidity for trading, price feed alignment between networks, custom UI, etc would still need to be explored.
Multichain
Due to Multichainās ceasing operations due to CEO/tech team being taken into custody, there is no bridge for Ethereum-based AKITA (e-AKITA) to Avalanche. With the Multichain bridge non-functional, there will be no additional minting of a-AKITA. The supply of a-AKITA that exists on Avalanche is limited to roughly 104B tokens. This is likely why there have been larger price discrepancies on TraderJoe vs UniSwap.
Adding liquidity to a-AKITA
In order to add liquidity to Avalanche, the DAO will need to establish a SAFE multisig on the Avalanche network. Our Pangolin multisig on Avalanche is not adequate for interacting with dApps. This will be a different address than our Ethereum SAFE multisig, and all assets from the current Pangolin multisig will need to be transferred to the new SAFE. With the Avalanche SAFE address established, the DAO can then use Synapse, Stargate, or a similar bridge with the additional function of supplying an alternative recipient address to receive funds.
Adding additional liquidity to Avalanche becomes difficult without the bridge for our e-AKITA tokens. In order to add liquidity, we would need to divest (swap) our e-AKITA to acquire ETH or USDC. These tokens would need to be swapped for the necessary amount of a-AKITA and AVAX to add to the LP. In swapping for a-AKITA, the DAO might be losing some value due to the price gap with e-AKITA.
Other Multichain tokens
Some other tokens who were affected by Multichain have chosen to establish a new bridge, minting a new token under a new contract. Because they have full control over their contracts, they are able to pull the LP, re-issue new tokens to replace the old ones, airdrop those new tokens to holders, and re-establish the LP for the new token.
AKITA is an ownerless token, the supply is fixed, and there can be no re-issuing of tokens. The Akita DAO is unable to follow the process of these other tokens.
Alternative Solution for a-AKITA
- Akita DAO would need to establish a new bridge through custom development or partnership with a pre-existing bridge (e.g. Singularity DAO which was also affected by Multichain). This bridge would mint a new AKITA token for Avalanche.
- The DAO would need to then pull the LP from TraderJoe, withdrawing the old a-AKITA and AVAX from the trading pool. This would require substantial advanced communication to AKITA holders, with plenty of lead time for other LP holders to exit their position. It could be anticipated this will lead to some sell-off and weakening of the overall LP, but it is a necessary step.
- Since the old a-AKITA pulled from the LP would be worthless, the value of the LP is essentially 50% of its old value. If the DAO wanted to launch the new token with equivalent or more liquidity, then it must bridge those additional funds to Avalanche.
- With a new LP in place for the new token, then Akita DAO could either airdrop the new token to holders, or it would use a Migration tool similar to what Singularity DAO has done here.
- A new price feed oracle or other tool must be in place with the new bridge in order to align the new a-AKITA token price with the e-AKITA token price.
Note: I have already established some communication with Singularlity DAO. Their website clearly lists their services, which could also be helpful for Akita DAO ā vesting, staking pools, vaults, etc. Akita DAO could reach out to Singularity DAO to discuss possible partnership.