Joined May 2021
491 Photos and videos
SWARM retweeted
Replying to @NicolasC3rny
It shocks me that four-eyes are involved in the process and are not able to provide a rationale in the edit phase, while other DReps are expected to do it for free. I can't complain about DReps like me, because I know how extremely demanding the work is when it's done as a part-time job. But when it's done by FE DRep (CF and EMURGO), the bar is higher. And if they can't provide all submitters with feedback after paying the submission fee, I don't understand why the Intersect process didn't adapt to it. The edit phase should have been extended. I described exactly this situation in my rationale for the Budget process. It was ignored. The Intersect process had one strong aspect. That was the edit phase. Not taking advantage of it and providing a rationale only after the vote, especially when I often feel that DReps haven't even read the comments on the proposal, makes me feel futile. Sorry, but FEs shouldn't be DReps. They aspire to become "execution body", and basically already are. If they are unable to fully utilize the governance process and help teams get funding, it looks very embarrassing, to say the least. Please don't take it personally. I'm just a little annoyed with what FEs have been doing in the last few weeks. I am losing confidence in our processes. Maybe Intersect should stop preparing them and ask DReps to take care of it.
1
3
12
342
After reading many dRep rationales and observing voting behavior across different #Cardano Governance Actions and proposals, I’m reaching an uncomfortable conclusion: In some cases, it feels less like the vote is reached through a consistent reasoning process, and more like the decision comes first, with the rationale built afterward to support it. “I want to approve this proposal, so I’ll find an argument that makes approval sound coherent.” “I want to reject this one, so I’ll apply a stricter standard here.” That is where the double standard becomes visible. The same weakness can be treated as fatal in one proposal and acceptable in another. The same criteria used to reject one proposal can be softened or ignored when evaluating a different one. Disagreement is not the problem. Inconsistency is. After seeing this pattern more often than I expected before Voltaire rollout, it becomes difficult to unsee, and it has reduced my confidence in the ecosystem’s decision-making quality. Am I seeing things? I wish I were wrong, but I've seen too much to believe it's just a distorted perception.
5
4
15
598
SWARM retweeted
Built a simple tool for dReps to track their votes/priorities for all currently live Cardano Treasury Withdrawals. Stores your preferences in localStorage and you can drag drop proposals to re-order them. Can also export a PNG/SVG to easily share them. Link in the comments 👇
6
17
65
2,031
As the Cardano Beyond MVG workshop comes to a close, the team will dig into the data for final analysis. Do the current recommendations address the challenges we face?
In the upcoming Beyond MVG workshop, we will attempt to refine the Cardano Constitutional Committee Recommendations and finish the workshop series with a retrospective. beyond-mvg.vercel.app/worksh…
153
Help shape the future of Cardano governance! Over the next three weeks, Beyond MVG is hosting interactive workshops where community members co‑create recommendations and use the Beyond MVG app to prioritise them. Sign up via linktr.ee/BeyondMVG
Cardano governance data has been collected. Analyzed. Debated. Now we're asking the real question: what do we actually fix? The Beyond Minimum Viable Governance team is running a series of community workshops on Governance Recommendations & Prioritisation this month. 6 of them are already scheduled. Find dates, times and registration links on our linktree.👇 linktr.ee/Beyondmvg #Cardano
1
1
117
SWARM retweeted
In a hour or so we be having one hell of a Governance WG session, so many dependencies and vibe coding involved :D Let's see, does that elevate our collective capabilities in live workshops? You will find workshop registration in Beyond MVG linktree linktr.ee/BeyondMVG
1
1
1
109
SWARM retweeted
CGOV now has a DRep Dashboard & profile pages, making it easier for you to explore and study DReps at Cardano Onchain Governance,. a thread ⬇️
1
9
31
3,381
SWARM retweeted
Cardano has a lot of visible work: launches, announcements, debates, big ideas. But a healthy ecosystem also depends on the unglamorous work that almost nobody sees, the editing, review cycles, cleanup, coordination, and relentless attention to detail that turns rough drafts into something the community can actually build on. This year, a huge amount of that load has been carried by Robert Phair (@rphair). He’s spent countless hours moving the CIP process forward: editing, reviewing, nudging, fixing typos, making commits, and doing whatever was needed to keep proposals progressing. It’s thankless work, and most people won’t even know his name; yet it is the foundation of the entire ecosystem. If you care about Cardano maturing, you should care about the people doing this kind of stewardship. Robert is one of those rare contributors who shows up consistently, does the hard parts, and rarely asks for anything. He deserves real recognition for the impact he’s had.
26
47
373
11,487
SWARM retweeted
The probably easiest way to explore DRep rationales is via cgov which allows you to: - filter DRep votes on each proposal - easily find & read rationales - built in language translation of all rationales - download votes & rationales
5
6
26
6,730
SWARM retweeted
Feb 10
we salute @Fabian_vBergen, his work and his doings. Rest in peace brother 💙
18
11
97
14,885
SWARM retweeted
CGOV V2 Release. You can now connect your wallet and vote as DRep on onchain governance actions. Compatible with all Cardano Wallet browser extensions. 🫡
4
13
27
2,451
Fund 15 voting delay – public accountability request The start of #ProjectCatalyst Fund 15 voting was officially scheduled for January 13th. January has fully ended and, as of now, there is still no confirmed new date for the beginning of the voting stage. Since January 13th, there has been only a single public update (details about it on the bottom 👇🏻), which acknowledged the delay in vague terms and did not explain the underlying cause. No technical details, no blockers identified, no revised timeline. Since that update, there has been no substantive public communication. There has been no public follow-up post, no written clarification explaining the cause of the delay, and no concrete timeline update for proposers, reviewers, voters, or dReps. While the Catalyst Team has replied to some questions in community groups, those replies have only pointed back to the January 13th announcement, without providing new information on what caused the delay or what is currently being done to resolve it. We are now approximately 3 weeks past the original schedule, still without transparent, publicly accessible details on the root cause and remediation plan. The core issue here is not the delay alone. Delays can happen. Systems are complex. What is unacceptable is delay combined with a lack of clear, public communication in a treasury-funded program. Project Catalyst is funded by the Cardano Treasury and exists because it received massive community support to continue fostering open, community-driven development. That funding and trust come with an obligation to communicate clearly, especially when timelines slip. Tagging responsible parties for visibility and accountability: @krissbaird @dannyribar and @fayyaadhadams from the @Catalyst_onX Team, and @JBriggsLondon from @IntersectMBO (the MBO responsible for fund distribution process and outcomes/deliverables verification). This needs a proper response: 🔹 What specifically caused the delay? 🔹What systems or processes were affected? 🔹What has been done since January 13th? 🔹 And most importantly, what is the updated timeline with concrete dates? The community deserves more than vague updates and weeks without substantive public information. Accountability and transparency are not optional in a treasury-funded program.
ℹ️ Please read the update about today's scheduled start of Fund15 Voting: projectcatalyst.io/blog/upda…
9
12
42
1,881
I received your feedback, I sound negative. Optimism is nice. Evidence is better. Help us measure Cardano governance using real experience, not assumptions.
Probably at this point I'm spamming, but submitted here a more elegant invite to Beyond MVG workshops with context and all :D forum.cardano.org/t/beyond-m…
1
116
We f'ed the Constitution up without clearly articulating our values. Let’s not make the same mistake with governance metrics. Join Beyond MVG or host your own and help ground Cardano measurements in real experience!
Cardano governance doesn’t wait and neither do we. Join any of the Beyond MVG workshops to share your governance experiences 🗓️ 27 Jan 15:00 UTC | 29 Jan 03:00 UTC | 31 Jan 17:00 UTC linktr.ee/BeyondMVG
1
3
294
SWARM retweeted
A long time ago, I mentioned a tool called Cquisitor cardananium.github.io/cquisi… here. It has now been updated with a more convenient UI and some new, cool features. It can now:

2
13
43
5,638
19 Dec 2025
how did this one went ? Said to call it up a year later, has been exactly one year now x.com/CatalystSwarm/status/1…

19 Dec 2024
Guess what, one day DReps will go live at Catalyst too, having a CF voting on proposals will be likely just one of many big players. Most wont remember then what and why CF is pushing on that now. Many large DReps wont have a fraction of the interest to speak and listen to the community as CF does. Call this tweet up in a year again hehe ^^ Hope so much to be proven wrong bt the future, but honestly, dont think that this will be the case
73
SWARM retweeted
15 Dec 2025
Mesh plan to build Bitcoin toolings starting with Bitcoin wallet package. That means projects building on either or both chains can benefit from having one unified tool. Question is, if we build it, who wants to use it? Want to sense check before committing resources. Tagging some projects doing some BTC stuffs, @FluidTokens @SundialProtocol @lace_io @BeginWallet
1
4
11
824