jstash

@0xInuarashi @notchefbob I think the bid count did increase correctly, the problem is that it should be checking against bidIndex rather than bidAmount in the claim... bidIndex is not a good name for what the variable is..

@notchefbob 20/ A summary Exploit 1: processRefunds() able to get stuck Exploit 2: bids count did not increment correctly with mint amount Exploit 3: withdraw requires bids count to increment correctly Final Caveat: funds stuck forever.

etherscan.io/address/0xf42c… 34 Million USD gone. Just like that. Locked in the contract forever. A lot of people put light on the grieving which locked processRefunds() for a bit, that was the first exploit. Luckily that was unlocked, but funds are still locked forever. How? 🧵 1/

@loldefi Too real 😢

Don't forget your capital gains tax is due before the end of the month, hentaikittenpapi69

@flashfish0x Great website 😉

There are only really a handful of exploits that happen in defi and this is one of them. Same concept as the Pickle exploit, same as the Rari one. And the same concept as the answer to challenge #3 on damnvulnerabledefi.xyz You can't trust any contract the user passes to you.

@loldefi 🤮

What the fuck is a Britcoin

@youngape11 No problem! Sorry for ruining your dopamine receptors 😆

@tom0pearson love the yearnings app. Have been waiting for something like this for a while.

@pastienot @cryptouf There is no direct api for this atm - working on adding it to the sdk. It just reads data directly from the graph. crvLINK v2 is working for me. Quit the app and reopen?

@cryptouf Not sure it is a direct API as no v2 crvLINK showing @tom0pearson

If you are using yVaults from @iearnfinance you should look at the app developed by @tom0pearson You can: 💠track multplie addresses 💠view historical earnings over the last month 💠 view aggregate apy and estimated earnings per day in $ 💠 only v2 vaults are supported