I’m so thankful for the opportunity to be a part of this wonderful team and amazing project! 💜 According to the latest stats, there were over 12 MILLION transactions today across all our heads 🤯 I can’t wait to see where else this project goes 👀

Looking for ways to contribute to the open-source Cardano ecosystem? The @Amaru_Cardano core team has worked hard to organize some tasks that are great places for new people to contribute. We've already seen a new PR opened by @_hadelive_!

We’re not just using AI to ship faster at Sundae Labs; we’re using it to build better, while protecting what matters most: ownership, quality, and team happiness. Our CTO @Quantumplation shares the mindset: - own every line of code - use the time savings for deeper testing & stronger correctness - raise the quality bar - and turn extra capacity into real work-life balance. Watch below 👇

So uh... lovely weather we're having today?

The Gummiworm specification is now publicly available. This document outlines the architecture, communication protocols, and wire formats that underpin the project, and serves as a foundation for peer review, technical validation, and future development. Read the specification here: gummiworm.net/whitepaper/int… Feedback and discussion are welcome.

How is my username actually pronounced? This poll will decide the canonical pronunciation. Choose wisely...

We had to restart the livestream, but we’re LIVE again! Come join us! x.com/i/broadcasts/1yGBeevYY…

New flavors, coming soon.

None of this happens alone. Thanks to the 60 Pallas contributors who've shipped PRs, filed issues, and pushed Pallas forward over the years 🙏 To name a few: @amw7 @rvcas @ch1bo_ @clarkalesna @hrpr @JSHyCS @_KtorZ_ @nicolasdiprima @Quantumplation @SebastienGllmt @SmaugPool @blocksmithy @matiwinnetou @therealdisasm

I think one of the most important questions to ask when evaluating a treasury withdrawal proposal is: "Why is this a treasury withdrawal?" The Cardano treasury is ultimately Cardano's money. Cardano should spend it in the interest of Cardano. There are other funding avenues; a treasury withdrawal must have a specific value proposition for the treasury. It is up to each dRep to judge whether or not that value proposition is worth investing in. But the treasury should not be viewed as a money faucet.

I have decided to release a revised version of my analysis of @MicheleHarmonic's Gerolamo proposal. This is not because I believe I was factually incorrect in any of my statements in that article, but because I had an in-depth, professional, and respectful private conversation with Michele where he revealed some more of his ideas, which aren't documented in the codebase(s) or in the proposal. I wanted to make sure this proposal reflected the most up to date version of all the information I have. I also wanted to make sure that the content was clear, and easy for readers to understand, especially non-technical ones. I will not be taking down my previous article as I have nothing to hide, and I think it's important context for readers to have. Enjoy! I am excited to hear thoughts/opinions. x.com/JSHyCS/status/20525519…

Not sure who needs to hear this but: 1. You can vote NO on a proposal, yet agree with its goal. 2. You can vote YES on a proposal, even if you don't like who's behind it. There are many reasons to vote NO; not agreeing with the budget, not being convinced by the delivery plan, doubting the team capacity to deliver etc.. And similarly, proposers may also convince you of the value of their proposal even if that's not something you find immediately useful at first. You may also have your personal beef with them, yet recognize a good plan and their ability to deliver it. It's okay to change opinion after reading a proposal. Point being: it's not only about the "what" and the "who", but also the "how". If the content of the proposals doesn't matter; why are we even attaching metadata? If governance is about funding friends and family unconditionally, then it's not governance, it's nepotism.

We used Gastronomy, our UPLC debugger, to find a bug in Aiken's tooling. One that was causing developers to see different behavior locally vs. on-chain. Here's how we caught it. 🧵

While I am no longer a dRep, I think I can provide useful insight to dReps to help with the burden of evaluating technical proposals. I plan to start writing articles sharing my analysis of the technical aspects of governance proposals based on my professional experience. I am not looking to tell anyone how to vote, but I am hoping to provide a useful reference for dReps when they are deciding whether or not to support a proposal. I've decided to first provide my analysis of @MicheleHarmonic and his team's two active proposals, as they have been the topic of much discussion recently. You can find my analyses here: Gerolamo: x.com/JSHyCS/status/20521045… Pebble & Tooling Maintenance: x.com/JSHyCS/status/20521047… I felt very conflicted about commenting publicly on the Gerolamo proposal; I am a strong supporter of node diversity and I don't want to be seen as either undermining those efforts or interfering with "competing" proposals. However, I actually feel that my position as a strong supporter of node diversity makes my opinion more important to share in this case. Supporting node diversity does not mean blindly throwing money at any proposal that resembles a node, nor does it mean funding friends and family in the ecosystem. I hope that my thoughts prove meaningfully additive in this conversation. If you have any questions or would like clarification on anything, please do not hesitate to reach out.

Always trying to make things a little bit better for Cardano In @Amaru_Cardano, the dreaded "PPViewHash" error includes the inputs, so developers can easily find where they're making a mistake