Comment on page
Atomic Swap as a Service
Also known as "bridging", this service allows you to easily create an atomic swap bridge across multiple blockchains. For example, you could bridge your ERC-20 with a BEP-20 token.
All OKLG-supported blockchains
For our atomic swap/bridging as a service dApp, once you have token contracts deployed on the networks you want to bridge between, you can setup a bridge within a matter of 10-15 minutes in our interface.
Note that our bridge service requires you to deposit tokens to each bridge contract to serve as bridge liquidity. You can deposit however many tokens you would like, but we recommend somewhere between 5-20% of supply in order to accommodate large migrations from one chain to another (i.e. if arb opportunities are large temporarily, etc.). If you anticipate a large movement from one chain to another on initial bridge deployment, it makes sense to deposit more tokens on the side of the bridge you believe users will go to which will eventually even out the bridge supplies on each side.
- Creating a new bridge: $5,000 USD per bridge created ($2,500 USD on each chain)
- Choose one of two paths from here for remaining costs:
- 1.Option 1 (DEFAULT): Users pay for swapping tokens across bridge: $10 USD per swap executed
- 2.Option 2: Project pays monthly service fee
- If you as the project owner(s) do not want users to need to pay $10 in order to bridge their tokens you can pay a service fee instead and we can remove this fee for users.
- $1,200 USD/month paid monthly
- $1,000 USD/month paid annually
An important note to start is you need project tokens to supply the bridge on both chains. We have been made aware of competitive solutions that utilize LP on both chains to handle supplying and swapping tokens on their bridge, but our solution does not need/care about LP and simply takes an initial supply you send the bridge that is used to send/receive token to users.
TODO
- 1.Make sure you're logged into the network where your tokens currently reside. Click the Initiate Swap button on the bridge you would like to use and select a number of tokens you would like to bridge across.
- 2.After clicking the button to begin a swap, you will go through a couple of transactions to approve the bridge to send your tokens, and finally to send your tokens to the bridge.
- 3.After your tokens have been sent to the bridge. You will be presented a swap ID, unique identifier, and amount that you should write down in the event you need them later. Normally this is not needed, but it's a good idea to write them down just in case.
- 4.Switch to the target network where you would like to claim your bridged tokens. Once switching, the bridge cards will update on the interface and you should see a red message in the bridge where you just started a swap.
- 5.Click the Claim Tokens button to begin claiming your tokens from the bridge.
- 6.You will execute a blockchain transaction that will initiate claiming your tokens. Note that depending on the network(s) your bridge uses, this step of claiming could take a number of seconds to a number of minutes to complete. Feel free if after several minutes of waiting to receive your tokens to initiate claiming again, as it's possible for a transaction to get stuck or be slow to complete due to congestion or gas variability.
The primary thing to consider when launching on another chain is you will deploy another token contract that our atomic swap service will effectively link between and support your users to swap tokens 1:1 between chains. You are responsible for calculating and ensuring circulating supply between chains does not exceed the expected total supply that your community expects. If you have 60% tokens circulating on chain A and you want to launch on chain B, it’s likely you should ensure you don’t exceed 40% of supply circulating on chain B if/when you provide liquidity on any DEXs. Note that the bridge supply you provide doesn’t NOT count as circulating, as tokens there will only ever be swapped 1:1 with circulating tokens
Similar to how FLOKI, CELL, ZINU, and others all have their own white labeled bridge pages, we have a partner we go through (the same guy who created our website and who will be helping us with a redesign of our platform this quarter) to build these.
$6,000 USD for a two-chain bridge, $10,000 USD for three-chain setup for all design and web3 hook up to bridge
- 1.Q: I am trying to bridge my tokens, and when claiming my tokens on the target chain I receive a very large estimate of gas to complete the transaction. What is happening? A: When a web3 wallet (i.e. Metamask) tries to estimate the gas for a transaction to quote you and cannot due to a contract error or otherwise, it will show a big red error message communicating "the transaction is expected to fail" and quote you an exorbitant gas fee. This fee is not the actual amount of gas it will take to complete the transaction, but simply a placeholder the wallet uses until it can properly estimate the transaction. If you experience this, it means 1 of 3 things are happening: 1. You don't have enough native token (ETH on Ethereum, BNB on BSC, MATIC on Polygon, etc.) for your wallet to estimate gas for the transaction, and it errors out. To resolve, add more native token to your wallet. 2. You're using a different wallet to claim than you sent tokens to the bridge on the other chain. To resolve, you must use the same wallet to claim your tokens than you used to send your tokens to the bridge.3. You have the incorrect swap info plugged in to the claim form. To resolve, confirm the info is correct that was provided to you when bridging in the claim form.
Last modified 1yr ago