danimim.eth

How about @AskVenice's VVV on Moonwell? WELL holders get to decide. Voting is open.

.@MoonwellDeFi was one of the first, launching the card product in 2024. 🌜💳🌛

We have prevented a governance attack in Shutter DAO (0x36): ~$100K of SHU tokens could capture a treasury of +$3M We are committed to securing the @ethereum ecosystem, its protocols, team and investors. Here are the details 👇

Latinoamérica es prácticamente un país gigante; sus ciudades son tan similares que esa foto podría ser de cualquier país latino.

have you ever considered being happy? idk maybe it helps

Over the past 7 years, POAP has made this entire ecosystem happy. It brought us joy through the NFTs themselves, the patches, stickers, pins, the painting parties… POAP showed a use of blockchain beyond DeFi. It’s been with us throughout the entire ride of this ecosystem, through bear markets and bull markets, showing us something much deeper: The importance of memories, of celebrating, of connecting, of being part of something together. Thanks to @worthalter for putting your heart and soul into this mission. Thanks @izgnzlz for pushing its growth and helping take it to the next level. Wishing you the best in whatever comes next. But no matter what happens, POAP will always live in our hearts.

the end of a very fun era 🥺

The solver routed through Sushi not because Uniswap liquidity was unavailable, but because the route generator was solving the wrong objective. At block 24643150, the Uniswap v3 AAVE/WETH pool 0x5ab53ee1d50eef2c1dd3d5402789cd27bb52c1bb held 53,164.7261 AAVE and 523.4226 WETH, which is about $6.93M at the incident-block Aave oracle prices, while the Sushi pool 0xd75ea151a61d06868e31f8988d28dfe5e9df57b4 held only 331.6320 AAVE and 17.6533 WETH, about $72.8K. But the replay trace of the actual settlement shows the executor 0x699c... explicitly did USDT -> WETH on Uniswap v3 0x4e68..., then called Sushi getReserves() on 0xd75e..., then immediately called Sushi swap(); the original calldata already embedded the Sushi pool address, so this was pre-encoded route selection, not runtime discovery. The reason this could still “win” is that CoW only had to satisfy the signed minimum 324.949260918... aEthAAVE, with an implied quote of only about 328.93 AAVE, so from the solver’s perspective a pool containing roughly 331 AAVE was enough inventory to clear the order, even though it was economically insane relative to fair value. In other words, the solver was not constrained by “find the deepest AAVE venue” or “find output consistent with market reality”; it was constrained by a catastrophically bad order floor, and once that floor was wrong, a dust-liquidity Sushi pool became admissible even though a rational fair-value router should either have used deeper Uniswap AAVE liquidity or rejected the route outright.

Imagine hearing "MOOOOOOO" after losing $50M 🤣🤣🤣

"yeah we are using API and CLI not MCP with AI to do the LLM and the ABC and the XYZ bro"

learning AI skills so that i can stay ahead in a changing world

@britodeisabella eu também, eu juroooo, fiquei assim 😐😐😐 não entendi nada

@danimimm e eu pensando que a final do pernambucano ontem tinha sido tensa 🥴 (side note: é a primeira vez NA VIDA que vejo mineiro na porrada)

cinema, ter assistido ao jogo ontem foi tipo sair pra ver futebol e ganhar um UFC de bonus

@nomos_paradox interesting, gladly I don't click links, also i really hope this is not a very bad "growth hacking"

Just got a account creation verification email as well. Sounds like this is widespread.

Just putting it out there: someone tried to create a Kalshi account using my email. And to be clear, I am zero into prediction markets. I do not have the time. Cheers

Dear @PancakeSwap. Looks like you copied our code without asking. It is violation of its license. Not only it is illegal: historically it showed to be unwise for those who did it this way in other regards. In any case. If you want to enjoy using stableswap without legal problems and to borrow some of our expertise to keep users SAFU - you still can contact us for licensing and collaboration.

open.spotify.com/track/0kl6Ozan… @ANOTR

@hackerdocc Noooossa, esse contexto eu não, tinha. Bom, que leve processo então. Tomara que alguém continue o projeto, a ideia é boa. Seria massa ter essa visibilidade desses dados. Obrigada pelo contexto, amigo!

ele mentiu pra todo mundo de propósito pra conseguir mídia, como ele faz com frequência na internet. ele fez uma cena dando a entender que já tinha achado casos de corrupção fazendo isso, censurou nomes supostamente de políticos corruptos, fez um drama sobre ser perseguido, enrolou todo mundo por dias enquanto surfava essa onda, e daí eventualmente foi forçado a revelar pra todo mundo que não tinha nada sim é um grande problema que os dados são mockados, porque é uma grande parte do projeto e se ele não fez nenhum progresso nisso o resto tudo é só fachada. do que adiantam esses supostos algoritmos vibe-codados de identificar corrupção se ele nem têm os dados pra validar? se é só uma questão de puxar os dados porque ele não fez? ninguém deve levar a sério uma base de código que não foi testada. ninguém deve levar a sério uma investigação em dados públicos que nem existem, ou são de difícil acesso o problema da mentira dele é que levou muita gente a pensar que sequer conseguir esses dados é viável ele farmou publicidade em cima do combate a corrupção, e enganou muita gente. não tem como tornar essa história em qualquer outra coisa senão isso talvez alguém até se inspire por isso e faça alguma coisa. mas honestamente é um desrespeito tremendo como todo mundo que levou ele a sério e esperava algo disso: ele é um salafrário tão ruim quanto os políticos que ele quer pegar

"No one sees me, yet I am everywhere." — Oscar Wilde, The Canterville Ghost

@jnptzl o brasileiro já foi de vala... não adianta fazer nada mais

@danimimm no good deed goes unpunished