Concrete Finance
Engineering DeFi products around wallet identity, smart contracts, and financial workflows.
The product
Concrete is a decentralized finance platform built around on-chain yield vaults. Users deposit supported assets and receive vault shares representing their portion of a vault, giving them access to yield strategies through one interface. The value of those shares changes with the underlying assets and strategy performance.
Concrete’s documented vault model follows ERC-4626, a standard for tokenized vaults. The protocol handles strategy allocation, accounting, and withdrawal operations behind the interface.
My engagement
I worked across Concrete Earn and Concrete Borrow, with different responsibilities on each product. For Earn, I was the sole frontend engineer, developing the complete application experience in React, Next.js, and TypeScript. My scope covered wallet connection and authentication, vault operations, deposits, withdrawals, rewards, balances, and portfolio experiences.
The work involved direct smart-contract integration alongside supporting APIs. I connected financial data and wallet authorization to the interface so users could review a position, authorize an operation, and follow its result within the application.
On Borrow, I worked alongside another engineer, contributing to multi-network vault management, liquidation protection, APY visibility, and reusable SDK integrations. This combined full application responsibility on Earn with focused contributions within Borrow’s shared implementation.
// engineering work
- Building Concrete Earn
I built the Earn client from wallet connection and authentication through vault transactions, rewards, balances, and portfolio management. The application connected the information users needed to assess a vault with the operations needed to deposit, withdraw, and review their holdings.
- Wallets and smart-contract interactions
I integrated on-chain reads, wallet signing, and transaction execution directly with smart contracts and supporting APIs. The client had to connect financial operations to understandable actions: reading a position supplied information, while changing it required a user-authorized transaction. My work joined those different interactions into the vault workflow.
- Concrete Borrow and reusable integrations
Alongside another engineer, I contributed to multi-network vault management, liquidation protection features, and APY visibility. I also developed reusable SDK modules for partner integrations, extending those capabilities beyond a single application surface.
Delivery and reflection
My work delivered the Earn client experience and targeted contributions to Borrow. The engagement reinforced the importance of making financial information and transaction authorization understandable together, with clear boundaries between what the client displayed and what users signed.