Below you will find my write-up as an independent after action report for the issue impacting Cardano late last week, along with things I learned, why I was impressed, and what I think we can do better at in the future. I try to strike the balance between confronting the seriousness of the issue, while defusing most of the over-stated positions from talking heads on Twitter. This is an adult conversation, not whatever the children are engaging in on Twitter this week. I don't think it's productive to get into debates of what constitutes "downtime" or not; Instead, I tried to equip you with a framework where you, dear reader, can think about these things for yourself, and decide what you want to call it. I just ask that you make that decision for yourself, or allow your audience to do so, rather than parroting some pre-decided talking points. More informed discussion leads to a higher quality industry overall. 314pool.com/post/cardano-pos…

Cquisitor has become one of my most used Cardano tools, so I always try to give back; If you're looking at sundae v4 transactions, cquisitor now renders all the gritty details. It should help you integrate, if you're so inclined, for example!

We calculated roughly 2 trillion blake2b hashes to find this seed to set the Sundae v4 pool contract address: addr1zysundaev4jxq60ehm8tlz6v8nk6lpxpnvgfa2jeszs55f4uzrlrz2kdd83wzt9u9n9qt2swgvhrmmn96k55nq6yuj4qeujly6 Pay close attention to the start of that address 👀

"Forgive the longer message, I did not have time to prompt Claude into producing something shorter", or whatever Blaise Pascal said

000000693663783b

We're moving fast and aggressively to make Sundae Float the nicest, most all-encompassing platform for DeFi analytics :)