[DISCUSSION] PeerLend – Oracle-Free, ICS-Secured Lending Protocol with Rescue Market

Introduction Despite its robust infrastructure, Cosmos Hub still lacks a sustainable DeFi credit layer. While Osmosis has succeeded as a DEX, Cosmos lacks a permissionless lending primitive that could anchor long-term liquidity and generate economic activity for the Hub. PeerLend is a protocol design that proposes a simple, transparent, and oracle-free lending mechanism tailored to Cosmos. A system where users set their own interest rates, loans accrue interest over time, and risky positions are resolved via an open “rescue market” — all without relying on price oracles. PeerLend is not currently under development. This post is intended to share the idea openly and invite feedback from the Cosmos community. How PeerLend Works • Lending Offers with Custom Interest Rates Lenders submit offers by specifying how much they’d like to lend and at what annual interest rate. Borrowers can browse offers and select the one that suits them. Example: Alex wants to lend 5,000 stATOM at 4% annual interest. Taylor chooses to borrow from Alex under those terms. Both the collateral and borrowed asset must be of the same token type. Cross-asset borrowing (e.g., ATOM → USDC) is…

Excerpt (1196 of 4640 characters). Read the whole post on the forum ↗

Thank you for submitting this idea — we appreciate the initiative and would like to offer a few points of constructive feedback. First, you’re absolutely right in noting that while lending markets do exist within the broader Cosmos ecosystem, none are currently operating in direct integration with the Cosmos Hub itself. This absence may reflect the reality that the Hub—under the InterChain Security model (ICS)—has struggled to attract strong market-fit demand for such consumer chain services. Second, it’s important to consider the current trajectory of the Cosmos Hub. With the recent strategic shifts at the ICF, the Hub is now undergoing a significant transformation into a service chain architecture. A central piece of this evolution is the upcoming deployment of an EVM execution module , which is expected to unlock new utility for builders and developers. Given this context, we strongly encourage you to explore the possibility of deploying your protocol directly on the Cosmos Hub via this EVM module, rather than pursuing a standalone consumer chain. This approach could bring more visibility, composability, and alignment with the Hub’s evolving priorities. Thanks…

Excerpt (1195 of 1292 characters). Read the whole post on the forum ↗

Thank you so much for the thoughtful feedback!

This was more of a conceptual contribution than a formal proposal — but I’m really encouraged to see the interest and strategic insight.

Should the project move forward, I’ll definitely revisit deployment options in light of the EVM module direction. Appreciate the input!