Integration with NFTfi

You're building a landing platform or NFT marketplace, and users request the ability to take out a loan against an NFT with a fixed term and fixed rate. Without liquidation oracles or AMM — only peer-to-peer. NFTfi is one of the oldest protocols, audited and with extensive documentation. However, integration requires correct handling of EIP-712 offers, state monitoring, and race conditions. We implement full integration: from offer signing to loan monitoring via subgraph.

The core of the protocol consists of two key contracts: NftfiHub (registry and router) and DirectLoanFixedOffer (fixed-rate loans). Since v2.1, DirectLoanFixedOfferRedeploy with ERC-1155 support has been added. The typical flow: the borrower locks an NFT, receives ETH or USDC, and if not repaid, the NFT transfers to the lender. No liquidation oracles — only clean fixed-term loan.

How the NFTfi protocol works

1. Borrower calls approve for the NFT to the NFTfi address, then accepts an offer via acceptOffer.
2. Lender creates a signed off-chain offer (EIP-712) stored in NFTfi's database or your backend.
3. Upon acceptOffer, the contract transfers the NFT to itself, sends tokens to the borrower, and mints a promissory note NFT (ERC-721) to the lender.
4. At expiry: payBackLoan from the borrower or liquidateOverdueLoan from the lender.

What is the offer structure (EIP-712)?

Integration via offer signing is where most errors occur. The offer contains:

struct Offer {
    uint256 loanPrincipalAmount;
    uint256 maximumRepaymentAmount;
    uint256 nftCollateralId;
    address nftCollateralContract;
    uint32 loanDuration;     // in seconds
    uint16 loanAdminFeeInBasisPoints;
    address loanERC20Denomination;
    address referrer;
}

The signature is created via signTypedData in ethers.js or viem, using the NFTfi contract's domain separator. The domain separator includes the chainId — an offer for Ethereum mainnet is invalid on Goerli, even if the contract address matches. See EIP-712 for details.

Common mistake: mishandling intermediate loan states

A loan can be in states: Active, Repaid, Liquidated, or in an edge case — when the block with payBackLoan is mined after loanDuration expires but before liquidateOverdueLoan is called. The contract accepts both calls in a short window (usually 2–5 blocks, 30–60 seconds on Ethereum, 4–10 seconds on Polygon). If the frontend does not update the status atomically, a user may see an active loan that has already been liquidated.

Recommended approach: listen to LoanStarted, LoanRepaid, LoanLiquidated events via ethers.js provider.on or a The Graph subgraph. The subgraph is preferable for UI — it allows complex queries (all active loans for a collection, loan history for an address). On-chain events give near-zero latency but require manual filtering. The subgraph delays up to 30 seconds but queries are 10x simpler for analytics.

Why choose NFTfi for P2P lending?

NFTfi is one of the oldest protocols in this niche with audited smart contracts and extensive documentation. Off-chain offers reduce gas costs for the lender (no transaction needed to create). Supported currencies include ETH, USDC, DAI, and other approved ERC-20 tokens. Using the @nftfi/js SDK accelerates development — the SDK is 2x faster to implement than raw ABI integration. The average acceptOffer transaction on Ethereum costs about $50 in gas; on Polygon, under $1. Our integration packages start at $3,000. We guarantee quality integration with audited contracts and extensive experience. Our team has completed over 15 projects with NFTfi. Order NFTfi integration for your project — get a consultation tailored to your case.

What is included in the integration

• SDK/library: Official @nftfi/js for fast integration or direct ABI work for full gas estimation control.
• Subgraph queries: GraphQL for active offers, loan history, collection data. Integrated via @apollo/client or urql.
• Loan currencies: ETH, USDC, DAI, and other approved ERC-20s. Requires approve logic for each currency from the lender before offer creation.
• Referral system: Support for referrer address in offers — a way to monetize the integration.

Our NFTfi integration includes peer-to-peer lending with fixed-term loans, utilizing EIP-712 offers and smart contracts.

Deliverables

• Full documentation of integration (API, events, subgraph queries).
• Access to subgraph endpoints and dashboard.
• Training for your team on offer signing and monitoring.
• 1 month of post-launch support and bug fixes.

Process

1. Study ABI and test on testnet (1 day). Deploy a test NFT, manually create a loan via contract, verify all events.
2. Backend integration (1–2 days). Store and relay offers, webhooks for loan events.
3. Frontend components (1–2 days). Offer creation form, active loans display, repayment flow.

Timeline estimates

Basic integration — creating and accepting offers, loan monitoring — 3–5 days. Full lending UI with collection analytics and automated offer creation — 1–1.5 weeks. Contact us to discuss details — we will tailor an optimal plan.

DeFi Protocol Development

We design modular DeFi protocols where the math of stablecoins, liquidity, and oracles works flawlessly. Mango Markets is a stress test: the attacker manipulated the spot price through a single account, took a loan against inflated collateral, and withdrew $114 million. The oracle took the price from a single source without TWAP. Not a code bug—it was an architectural decision that became a vulnerability. Our experience shows: any DeFi protocol is a system of bets that all components, from calculations to economic incentives, are correctly aligned simultaneously.

We don't write code under the 'if it works, don't touch it' mindset. We model stress scenarios: cascading liquidations, depegs, flash loans. Only then do we build events that won't break the protocol.

Why are oracles a critical component of DeFi?

Most major DeFi hacks started with oracle manipulation. Let's break down the three layers we use in every project.

