.png)
<aside> 💥 Building something cool on blast? Let’s make it secure together. Contact me at [email protected] or @NirlinSecurity on telegram
</aside>
Uncle Ben once said “With great power comes great responsibility”, but today Uncle Nirlin is going to teach you an even more interesting lesson.
”With each new great protocol, comes new integration bugs”
At least this has been the case with all big projects, integrations are hard, and if the codebases you are integrating with are complex it’s even harder. That’s why I said quite a few times, we need more integration-specific auditors, like Windhustler for layer zero and Stargate and jeiwan for uniswap.
So what could go wrong when integrating with blasts yield and points mechanism?
Well, there are quite a few things, let’s break them down one by one.
A small note for people who are living under the rock and don’t know what blast is
Blast only Ethereum L2 with native yield for ETH and stablecoins (for now just usdb → usd-blast)
Where does yield come from?
If you don’t know the source of yield, you are the yield. In the case of blast, it comes from staking the eth in LIdo and for USDB it comes from the makerDao T-bill protocol. You can read more about this here :
https://docs.blast.io/about-blast
For EOA accounts on blast, the yield is accrued automatically for weth and usdb, one may assume that is the case for the smart contracts too which is not.
Smart contract accounts have three Yield Modes for their rebasing mode: