Top Tweets for #CardanoDevs

Reminder: Calling all Cardano Developers! The State of Developer Experience Survey is Live! Respond now! 🔗 👇 English - https://t.co/4N83tGpOcf French - https://t.co/0CCACZucYO Portuguese - https://t.co/cz22tWBjfP Japanese - https://t.co/7Dq3p7WwN8 Chinese - https://t.co/pBkIEjHipD

Hey, if anyone wants to claim 400 Ada from the attacker just deregister the stake credentials they are using (you get 2 Ada per stake credential you deregister and the attacker is using 194 always succeeds credentials). Also, this would immediately stop their DDOS on the network (it would cost another 400 Ada to start again which could then immediately be stolen from them). Just to clarify, the network is behaving as intended. Liveliness is unaffected. Everything (block size limit, transaction size limits, block times) are all set so conservatively that any attack on liveliness is a total waste of funds. Even with validators deserializing 194 junk scripts (~16kb each) per transaction the validators are totally fine processing these transactions (which involve deseralizing roughly 200x what they are used to). If anything this is a really great illustration that we have a huge amount of leg room to bump up the parameters safely. The idea behind this attack is to take advantage of the fact that the size of reference scripts currently does not impact the transaction fee, but it does impact the work that validators have to do to process the transaction. However, it actually does indirectly have a cost because each script execution incurs the CEK setup cost and requires an additional reference input which increases the transaction size.