@BabylonLabs_io
for something babylon calls trustless, the actual trust in this specific step comes down to one number i can't find anywhere — how long the challenge period actually runs for redemptions in the aave v4 tbv design. that window is what lets a bad claim get disputed before btc moves back on the bitcoin side, and right now it just isn't specified in anything babylon or aave has published.
context worth keeping in mind: aave apparently took around $190m in bad debt from an exploit in april 2025, at least going by the coverage i've seen, not something i've traced to a primary aave disclosure myself. that's likely part of why this whole native-btc redesign leans so hard on security language. a short challenge window keeps borrowing fast but leaves less time to catch a bad claim, a long one's safer but slows every redemption down, and neither pick is wrong on its own. this is still testnet, still temp-check stage, nothing's final. what would actually need to be published before i'd trust this redemption step with real btc? 🤔

#baby $BABY