*Since Proposal MR32 passed but executed failed with bad origin in General Admin Track, this proposal has been reinitiated in Root Track now.
Summary
This proposal aims to amend the previous asset registration proposal by changing the sufficient value of the registered xcvKSM, xcvMOVR and xcvBNC from ‘false’ to ‘true’.
Issue Statement
Recently, we have discovered that xcvToken , Bifrost liquid staking tokens “vTokens”, cannot create trading pairs when integrating with Native Moonbeam and Moonriver DEXs such as Stellaswap, Beamswap, and Solarbeam. (*The issue had fixed on Moonbeam.) The reason is that when xcvToken is registered, the sufficient parameter is set to false, which prevents any address from receiving xcvToken without having the native token GLMR. As a result, the contract for creating trading pairs fails.
Failed TXes for example:
On Beamswap V2: Moonbeam Transaction Hash: 0xf2afc1c170... | Moonbeam
V2: Moonbeam Transaction Hash: 0x97ca37b9b6... | Moonbeam
V3: Moonbeam Transaction Hash: 0x3de1e740eb... | Moonbeam
On Solarbeam:
As the Moonbeam team reported: “If an asset is sufficient it means that it can be sent to an account that has no balance of a native token. If an asset is not sufficient, it can’t be sent to an account that has no balance of the native token.”
Although sending GLMR or MOVR to a DEX pool contract in advance to avoid sufficient issue can be solution, but pool contract needs to have a payable function to accept GLMR, which unfortunately most DEXes pool contracts doesn’t have.
So, we would need to change sufficient from false to true to ensure that any address can still receive xcvKSM, xcvMOVR and xcvBNC without MOVR.
hopefully this one passes, I am in continue favor of supporting this.