Spot price as oracle—not an option. Uniswap v2 spot price can be shifted by a flash loan in one transaction. The price at the end of the block is the only one that enters the state, and the oracle reads it. Attack scheme: borrow via flash loan → buy asset into the pool → price rises → take a loan against inflated collateral → sell asset → repay flash loan. One transaction.

TWAP as protection. Uniswap v3 observe() averages the price over a period (30 minutes). Manipulation requires maintaining the price for several blocks—this is expensive. But TWAP reacts slowly to legitimate changes, opening a window for arbitrage on liquidation during sharp movements.

Chainlink Price Feeds are an aggregation from multiple data providers with a median. Standard for lending. Problem: heartbeat 1–24 hours and deviation threshold 0.5%. If the price doesn't move, the feed may not update for a day. In volatile markets—lag.

In production, we use a two-tier check: Chainlink aggregator + Uniswap v3 TWAP as a verifier. If the discrepancy exceeds N%, the transaction is rejected and the system is paused.

How to protect a DeFi protocol from flash loan attacks?

Flash loans turn any user into an owner of unlimited capital for one transaction. Therefore, when designing contracts, we assume: everyone has access to unlimited capital. This completely changes the threat model.

Legitimate uses of flash loans are arbitrage, liquidation, and self-liquidation. But the protocol must verify that the loan is not used for manipulation: the oracle must not read the price from a pool that can be shifted in one transaction. We add checks on block.timestamp and minimum liquidity depth.

Key Components of DeFi Architecture

AMM: From x*y=k to Concentrated Liquidity

Uniswap v2 uses x * y = k. LP tokens are ERC-20—each pool issues its own token proportional to the share. Problem: liquidity is spread across the entire curve, most of it unused.

Uniswap v3 and ERC-721 positions: concentrated liquidity—LPs provide liquidity in a range [priceLow, priceHigh]. Capital efficiency up to 4000x for stable pairs. But ERC-721 breaks vault strategies built for ERC-20. Range management is a separate engineering challenge: a position falls out of range when the price moves, stops earning fees, and becomes single-asset. Protocols like Arrakis Finance automatically rebalance. If you build a vault on top of v3, you need your own range manager or integration with an existing one.

Slippage in v3 is calculated via sqrtPriceX96—96-bit fixed-point math. Errors on the frontend lead to discrepancies between visible and actual slippage.

Curve for pairs with close prices (stablecoin/stablecoin, stETH/ETH) uses an invariant combining constant product and constant sum. Lower slippage within the peg range. Contracts are in Vyper, code is mathematically dense, auditing is difficult.

Lending Protocols: Collateral, Liquidation, Bad Debt

LTV defines the maximum loan against collateral. Liquidation threshold is the level for liquidation. The difference is the buffer for the liquidator. Typical example: LTV 75%, liquidation threshold 80%, bonus 5%. If the price drops 20%+, the position is open for liquidation.

Cascading liquidations: many positions are liquidated simultaneously → liquidators sell collateral → price drops → next wave. LUNA/UST 2022 is a classic cascade.

If collateral devalues faster than liquidation, the protocol incurs bad debt. Aave uses a Safety Module (staked AAVE), Compound uses reserves. Without a backstop, bad debt is socialized via dilution of the supply token or netting.

Designing a liquidation system requires modeling stress scenarios: a single liquidation bot failure, high gas, collateral delisting.

Yield Farming and Incentive Mechanics

Liquidity mining distributes governance tokens to LP providers. Problem: mercenary capital—farmers come, sell tokens, leave. TVL is illusory.

Sustainable mechanics: protocol-owned liquidity (Olympus bonding), veToken (CRV locked → boost + governance), locked staking with penalty. The ve-model, if implemented incorrectly, creates governance concentration. A timelock on gauge weight changes and limits on voting power are needed.

What Our DeFi Protocol Development Includes

• Architectural documentation: contract interaction diagrams, liquidation stress tests, oracle calculations.
• Implementation in Solidity 0.8.x with OpenZeppelin 5.x (AccessControl, ReentrancyGuard, Pausable, TimelockController) and Solmate for gas-optimized base contracts.
• Foundry fork tests on real mainnet (Uniswap, Chainlink, Aave) — pre-deployment tests cover all scenarios.
• Audit: at least two independent auditors for TVL over $1M. Code4rena or Sherlock for bug bounty.
• Deployment with Gnosis Safe 3/5 multisig + timelock 48–72 hours.
• Monitoring via Tenderly (alerts, simulations), OpenZeppelin Defender (automation), Forta (on-chain threat detection).
• Post-launch support: updates, patches, upgrades via proxy.

Our Expertise and Experience

We have been developing DeFi protocols since 2020, delivering 30+ projects with a combined TVL of over $150 million. Our clients include protocols in the top 20 by TVL on Ethereum, Arbitrum, and Base. The team consists of certified Solidity developers who have completed ConsenSys Diligence audit tracks.

DeFi basic principles that we apply in practice.

Timelines

• DEX with AMM (Uniswap v2 fork): 6–10 weeks
• Lending protocol (Aave-style, single collateral): 3–5 months
• Yield aggregator with multiple strategies: 2–4 months
• Full-fledged DeFi protocol with governance: 5–8 months including audit

Cost is calculated individually—contact us for a project estimate.

Get a consultation on DeFi protocol architecture—we will analyze the risks and propose an optimal solution.