Case studiesDecentralized lending

Chedda Finance: lending protocol and dApp delivery

Chedda Finance brought cross-chain lending contracts, position-risk services and a dApp interface into one product. Ego Eimi’s delivery covered the protocol and the application people used to interact with it.

Business
Chedda Finance
Sector
Decentralized lending
Scope
Smart contracts, risk services and dApp
Contributor
Ego Eimi
Editorial illustration: metal chain links bridging dark piers with one orange link
AI-generated editorial illustration of the project’s domain.

The interface and collateral rules needed to describe the same position.

A lending application spans more than its transaction screen. Deposits, borrowing, collateral and liquidation logic live in the protocol, while the user needs a clear representation of the resulting position. Cross-chain operation adds dependencies between networks and services.

The engineering task was to connect those layers. A position shown in the interface needed to correspond to the contract state and the information used by the risk service.

Build the contracts, risk services and dApp together.

The project combined Solidity smart contracts, a risk-scoring engine and a Next.js dApp. The contract layer handled deposit, borrow and liquidation logic; the application connected those actions to the front end.

Foundry and Hardhat supported contract development, with ethers.js connecting the application to the contracts. The stack also included The Graph and Python for the surrounding data and risk services.

What the workflow includes

  • Implement lending and collateral logic in Solidity.
  • Connect position-risk information to the application.
  • Expose protocol actions through a dApp interface.
  • Deliver the contracts and application stack together.

A connected lending application and its underlying protocol.

The client received the protocol and dApp as a connected stack. Its delivery scope included contract logic, the risk service and the interface, making the relationships between those components part of the product handover.

What this means for the technology owner.

A protocol owner needs a record of deployed contracts, administrative authority, data dependencies and changes to risk logic. Application ownership and financial risk are separate responsibilities; both need explicit boundaries when a team takes over the system.

The technology ownership checklist →

SolidityFoundryHardhatethers.jsNext.jsTypeScriptThe GraphPython

Project contribution: Ego Eimi. The scope described above identifies the work behind this case.

Editorial review: Ego Eimi · Updated September 6, 2026 · About the team

Related case studies

Editorial illustration: a small metal vault with an orange ingot and three key components
Bitcoin-backed lending

BTC Backed

Backend, wallet and multisignature escrow

Read the case →
Editorial illustration: a coordinated mechanical timing assembly with one orange arm
Trading software

Crypto Trading Platform

Market data and concurrent execution

Read the case →
All case studies46 projects

Your technology

Start with the business

Your business depends on it.

Tell us which system matters, what has changed and who controls it. We will define a reviewable next step. Read Foundation and the commitments and evidence.

Start a conversation More case studies