AtlasHub

This proposal represents a proportionate continuation of an established open-source developer platform that alredy provides value to the Cardano ecosystem.

I am completely unhappy with the intersect budget process as it fragments descriptions across varying levels of detail and different sources.
However, this should not be at the expense of the project. Dolos is mature, open-source Cardano infrastructure that reduces resource requirements for chain-data access and improves developer experience. I have changed my vote to “Yes” – future support should be dependent on continued ecosystem adoption and remain conditional on transparent reporting, protocol compatibility, releases, issue resolution.

Blockfrost is already critical Cardano developer infrastructure, and the proposal meaningfully converts it into a community-governed public good. The transfer of source code, trademarks, domains, and associated assets justifies treasury support more strongly than a normal operating subsidy. My support is based on enforceable IP transfer, transparent board elections, public cost and revenue dashboards, quarterly reporting, milestone-based disbursement, and a credible sustainability plan before the end of the 18-month period.

These Intersect excerpts are tedious.
But given this is mature, open-source infrastructure, that is already widely used in the Cardano ecosystem to stream blockchain events, it has my support.

If there were full descriptions instead of excerpts only here, the treasury governace process would be less cumbersome.

Plutarch and Ply are mature, open-source development tools with demonstrated adoption, so "Yes".

Again only an excerpt "sourced from the approved proposal submitted by the Vendor as part of the Intersect budget process". It's getting tiring.

But Mithril is of strategic importance to the whole Cardano ecosystem, so this has to pass.

I cannot support that, no matter how hard I try.

This proposal combines many operational functions into a single 25.4 million ADA request.
This does not work out. The proposal does not provide enough granularity, prioritization or metrics to justify that amount. The funds will simply evaporate without yielding any results.

Although this treasury withdrawal action is only a partial excerpt of the original proposal from the Intersect budget process and remains underdefined here, I consider this to be useful work:
Standardizing transaction construction accross Cardano applications as open-source infrastructure.

Although this is only an excerpt as a description here, given the proposal's objectives, Palla's role in the ecosystem and the principles put forward, this has my support.

Again only an excerpt , and I have some reservations (sound reporting and clear deliverables are required). However, I do not want to stand in the way of governance support.

Although this treasury withdrawal action is only a partial excerpt of the original proposal from the Intersect budget process and remains underdefined here, I consider this to be important work: It focuses on maintenance, evolution and useful standards for supporting the ecosystem.

The proposal is addressing a structural problem in treasury governance:

How can the Cardano ecosystem allocate treasury capital efficiently, when DReps realsitically are not able to perform due diligence checks on hundreds of projects?

Despite the risks lying in a large budget, the introduction of another meta-governance layer and a concentration of decision-making, my vote is "Yes" here.

Again, the description of this treasury withdrawal action is only a partial excerpt of the original proposal from the Intersect budget process. It leaves out elementary contents and remains underdefined here in my opinion. This is making the treasury govenance process even more fragmented as it already is.

With respect to the contents presented here, ist is unclear, if the Cardano ecosystem would still benefit, if the original platform disappeared. This remains a grey area, thus my vote is "No".

Although this treasury withdrawal action is only a partial excerpt of the original proposal from the Intersect budget process and remains underdefined here, I consider this to be important work.

The description of this treasury withdrawal action is only a partial excerpt of the original proposal from the Intersect budget process. It leaves out elementary contents (e.g., the treasury return clause to name just one example). DReps have to painstakingly piece this information together themselves. And here it becomes completely unacceptable in my view. How much more fragmented is the treasury governace process supposed to become? For me, this simply remains underdefined here.

I consider this important work to be done.

Supporting BTC DeFi.

This project offers several benefits:

• Supporting a protocol with proven track record
• Capital remains treasury owned, yet in a productive form
• The Cardano ecosystem also needs commercial growth

There are also riskd:

• Exposing funds to DeFi risk
• Concetration in a single protocol
• Operational and custody complexity

The treasury opportunity cost argument applies to all funded projects; therefore, despite the difficult market situation, this cannot be the reason for exclusion in this case.

My point is that this Ecosystem needs growth. And with growth, I also mean commericial growth.
We cannot afford to simply sit back and focus on great technologies that lack commercial relevance.
I hold the view that the treasury must not be limited to public goods and core protocol development.

Therefore, I am voting with "Yes".

After considering the matter at length, I have decided to change my vote to "Yes."
I generally view the issue of supply chains as challenging, particularly because projects supported to date have never subsequently become visible.
And also this project has some considerable risks:

• Large upfront payments
• Dependence on external adoption
• Very ambitious KPI projections

However, there are also several points suggesting that this project can deliver genuine value and be successful:

• A strong case of ecosystem collaboration
• Real-world adoption focus
• Existent operational proof

Given that the Cardano ecosystem needs concerted action and projects that pursue clear strategies, I am changing my vote to "Yes".

Eternl is a flagship wallet within the Cardano ecosystem. Being a wallet, it has the characteristics of a public good and should be supported.

Supporting the upgrade with its improvements.

I am abstaining, as this is my own proposal.

This should have been resolved by our official entities long ago.

Hydra is one of Cardano's core technologies.

Research defines Cardano's profile.

ack

Open source core protocol and infrastructure technology - AtlasHub is supporting this proposal.

We assess this event to be primarily appealing to insiders.
While it may be a great community event, it is exactly this:
An event focused on the already existing community with little impact for ecosystem direct growth and opaque synergistic effects.
Given the current market condition, AtlasHub unfortunately does not support this event.

AtlasHub supports the upates to enhance the capabilities of Cardano.

V1 has already achieved visible results. AtlasHub supports to proceed.

Wallets are critical infrastructure within a crypto ecosystem and while everyone not only wants but has to use them, nobody wants to pay for maintenance or development. That being said, wallets share the tragedy of the commons. As Eternl is a flagship within the Cardano ecosystem, AtlasHub supports this proposal.

This proposal still appears unbalanced in terms of scope, dependencies, and schedule.

This proposal suggests a parallel bureaucratic vehicle in which funds simply evaporate.

We already supported the previous Stablecoin DeFi Liquidity Budget Info Action. This is the next logical step to move the project forward.

This is a long-term strategic project that has already reached several milestones. Even if multi-node diversity is not the highest priority under the current conditions, the project should be continued.

In order to be considered a "Constitutional Committee", the minimum requirements for the body should not be lowered.

Voting for 350M.

We continue to vote NO on this action because of poor legal writing, the large number of changes, the vague legal terms, and the unpredictable consequences in interpretation.

This is a completely opaque action that arbitrarily increases the number of members beyond the amount stipulated in the constitution. Furthermore, there are good reasons for having an odd number of members.

Too many changes, unclear or ambiguous definitions and introduction of indeterminate legal terms (poor legal writing) as well as absolute unclear combined or unwanted side effects. As a very simple example among many other problem areas: The crucial difference that can exist between Ada Owners and Ada Holders is completely ignored (just think of trust relationships as a simple case).