Frequently Asked Questions
Please remember that ElkNet only sends the $ELK Token from one chain to another. So if you don't see $ELK on the chain you sent to after adding the other chain to your MetaMask, make sure you have added the $ELK Token's Contract Address to MetaMask on each chain so you see it in your wallet. The Contract Address for ELK is the same on every chain:
To do this, simply click "Import Tokens" on MetaMask, and then paste the address above into the custom tokens field, MetaMask should autofill the rest of the details.
If this does not work, please ensure your RPC is correct, and try switching it to an alternate one if possible (go to settings in MetaMask > Networks > the chain you are having trouble with, and change the RPC field). A collection of RPCs can be found here in the docs.
Please ensure you have your transaction number from the ElkNet page at https://app.elk.finance/#/ElkNet, the status of the transaction (Initiated, Processing, or Completed), the chain the transfer it was sent from/to, and how long it has been stuck for. Please provide these details to the Bridge Support Chat on Telegram. The transaction number has been circled in the picture below, and is in the format T00-00000-0000. Transactions will eventually come through.
No $ELK has EVER been lost in an ElkNet transfer, and it is 100% safe and all transactions are logged and pending on the blockchain. Problems with congestion, overloaded RPCs, and fluctuating gas prices on popular/high traffic networks delay transfers for the ElkNet. This is out of our control, and we are working to improve functionality daily. If you are stuck, please be patient. The transaction will come through on it's own. Usually transfers are as fast as 7 seconds, but sometimes RPCs get busy and this can take a lot more time! Waiting 30 minutes or so and checking again is always a great strategy.
Not to worry. The UI is sometimes wrong, and may take a lot longer to reflect changes. Go into MetaMask's transaction history and make sure the transaction has gone through there, if it has, just ignore the PENDING message in the UI.
No. Admins from Elk Finance will NEVER message you first. If this happens, assume that they are a scammer and not to be trusted. Do not follow any of these instructions, such as "resyncing you wallet".
The explorer and MetaMask only indicate that ElkNet has received your $ELK and is sending it to the other chain, not that the whole chain was complete. It still must be burnt on one chain, and sent to your wallet on the other chain. Please reference the transaction number in the example below at https://app.elk.finance/#/ElkNet, and refresh the page periodically. This will say either Initiated, Processing, or Completed.
Please ensure you are using the browser in the MetaMask app, not Safari or Chrome.
If you are not receiving ther prompt in MetaMask to confirm the transaction, then please refresh the page. If you are receiving it and it fails immediately, first try switching your RPC to an alternate one if possible (go to settings in MetaMask > Networks > the chain you are having trouble with, and change the RPC field). A collection of RPCs can be found here in the docs.
If this does not work, please try increasing the gas limit and price. You can do this by hitting "edit" in MetaMask BEFORE submitting the transaction. Then, increase the "gas limit" in the top field by adding a 1 to the first digit (e.g. put 450000 vs 350000) and add 1 to the first digit to the "gas price" on the bottom (e.g., put 6000 vs 5000).
Elk defaults to Avalanche chain since it was the first chain Elk launched on. To use Matic, for example, just change your network to Matic on your MetaMask and you will see it change to Matic in the ElkDex. If you need to add other chains, try connecting your wallet to https://chainlist.org/ and adding additional chains.
If the token is relatively new, it may not be whitelisted yet. Fortunately, you can manually import it into the swap/pool fields by copying and pasting the token address. If you don’t know the address, visit the Analytics page and click on the token. From there, you can either copy the token address, or you can click the ‘trade’ or ‘add liquidity’ buttons at the top. You can also use this token address to add the token to your MetaMask or other crypto wallet.
All of our ElkDex smart contracts on Avalanche, Polygon, Fantom Opera & Huobi Eco have been successfully audited!
Our ElkNet has not yet been audited. This audit (actually two audits) will probably take place in early Q3. We publish and verify all our code and follow the best practices in terms of security. That said, please remember that most crypto projects are very early and even audited projects are not necessarily safe! Stay safe out there and never invest more than you can afford to lose.
The difference between Elk and traditional bridges is best illustrated in several examples. Say the user trades ETH for, let's say, "Anybridge" ETH (a.ETH). Then the bridge has to have enough a.ETH liquidity on the second chain the user is going to (i.e., exit liquidity) so that it can be transferred over. Then, the user has to convert a.ETH back to ETH, and hopefully that is also close in value due to different amounts of liquidity on different chains to ensure a fair exchange price, all the while paying lots of gas, and taking a hit if there is not enough liquidity for ETH on all chains. When traditional bridges introduce chains, more support is required for each additional chain, and not only do they need ETH liquidity, they need it paired with,. say a.ETH, to not take a big hit when selling. Plus with each new chain on a traditional bridge, the "two way bridge" requires a bridge to each new other chain. So if you have AVAX-ETH you have that bridge, but if you introduce BSC and FTM now you need AVAX-BSC, AVAX-ETH, BSC-ETH, AVAX-FTM, FTM-BSC, ETH-FTM, and it gets exponentially more difficult to maintain with each new chain, as it needs to have an individual bridge with every existing chain, as well as maintain enough exit liquidity on each.
So the difference in how the Elk Multi-Bridge works is that $ELK is actually sent across the mainnet (ElkNet). Let's use sending from AVAX and MATIC as an example. $ELK is effectively burnt on AVAX, decreasing the supply and slightly increasing the price of $ELK on that chain, and minting the $ELK on the other chain, slightly increasing the supply and decreasing the price of $ELK on that chain.
The beauty of it is that the market naturally balances the price of ELK across all chains, vs having to manually manage exit liquidity on all chains (like traditional bridges have to do). That's why $ELK is close to the same value across chains, because users can manually arbitrage it for more $ELK using ElkNet and other methods to convert the currency, accumulating more $ELK. Eventually, the plan is to be able to simply be able to swap, say, ETH on it's native chain for, let's say, AVAX on it's native chain, while in the background, behind the scenes the DEx trades ETH for $ELK at the best price on the ETH chain, ElkNet burns ELK on ETH, mints it on the AVAX chain, and swaps the ELK for AVAX at the best price. As we have more $ELK liquidity providers, this will lessen the price impact of even large trades. If there is impact, people will see the difference in price, selling ELK on one chain, and moving the value to the other in order to but more $ELK, which evens things out price wise.
It's also faster than any other bridge. We were seeing times between 7-20 seconds (the slower ones are simply slower because of the network's RPCs), and the gas required is not much. Right now that gas coming out of the ElkNet is completely covered by us, so you don't have to pay for it.
Another thing is that each transfer will permanently burn a very small amount of $ELK from all chains, to ensure sustainability.
Lastly, it is completely decentralized, as only Moose NFT holders can validate transfers across ElkNet (who will get a small amount of $ELK for each validation) only if they are holding a certain amount of $ELK