Before we start blaming DReps, the community, fatigue, price action, or anything else, I want to give what I think is fair feedback on what went wrong with the proposal, why it failed to pass in the first place, and how this could have been avoided.
Instead of becoming something positive that the community could be excited about, the proposal turned into something people rolled their eyes at. It even became one of those proposals where the community used the vote to make a point about where it stands with founding entities.
In my opinion, this could have been avoided if the process had been handled correctly.
How it started
On November 13th, 2025, during the closing remarks of the Berlin Cardano Summit 2025,
@F_Gregaard revealed that the next summit would happen in Singapore on October 5 and 6, around the time of TOKEN2049.
This was actually a good decision. It showed that the
@Cardano_CF understood the need to get in front of the right crowd. We do not need to go too deep into that, but I do not think many people had an issue with the location or timing.
There was also a good balance between having the 2025 summit in Berlin, which gave many of us “eurepoors” a fairly accessible location to attend, while already knowing that the next one would be a bit more prestigious and internationally focused.
Up to this point, there were no real mistakes.
Where things started going wrong
Unfortunately, the mistakes started after that.
From November to March, there was basically nothing. No communication, no community involvement, and no visible public process. It felt like silent work by one corporation preparing an event and a treasury proposal behind closed doors.
In my opinion, this was the most crucial period, and it is where the proposal failed before voting even started.
That time should have been used not only to prepare the summit, but also to actively involve the community. If conversations were happening, they should not have been behind closed doors. They should have been public.
There should have been open AMAs with key builders, community members, and ecosystem participants. There should have been feedback rounds about what could be improved from previous years and what people wanted to see from the next summit.
Honestly, there should have been at least three or four smaller, connected PUBLIC sessions each month. That would have communicated two important things to the community: that you were present, and that you cared.
It would also have helped set expectations early. Even if you did not have exact numbers, you likely had ballpark figures in USD, since you were already working on the proposal. Sharing those early would have helped prepare the community for what was coming later in the year.
You could have used spaces, streams, open forms, and one-to-one calls with important community figures to turn the summit into something positive, as it should be. During those feedback rounds, I think you would also have learned that one of the things you should have done was invite a few people and projects from the community to Singapore so they could be represented.
Whether that meant free tickets, or a more tailored opportunity such as covered travel and accommodation, I do not think many people would have had an issue with it. Even if it increased the cost, most people would agree that having those people and projects at the summit would be beneficial (crucial) and would improve the ROI of the event.
Instead, what the community got was early-bird discounts and one blog post on March 3rd, looking back at the previous year. In that post, you also stated that some things for the 2026 summit had already been covered from 2025 summit revenue, and that you would again need to open a treasury withdrawal for the next year.
So, to sum up the period from November to March: you failed to communicate, you failed to work with the community, you failed to understand your own community, and you failed to set expectations for an important proposal.
The result? No Cardano Summit in 2026.
The April proposal
Then, after all of that, and after already losing five months, April 9th arrived and the first proposal was published as a joint proposal with
@emurgo_io/
@phillip_pon.
The exact decision-making process behind that joint proposal is unclear to me. I could speculate, but honestly, meh. The important point is that this was the version the community first had to react to.
The wording was essentially: if this does not pass, we will not make any changes, and there will be no summit this year.
I have to ask: are you mad?
Do you live in this community with the rest of us?
I will not call out specific people or entities, but do you understand that the community has had enough of feeling like it is being held in a chokehold by people or entities above it?
In my opinion, this was the second biggest issue with the proposal. Maybe if that announcement had been worded better, with a deeper explanation of what, why, and how, and with more transparency, you would not have faced such a strong backlash.
But there it was, backlash.
The reaction came too late
I also want to point out your reaction after April 9th.
You were silent for several months, and only after receiving backlash did you become more proactive. We then saw FAQs, spaces, more posts from CF, and more communication from involved individuals.
Honestly, you have to understand how that looked. At that point, it was too little, too late. The sudden activity and care came across as fake and dishonest, as if it was only happening to get the proposal passed.
Then came another issue.
After strongly stating that you would not resubmit, you resubmitted anyway, and quite quickly. It was only during the early UTC AMA spaces that I understood why: vendors were chasing you, and you needed to lock the venue and make payments.
You were forced into a corner, so of course you had to resubmit around April 28/29th.
But honestly, even if the proposal ask had dropped by 50 to 60%, I do not think it would have passed. The damage had already been done. You cannot go back in time and fix months of silence, inactivity, and blindness toward your own community.
After forcing the proposal onto the community in quite an aggressive way, the damage was already done. Even if you listened during that short window, it was too late.
Again, this could have been entirely avoided.
The second proposal was not enough
I also want to add that changing the proposal was not enough.
There were some small pushes and some communication, but from April to late May, you were again fairly silent and inactive. It felt like you thought you had done your work, made an easy fix, and could move on.
No.
You should have been campaigning and working on getting the proposal passed every day and night (actually every single day 24/7, no breaks, no weekends) from the April resubmission until the voting deadline on May 29th. That might have changed the result.
You did make some good decisions, such as abstaining from voting, but even that felt reactionary to backlash. At that point, I think you understood that voting for yourselves would do more harm than good, even if it meant the proposal would not pass.
But again, all of this could have been avoided.
Final thoughts
To sum up, it is a real shame that there will be no summit in 2026. The intention was good, and the value created could have been real.
But the proposal should never have passed in the way it was handled.
I hope you learn from this and understand where the mistakes were made. It is not all because price is down bad, and therefore people do not want spending. Spending and investment into Cardano are important, even during a bear market, and this was one of the initiatives that had potential for real returns.
But you failed to set expectations. And maybe, for the first time, you got a real taste of the impact that can have on your operations.
Hopefully, 2027 will be better. There is plenty of time.
But let this be a warning: if you come back in six months with another blog post saying how sad it was that we skipped 2026, and that here is a new proposal to vote on because we cannot miss two years in a row, it will fail again.