Lombard vs Lido DAO — how do they compare? Lombard trades at Rp1,968 (market cap Rp673,08M, Rp98,49M 24h volume), while Lido DAO trades at Rp5,337 (market cap Rp4,49T, Rp394,49M 24h volume). The key difference: Lido DAO is far larger — about 6670.8× Lombard's market cap, and Lombard's supply is capped (343,1M / 1B BARD (35%)) while Lido DAO's keeps growing. Which is the better fit depends on your goals — on Pluang, investors hold Lombard for 10 Days and Lido DAO for 34 Days on average.
| BARD | LDO | |
|---|---|---|
Market Cap | Rp673,08M | Rp4,49T |
Volume (24h) | Rp98,49M | Rp394,49M |
Circulating Supply | 343,1M / 1B BARD (35%) | 836,3M LDO |
Typical Hold Time | 10 Days | 34 Days |
Signals from Pluang's Aura AI — not financial advice
No Aura AI signal available yet.
LDO is trading at Rp5,337 with a bearish technical bias, below key moving averages, though oscillators are neutral. The price sits between support at Rp5,181 and resistance at Rp5,374. On-chain hold time is 34 days, indicating moderate holding behavior. No major protocol upgrades or ecosystem news were reported recently.
Outlook remains cautious due to bearish momentum and lack of catalysts. Key opportunities include potential rebound from oversold RSI levels, while risks involve low liquidity and crypto market volatility. Investors should monitor Ethereum staking trends for fundamental cues.
What Pluang investors did over the last 30 days
Latest headlines on both assets
Lombard is developing on-chain Bitcoin capital markets to maximize Bitcoin's potential. Founded in 2024, it leads in DeFi with LBTC, the largest yield-bearing Bitcoin option. The company is building infrastructure for BTC adoption and is backed by top digital asset leaders.
Read more on BARD →Lido is a liquid staking solution for Ethereum that allows users to earn staking rewards without maintaining staking infrastructure. This native utility token can be used for granting governance rights in the Lido DAO, managing fee parameters and distribution, and also governing the addition and removal of Lido node operators.
Read more on LDO →