Web3 R&D Laboratory
Build on-chain.
Without the noise.
Sullend Labs builds open-source developer tools, DeFi protocols, and DAO infrastructure for engineers who ship. No hype. No abstractions that leak. Just code that works.
What we build
Dev tools / SDK
A TypeScript SDK and CLI suite for building on EVM-compatible chains. Typed interfaces generated directly from contract ABIs, composable modules for common protocol patterns, and zero unexpected side effects. Built for protocol integrators and application developers who need reliable primitives, not magic.
DeFi protocols
Audited smart contracts for lending, liquidity provision, and yield strategies. Modular by design — deploy only what your use case requires. Each component exposes a minimal interface, carries a formal specification, and is tested against forked mainnet state before any release reaches a public testnet.
DAO infrastructure
On-chain governance contracts and treasury management tools for decentralized organizations. Proposal lifecycle, weighted voting with delegation, and timelock execution queues — each module independently deployable. Built for organizations that need governance to function as infrastructure, not optics.
Projects
Sullend SDK
TypeScript SDK for EVM protocol interaction — multicall batching, typed ABIs, provider-agnostic
CoreLend Protocol
Modular lending contracts for EVM chains — isolated pools, pluggable oracles, EIP-3156 flash loans
Govern
Lightweight DAO governance toolkit — token-weighted voting, timelock, treasury under 800 lines
Why we exist
Infrastructure that doesn't require a PhD to debug
Most web3 tooling is built for demos, not production. It works until a contract is upgraded, a dependency breaks, or an edge case appears at 2am on a Sunday. We built Sullend Labs to fix that.
Every project we ship follows three rules: the code must be readable by a competent engineer without consulting the author; every external dependency must be justified and auditable; the test suite must cover both the happy path and the conditions under which the protocol will be attacked.
We write everything in public and accept that scrutiny is a feature, not a threat. If something in our code is wrong, we want it found before it costs someone money.
Technical approach
Separation of concerns at the contract level
We do not couple business logic with state management. Pool state, interest rate calculation, oracle resolution, and liquidation logic each live in separate contracts with minimal interfaces between them. This makes the system easier to audit, easier to upgrade, and easier to reason about under failure conditions.
Types as documentation
The Sullend SDK generates TypeScript types directly from contract ABIs. There is no manual type maintenance — types are a build artifact, not a promise. When the contract changes, the types change. Your editor surfaces the discrepancy before you write a single line of integration code.
Forked mainnet testing, always
Unit tests cover logic. Forked mainnet tests cover reality. We run integration suites against forked mainnet state before every release to catch behavior that only emerges when your contracts interact with live DEX liquidity, real oracle feeds, and existing protocol state.
Audit before any financial contract ships
No CoreLend deployment will reach mainnet without a completed, published audit report. The report lives in the repository alongside the contracts. We do not ship financial infrastructure on a timeline that requires skipping this step.
We build open-source infrastructure for web3 teams who don't have time for abstractions that leak.