Liquidity provision, routed in one transaction.
BOTLend turns a single-asset deposit into a live BDEX V2 liquidity position through an automated, one-transaction route — with transparent fees and individually tracked positions.
A complete liquidity experience, built around BOT Chain.
BOTLend v2.0 focuses the user journey around live BDEX V2 liquidity: discover the pool, balance the deposit, supply liquidity and track the resulting LP position by wallet.
Automated routing
Pool discovery happens through the BDEX factory at transaction time, keeping the route aligned with live pool availability.
Individual accounting
LP balances are recorded against the user's address for the specific pool, giving every position clear on-chain accounting.
Transparent economics
A 0.3% deposit commission and 0.3% withdrawal commission are disclosed and routed automatically to the treasury.
Transaction-level execution
The deposit path combines the required routing actions into a single transaction for a streamlined user experience.
From one asset to a balanced LP position.
Every deposit() executes the complete route from start to finish in one transaction.
You deposit
Send either asset of a BDEX pair to the router.
0.3% to treasury
The fixed commission is taken immediately.
Swap half
Half of the remaining amount is swapped using a live BDEX quote.
Add liquidity
Both assets are supplied and LP tokens are received.
Credited to you
Your LP amount is recorded against your address for that pool.
Built for practical on-chain liquidity.
BOTLend provides a streamlined route into BDEX V2 liquidity for users who want a simple, automated way to create and manage individual liquidity positions.
Single-asset liquidity
Start with either asset of a supported BDEX V2 pair and let the router handle the balancing step.
Liquidity provisioning
Convert a deposit into a BDEX V2 LP position through an automated, transaction-level route.
Position management
Track liquidity positions by wallet address and pool, with the resulting LP amount recorded individually.
On-chain transparency
Protocol commissions and routing actions are designed to be visible and verifiable on-chain.
Simple fees. No hidden layers.
BOTLend uses a simple, transparent fee model with two protocol commissions. There are no management or performance fees.
Taken once before routing to the pool.
Taken per returned asset on withdrawal.
Designed to minimize unnecessary trust.
The whitepaper emphasizes a focused architecture built around individually tracked LP balances, automated pool discovery and transparent routing.
Each liquidity position is tracked by address and pool for clear ownership and accounting.
Deposit and withdrawal paths use a reentrancy guard and checks-effects-interactions ordering.
Swap and liquidity-add legs calculate minimum acceptable outputs from live BDEX reserves with a 2% tolerance band.
The BDEX factory is queried at transaction time rather than relying on a stale hardcoded pool list.
The protocol architecture is designed around clearly defined routing, position accounting and treasury mechanics.
Independent security review is part of the roadmap before mainnet launch.
Build the router. Verify it. Then expand the ecosystem.
Phase 1 · Foundation
Router contract built, flattened for Remix, compiled and prepared for BOTScan verification. In progress.
Phase 2 · Frontend & testnet
Liquidity-router dApp, wallet integration and full deposit/withdraw testing against live BDEX pools on BOT Chain testnet. Weeks 3–4.
Phase 3 · Audit & verification
Independent security review, slippage-guard stress testing and public BOTScan verification. Q2 2027.
Phase 4 · Mainnet launch
Deploy to BOT Chain mainnet and support any pair with a live BDEX pool, subject to the protocol's deployment readiness. Post-audit.
Phase 5 · Growth
Pool analytics, historical yield tracking per position and expanded token support as new BDEX pools go live. Post-launch.
Connect, explore, and manage your liquidity journey.
The interface uses live wallet/network information where available, while protocol metrics and position examples remain clearly presented as application demo data until the router contract is connected.