▫️Routers

Routers - WebGlide

The WebGlide network's active liquidity providers and nodes are routers.

How do routers work?

Before becoming active in the network, routers provide liquidity on each chain and for each asset they want to support. This liquidity is denominated in nextAssets - a WebGlide-specific unit-of-account that acts as an IOU of locked funds on Binance L1.
Routers observe all chains in the network. For WebGcalls involving their supported chains & assets, routers simulate the transaction on destination, create a bid (a signed transaction that executes the destination chain interaction), and submit that bid to the WebGlide sequencer .
The sequencer waits a fixed period of time to collect bids from routers and then randomly selects from among them. For every batch of transactions, the sequencer will send a corresponding batch of winning bids to a relayer network (e.g. Gelato) to submit the transaction to the destination chain.
For router transactions that are submitted by the sequencer immediately (see fast path), the router effectively fronts the transaction funds and calldata on the destination, being repaid by the protocol after the slow path completes if they submitted the transaction with the parameters provided in the origin chain WebGall.

Risks

In general, routers are intended to be as safe and passive for operators as feasible. There are a few concerns to be aware of, though:

Hot wallet: Routers are effectively a "hot wallet" of funds owned by the router operator that can unilaterally spend owned funds in the protocol. This means that proper key management practices are a must for routers that want to operate in production.
Misconfigured environments: Router operators should also ensure that they are careful to not expose the router's private API as part of setting up their environment.
Protocol security: As with any protocol, router operators are ultimately exposed to the risk of WebGlide's underlying implementation. While this risk is never 0, WebGlide follows best practices for auditing, security bounties, and operational practices to keep routers safe.

Business Model

The router’s primary business model is to earn transaction fees for providing liquidity and relaying data across chains.

Routers earn a fee of 5 basis points (0.05%) on all liquidity that is provided for a user transaction. Router liquidity is then subsequently locked up until it can be claimed against the slow path. In effect, this is asa if the router is giving a protocol-level loan to the user for a period of up to 2 hours. In this model, router ROI scales with user demand - routers earn the highest returns if a high percentage of their capital is frequently locked up.

Routers currently do not take a fee for relaying data itself. There are future plans to implement an EIP-1559-style tip, that can supplement router income for data-only transactions.

PreviousWebG Governance NextLegal disclaimer

Last updated 1 year ago

How do routers work?

Before becoming active in the network, routers provide liquidity on each chain and for each asset they want to support. This liquidity is denominated in nextAssets - a WebGlide-specific unit-of-account that acts as an IOU of locked funds on Binance L1.

Routers observe all chains in the network. For WebGcalls involving their supported chains & assets, routers simulate the transaction on destination, create a bid (a signed transaction that executes the destination chain interaction), and submit that bid to the WebGlide sequencer .

The sequencer waits a fixed period of time to collect bids from routers and then randomly selects from among them. For every batch of transactions, the sequencer will send a corresponding batch of winning bids to a relayer network (e.g. Gelato) to submit the transaction to the destination chain.

For router transactions that are submitted by the sequencer immediately (see fast path), the router effectively fronts the transaction funds and calldata on the destination, being repaid by the protocol after the slow path completes if they submitted the transaction with the parameters provided in the origin chain WebGall.

Risks

In general, routers are intended to be as safe and passive for operators as feasible. There are a few concerns to be aware of, though:

Hot wallet: Routers are effectively a "hot wallet" of funds owned by the router operator that can unilaterally spend owned funds in the protocol. This means that proper key management practices are a must for routers that want to operate in production.

Misconfigured environments: Router operators should also ensure that they are careful to not expose the router's private API as part of setting up their environment.

Protocol security: As with any protocol, router operators are ultimately exposed to the risk of WebGlide's underlying implementation. While this risk is never 0, WebGlide follows best practices for auditing, security bounties, and operational practices to keep routers safe.

Business Model

The router’s primary business model is to earn transaction fees for providing liquidity and relaying data across chains.

Routers currently do not take a fee for relaying data itself. There are future plans to implement an EIP-1559-style tip, that can supplement router income for data-only transactions.