10 chains, one interface. Binance has taken over the most tedious part of integrating DeFi.
On October 16, Binance Wallet launched its DeFi API, initially supporting 10 EVM chains. The docs specifically name BSC, Ethereum, Base, Arbitrum One, Polygon, and others. Solana is said to be coming soon, but no date was given.
It does two things. For position queries, provide an address to get holdings on Aave, Morpho, Venus, and other protocols, broken down by address, protocol, and pool. For transaction building—deposits, withdrawals, adding liquidity, and claiming rewards—it only assembles the unsigned transaction. Signing and broadcasting are handled by the connected wallet. Binance never holds the private keys.
There’s one integration detail to watch. More protocols support position queries than transaction building; those extra protocols are marked as display-only, and their investmentIds may be empty. An app being able to show your positions doesn’t mean it can build the corresponding transactions for you. The official list of supported items must be checked at runtime. Copy the allowlist from the docs and it’ll be out of date before long.
The protocols that initially support transaction building include Aave, Morpho, Venus, Spark, Fluid, and Lido for lending and yield, and Uniswap, PancakeSwap, and QuickSwap for DEXs. Five of the transaction-building endpoints support a simulate parameter, which provides balance changes, gas estimates, and health factor changes before signing. Redemptions also include redeemDelayDays, so users can see how long they’ll have to wait for their funds.
What Binance is taking over is distribution. In the past, building a DeFi entry point meant negotiating with each protocol one by one. Now, you can fill in a single API, use the ready-made list, and bring Binance’s pools and assets into other apps.
Wallet developers no longer need to maintain a team for integrating protocols. Binance becomes the invisible plumbing layer inside someone else’s app.
#中本聪国际社区Baoluo币商资本 #币安推出BinanceIntelligence #BinanceWallet
On October 16, Binance Wallet launched its DeFi API, initially supporting 10 EVM chains. The docs specifically name BSC, Ethereum, Base, Arbitrum One, Polygon, and others. Solana is said to be coming soon, but no date was given.
It does two things. For position queries, provide an address to get holdings on Aave, Morpho, Venus, and other protocols, broken down by address, protocol, and pool. For transaction building—deposits, withdrawals, adding liquidity, and claiming rewards—it only assembles the unsigned transaction. Signing and broadcasting are handled by the connected wallet. Binance never holds the private keys.
There’s one integration detail to watch. More protocols support position queries than transaction building; those extra protocols are marked as display-only, and their investmentIds may be empty. An app being able to show your positions doesn’t mean it can build the corresponding transactions for you. The official list of supported items must be checked at runtime. Copy the allowlist from the docs and it’ll be out of date before long.
The protocols that initially support transaction building include Aave, Morpho, Venus, Spark, Fluid, and Lido for lending and yield, and Uniswap, PancakeSwap, and QuickSwap for DEXs. Five of the transaction-building endpoints support a simulate parameter, which provides balance changes, gas estimates, and health factor changes before signing. Redemptions also include redeemDelayDays, so users can see how long they’ll have to wait for their funds.
What Binance is taking over is distribution. In the past, building a DeFi entry point meant negotiating with each protocol one by one. Now, you can fill in a single API, use the ready-made list, and bring Binance’s pools and assets into other apps.
Wallet developers no longer need to maintain a team for integrating protocols. Binance becomes the invisible plumbing layer inside someone else’s app.
#中本聪国际社区Baoluo币商资本 #币安推出BinanceIntelligence #BinanceWallet