Design Philosophies

Replete has been developed based on several design philosophies, which can be distilled into six pillars. These pillars serve as guiding principles for protocol contributions and act as a crucial reference point when improving any aspect related to the protocol.

Design philosophies in practice

More chains, more volume

Replete Finance is designed to be available on a diverse range of markets (chains) for blue-chip assets, bolstering opportunities for blue-chip asset holders. Connecting more chains allows protocol stakeholders to participate in more markets. In turn, by integrating additional chains, liquidity providers get to benefit as the liquidity is available on a broader spectrum of the market.

Offering liquidity on one chain, yet earning from all.

Abstracting cross-chain complexity for regular users

The cross-chain functionality is seamlessly abstracted away for end-users. Abstracting the multi chain complexity for users, is necessary for a more streamlined interchain future.

Suppliers can effortlessly provide liquidity to any of the connected chains using the dApp on their preferred blockchain. Likewise, borrowers can supply collateral to any connected chain and borrow to any destination chain. Repayment occurs in a similar streamlined manner.

Concentrating liquidity, lower slippage

Rather than requiring deployment a pool on every chain, Replete maintains a unified pool where all liquidity is consolidated. This results in a level of depth that surpasses conventional cross-chain money market reducing slippage and attaining a higher efficiency rate benefitting all participants.

Concentrating collateral on a single chain provides more competitive rates for all stakeholders, benefitting stakeholders on every connected blockchain.

No stables

Replete is intentionally designed to not issue its own stablecoin. While these options have their merits, users benefit from borrowing assets with established use cases in DeFi, enhancing the viability of their strategies. It's about empowering users, not restricting them.

Last updated