Integrating the Router suite just became a more bespoke affair

Router Protocol
3 min readOct 6, 2022

--

With configurable fee tokens, enterprises can now tailor their UI/UX further

A few months ago we abstracted our flagship dApp “Voyager” built on Router Protocol’s modular cross-chain infra. This abstraction was executed in three classes namely; Widget, JS SDK, and API. These offerings allowed Web 3.0 devs to integrate Voyager on their dApps and provide their users the ability to conduct cross-chain swaps and transfers on their interface without worrying about a technical overhead.

With a simple low code integration, Web 3.0 projects got the ability to acquire users whose native network differed from their native chain.

It is no secret that the ability to integrate Voyager both as a widget and as a white labelled solution is beyond the scope of functionalities provided by any other cross-chain bridge in the market.

However, we decided to go a step further.

With our Widget and SDK/API, Web 3.0 devs don’t just get the ability to integrate cross-chain bridges on their application, they can also control allowed transactions on the bridge. Up until now we offered the scope of following modifications to the default setting of Voyager. Developers can:

  • Set up the default chains and tokens to be shown to the user when the bridge is opened.
  • Restrict chains on the source and/or destination side. When you control the flow of liquidity on your dApp, the scope for augmenting the relationship with a prominent blockchain network also increases.
  • Restrict tokens that are shown on the source and destination chains.

These unparalleled functionalities have paved the way for multiple partnerships with prominent Web 3.0 projects. And now we are glad to announce that we are adding the scope to customize the user experience of Widget and SDK/API even more.

Notwithstanding the existing customizations, Web 3.0 Devs and dApp owners can now also set a default fee token for transactions. Currently, users can opt to pay the fees from 4 tokens namely: $USDC, $ETH, $DFYN, and $ROUTE. If you integrate any of the three abstractions of Voyager on your platform, you can now limit these four fee options to only one.

4 Fee Tokens
1 Fee Token

If you want a fully customizable integration of a cross-chain bridge on your dApp, then feel free to set up a call with our partnerships manager to know the next steps: https://calendly.com/router-partnerships/router-partnerships-call

About Router Protocol

Router Protocol is building a suite of cross-chain infra primitives that aims to enable blockchain interoperability between current and emerging Layer 1 and Layer 2 blockchains.

Website: https://routerprotocol.com/

Mainnet: https://app.thevoyager.io/

Documentation: https://docs.routerprotocol.com/

Twitter: https://twitter.com/routerprotocol

Telegram: https://t.me/routerprotocol

Telegram Announcements: https://t.me/router_ann

Discord: https://discord.gg/yjM2fUUHvN

--

--

Router Protocol
Router Protocol

Written by Router Protocol

Router Protocol is a secure, composable, and modular framework for building interoperable applications. More at https://routerprotocol.com

No responses yet