Comment on page
All your common questions answered here.
The smart contracts are running decentralized, while the backend is centralized.
Why? Native is working with many market makers who provide quotes off-chain. The amount of data processing to process all these quotes cannot be done on the blockchain in a fast enough manner. At the same time, it would cost hundreds of dollars per swap computation from a gas-fee perspective.
Will it change? We would love to decentralize our infrastructure if the future allows it. We know that some projects are working on this, and we're watching them closely. Around that, we also need a proper dev-ops ecosystem that allows us to keep such an infrastructure up and running and maintain it while keeping it fast and secure for the user.
Liquidity is siloed across chains, and your users might come from everywhere.
Presently, your users need to use external bridges, sending them away from your dApps, creating friction, reducing your conversion rates, and increasing the communication overhead.
Alternatively, you could implement one or more bridges by yourself. But this comes with a lot of drawbacks:
- 1.One bridge is not enough. There is no one bridge that supports all chains. One bridge is also susceptible to being hacked or not having sufficient liquidity. In all of these cases, you need to have a fallback solution.
- 2.Bridges are still immature and will change going forwards, which creates unnecessary dependency and maintenance overhead.
- 3.Implementing a bridge is not enough; you also need them to connect to DEX aggregators and DEXs to have a real benefit. Many bridges are just focused on stablecoins and native currencies.
- 4.The cost and resources to build your own bridge is often beyond the capabilities of a typical project. We all have limited resources and should focus on our own strengths, especially when there is an existing solution like Native.
RFQ in crypto stands for "Request For Quote." It is a trading mechanism that allows buyers and sellers to privately negotiate trades off-exchange. In an RFQ system, a buyer will send a request for the price of a specific asset or quantity to a seller. The seller then responds with a quote for the requested asset or quantity.
RFQ systems can be found on various platforms, including decentralized exchanges (DEXs) and centralized exchanges (CEXs). They are particularly useful for large trades, where the size of the order may not be easily filled on the open market without significantly affecting the price.
Overall, RFQ systems provide a flexible and efficient way for traders to negotiate trades privately and find the best price for a given asset or quantity.
Native has a swap widget SDK that is compatible with popular UI frameworks such as React, VueJs, and VanillaJs. You can customize this widget depending on your needs. For more details, you can refer to Swap Widget section.
Chameleons change colors to blend in with their environment. They adapt to stay out of sight. Native wants to be the invisible liquidity layer that powers crypto. As an infrastructure protocol at the base level, the best user experience for us is that users do not even notice we are there and everything just magically works.