A few days ago, @samczsun pointed out that @indexcoop's Rari pool 19 was being attacked. While this was indeed an attempted oracle manipulation, the attacker ended up failing miserably and lost 68 ETH.
Here's a breakdown of how it went wrong for the attacker:
@addingdigitz @NFTNFTNFTNFT@JonGalt14@Tetranode@dopex_io Could be applied as a hedge in cases where people take out leverage against an asset (assuming growth through apy) and might get uncomfortably close to liquidation if the underlying doesn’t continue growing.
I hear this a lot:
"I wanna get into X! But first I have to learn the tech behind X, then I’m going to do a 4-week bootcamp on X, then I'm going to..." and on and on.
Instead -- just start building, assume you're going to fk up terribly, and adjust along the way.
IMO problem is that there's too many junior tutorials (any dev can learn basic Solidity syntax in a weekend) vs more advanced ones for senior ppl, some examples being gas optimizations, patterns for vault/staking/governance/asset transfer contracts, fuzzing/testing workflows etc.
So you are a dev and have seen these lists of "top software books" and you are wondering if they are worth reading as a smart contract (SCs)/web3 developer.
This is a 🧵 explaining which i think can be relevant to SCs.
👇
The last 2 years I worked w/ @noahkagan every day.
Like right next to him.
First thought, "wow this dude moves fast."
Maybe I shouldn't have been surprised (he was #30 at Facebook, founder of @AppSumo).
But everything felt like 2x speed at first.