Se7en Labs: Daedalus Wallet Maintenance and Improvements 2026-2027
180 DReps voted · 64 with a rationale · 2 changed their vote
Open a row to read the rationale.
- Yes182.6K ₳No rationale
- Yes164.8K ₳No rationale
- Yes163K ₳No rationale
- No161.1K ₳No rationale
- Yes157.8K ₳No rationale
- Yes157.6K ₳No rationale
- Yes149.7K ₳Rationale
Good ROI
- Yes142.8K ₳Rationale
I vote Yes. I'm eager to be able to use DeFi from my Daedalus node.
- Yes138.3K ₳Rationale
Se7en Labs: Daedalus Wallet Maintenance and Improvements 2026–2027 — Voting Rationale
Governance Voting Rationale GAID gov_action1mr0...4yjd6j Title Se7en Labs: Daedalus Wallet Maintenance and Improvements 2026–2027 Type of GA Treasury Withdrawal Amount 1,785,333 ADA (1,666,667 labor · 33,333 test hardware · 33,333 financial audit · 52,000 Intersect administration) Date submitted Epoch 639 (Jun 23, 2026) Expiration Date Epoch 646 (Jul 28, 2026)
Contents
- 1.0 Introduction
- 1.1 Summary
- 1.2 Description of Governance Action
- 2.0 Discussion
- 2.1 Method
- 2.2 The sort, published
- 2.3 The good, stated as a relation
- 2.4 The private-surplus burden
- 2.5 The floor, and the six rights in brief
- 2.6 What the vote does not reach
- 2.7 Fiduciary verification (external instrument)
- 3.0 Conclusion
1.0 Introduction
1.1 Summary
We are voting YES on this governance action to fund twelve months of maintenance and development for Daedalus, delivered by Se7en Labs.
I want to be precise about the character of this YES, because the framework I vote by treats a for-profit entity drawing 1.78M ADA from the treasury as a claim that must be examined at its structure rather than waved through on its usefulness or refused on its tax status. Both of those shortcuts are errors, and the sort exists to avoid them.
Three things carry the vote. First, the action sorts shallow: it is a discrete, named-deliverable maintenance grant that lapses on its own terms, and the sort's most useful service here is to refuse the commercial sector label as a routing key. Second, the load-bearing test for any treasury withdrawal to a for-profit — the published private-surplus burden — is not merely attempted but discharged about as completely as a for-profit maintainer can discharge it. Third, the good, stated as a relation rather than a deliverable, is a genuine commons relation with direct rights anchoring: Daedalus is the only full-node desktop wallet, the primary path by which a non-technical participant reaches the chain without trusting a third-party backend. Funding its maintenance strengthens the rights it touches and harms none.
This is a YES on the merits of the action. It is not a YES to everything the proposal says about itself. Several signals the reading surfaced: the proposal's self-referential justification against a strategy framework its own authors produced, its KPI framing, and the standing single-maintainer dependency it services, are real, but they are readings of the ecosystem's trajectory and vocabulary, not findings about this action that the ballot could carry. They are recorded below and carried to the trajectory log rather than converted into the vote.
1.2 Description of Governance Action
This is a Treasury Withdrawal funding a twelve-month, time-and-materials engagement by Se7en Labs, Inc. for maintenance and improvement of the Daedalus desktop wallet. Daedalus is Cardano's only full-node desktop wallet: it runs an embedded node, derives all wallet and governance data directly from the chain with no third-party APIs or trusted backends, and generates and stores keys on-device. It is released under the Apache License 2.0.
The scope covers three registers. Protocol maintenance: node currency, hard-fork readiness, and Leios/Peras/Nested-Transactions compatibility, with a compatible release at least two weeks before every mainnet hard fork. Ecosystem expansion: Keystone and Flex hardware-wallet support, a CIP-30 dApp connector, and Japanese localisation. And user support, with a scoped architecture assessment published regardless of outcome.
Administration and oversight run through Intersect as administrator and independent milestone verifier under Article II.7.5, using the Sundae Labs treasury-management smart-contract framework, with a six-entity Oversight Committee, milestone-based disbursement controls, monthly disbursement against verified work, and unspent budget returned to the treasury at contract close. The proposal states compliance with the 350M Net Change Limit for the applicable window, and discloses that Se7en Labs has received no treasury ADA in the prior 24 months, having operated under a direct IOG contract for Daedalus maintenance since January 2026.
2.0 Discussion
2.1 Method
Every governance action gets read; not every action earns the same reading. This DRep runs each action first through the intake and sort, which assigns a lane (how much analysis the action earns and which instruments run on it) before any merits are read and before any standing policy is applied. The sort returns depth, never a verdict. The token is then selected downstream, under the abstention-spine discipline, where the operative question is not whether a vote helps a proposal pass but whether a warrant has been derived to deploy delegated stake against it.
Reading the merits first and then choosing the depth is how depth ends up chosen to fit a conclusion already reached, so the order is held. The sort is published with the rationale, because a reader who disagrees with the vote is owed the ability to locate whether the disagreement is about the sort or about the analysis, and those are different arguments, and only one of them is about the proposal.
2.2 The sort, published
Reading Axis 1 — wall / knob / wall-building Knob. A discrete twelve-month engagement with named deliverables that sunsets at term and returns unspent funds. No structural constraint is treated as tunable; no default is installed where a per-action decision now stands. Renewal is not by default — each cycle requires a fresh proposal. The claim reconstructs cleanly as service compensation and sits under, not senior to, the commons' discretion. Axis 2 — exit-remediability R3 — reversal by inaction, with a logged mild decay note. Measured at the failure mode: if the engagement proves wrong, not renewing is the default, and monthly milestone-gated disbursement stops a mid-stream problem before it completes. The deeper failure mode — a sole full-node wallet falling behind at a hard fork — is a pre-existing ecosystem dependency this action services and reduces, not one it manufactures; vendor-specific lock-in is bounded by Apache-2.0 forkability and the documented drt/Nix toolchain. Terminal band stays R3. Axis 3 — epistemic-dependency depth D1, brushing D2. What reads through Daedalus reads mostly within its own domain: settlement access for its user cohort. Its governance-data-from-chain property is a positive for informational integrity, not a dependency risk. Critically, if Daedalus degraded, the degradation would register through public GitHub repositories and mainnet — external to the vendor, the opposite of a self-concealing D3 signature. The proposal makes its own success metrics externally verifiable by design. Lane Shallow. Procedural check, Hippocratic floor, public-goods reconstruction, vote, short rationale. The sort ran before merits and before any standing policy. That ordering is key here, and the case it protects against is exactly this one: a for-profit entity maintaining a widely-used open-source tool carries a commercial sector label while presenting a non-rivalrous good with discrete delivery, which is a commons-derived claim by every axis that matters. A standing policy keyed to the sector label would fire on it wrongly, and because explicit abstention has a direction (it lowers the passage bar) the mis-fire would not be a null act. This proposal is the Archetype A the calibration was written around, and the sort keeps standing policy from doing work the derivation did not authorize.
2.3 The good, stated as a relation
Asked what the good is as a relation rather than a deliverable, the proposal answers largely in deliverables: node upgrades, a connector, a localisation. But a genuine relation is present and it is the one that matters: Daedalus is the only full-node desktop wallet in the ecosystem, and therefore the primary mechanism through which a participant without command-line fluency runs a full node and reaches the chain without trusting a third-party API or backend. The good being funded is the maintained existence of a non-custodial, non-intermediated path to settlement for the cohort that would otherwise have no alternative preserving that standard.
That is a capacity the commons maintains, not a product a vendor sells, which is what makes it a public good in this framework's sense. On rivalry: the good is non-rival and non-excludable. Under Apache 2.0 the source is public in perpetuity and forkable by anyone; there is no captured customer relationship, no subscription, no token, no IP exclusivity. No participant is excluded, and no mechanism of exclusion is created.
The relation is directly rights-anchored. It is settlement access (Right I) for the self-sovereign cohort, and it is exit integrity and productive autonomy (Right VI): a forkable, auditable, on-device-key wallet is precisely the arrangement under which a participant can exit any custodial or backend relationship without forfeiting access. Maintaining it moves both rights in the protective direction.
2.4 The private-surplus burden
The published burden is the test this proposal must pass, and it is worth stating in its own terms: treasury funds may fund the maintenance of commons relations; they may not fund the transfer of a private surplus. This is a test of claim structure, not of the recipient, a for-profit maintaining a non-rival good the ecosystem depends on presents a commons-derived claim, and the recipient's tax status is not asked and does not bear on the answer. Where a proposal seeks funds for an activity generating private surplus, the burden is on the proposal to show that a commons relation is maintained, stated in relation terms; expected-value and ecosystem-growth arguments do not discharge it.
The proposal's "Nature of This Proposal" section is an unusually direct answer to exactly this burden. It states that Se7en Labs does not monetize Daedalus usage and captures no customer relationship, subscription revenue, token value, or IP exclusivity; that all funded outputs are public assets in perpetuity, forkable under Apache 2.0; and that the treasury is funding maintenance of community infrastructure rather than subsidizing a private business expansion. What Se7en Labs receives is service compensation: labor at USD-denominated rates, invoiced at spot and converted to stablecoin, which is the legitimate-service-compensation category the corrupted-terms test in Right I explicitly preserves, not extraction beyond service value.
The burden is therefore not merely attempted in good faith; it is discharged, and the claim structure is commons-derived on every axis the framework recognises. Under the burden-contested spine's outcome table, a discharged burden with the relation genuinely served returns the proposal to evaluation on the merits like anything else, no standing abstain fires, because the standing thing is the burden, and the burden is met.
One qualification: the proposal's KPI-alignment section leans on expected-value and ecosystem-growth arguments: MAU toward one million, transaction counts toward a 2030 target, which are exactly the arguments the burden says do not discharge the relation question, because they answer a quantity question in place of the relation question. What saves this is that the proposal does not rely on those arguments to discharge the burden; it discharges the burden separately and completely on claim structure, and the growth framing is decoration in the ecosystem's current vocabulary rather than the load-bearing justification. The burden's own answerability clause also applies charitably here: to the extent the growth matters, maintaining Daedalus produces growth in productive settlement capacity for the self-sovereign cohort, which is productive activity, not price, valuation, or attention. The growth framing is logged as a vocabulary signal; it does not convert a discharged burden into a contested one.
2.5 The floor, and the six rights in brief
The shallow lane runs the Hippocratic floor and a public-goods reconstruction, and both are already substantially answered above. Read against the six rights as violation tests, the action harms none and strengthens several. Settlement access (Right I) is maintained at its only full-node desktop point of entry. Self-determination (Right VI) — exit integrity and productive autonomy specifically — is strengthened by a forkable, non-custodial, on-device-key wallet. Informational integrity (Right IV) is served rather than strained: the wallet derives governance and chain data directly from the chain, key handling is auditable because the source is open, and the proposal's success metrics are independently verifiable from public repositories and mainnet without reliance on applicant self-reporting. No monetary parameter is touched, so unit-of-account integrity (Right II) is not engaged. Governance participation (Right III) and commons integrity (Right V) are not harmed; the administration architecture — Intersect as independent milestone verifier, a six-entity Oversight Committee, monthly disbursement against verified work, unspent-returns — is a contestable, auditable arrangement rather than a concentrating one.
The floor is cleared comfortably. No abstention spine triggers: the finding is expressible as a property of this action, the derivation has purchase (so not jurisdictional), the burden is discharged (so not burden-contested), the constitution- and framework-required completeness items are present (so not insufficiency), and this DRep holds only the general participant interest that does not disqualify (so not reflexive). The honest token is YES.
2.6 What the vote does not reach
A vote is a snapshot; the log is the trajectory; and trajectory over snapshot is the commitment this framework was built to keep. Four signals the reading surfaced belong in the trajectory log rather than in this vote, and I record them here so the YES is not mistaken for silence on them.
The self-referential justification. The proposal grounds its primary motivation in the Cardano Vision & Strategy framework and its pillar structure — and Se7en Labs members served as chair and vice-chair of the Product Committee that produced that framework, ratified by DRep supermajority in January 2026. Nothing about this is a violation, and the strategy is a legitimate object to cite. But the standard against which the proposal measures its own alignment is a standard the proposer helped author, and that is an asymmetry signal in the register of the narrative-accuracy and asymmetry tests — a reading about KPI-authoring concentration in the ecosystem, not about this action harming a commons relation. It is logged as a trajectory item about who writes the yardstick, not as a finding the ballot reaches.
The quantity vocabulary. As noted under the burden, the KPI framing performs the quantity substitution the framework exists to catch. It does not carry this proposal's justification, so it does not move the vote — but the fact that a proposal this cleanly commons-derived still reaches instinctively for MAU and transaction targets is itself a reading of the ecosystem's present vocabulary, and it belongs in the log as such.
The single-maintainer dependency. The proposal's own expected-value case is that a Daedalus user running an incompatible node at a hard fork cannot sync at all, where a lite-wallet user can switch backends — which is to say the ecosystem depends on a single maintainer for its only full-node desktop path. This is a real client-diversity and contestability concern (Right I decentralization, Right V contestability). The correct response is not to withhold funds from the one wallet that exists — that would increase the failure mode — but to fund the maintenance now and carry the client-diversity concern as a standing trajectory item, one the proposal itself gestures at through its ≥2-full-node-client framing and its scoped architecture assessment. The structural remedy is a second independent full-node wallet, and this grant is not it. This is the one trajectory item that does not rest on this framework alone: as recorded in §2.7, the external fiduciary read reaches the same soft spot from the capital-stewardship side, and the convergence of two independently grounded instruments on one concern is what raises it from a note to a candidate for a future proposal.
The decay note. Remediability here is R3 (the action lapses on its own terms) , but dependency-servicing grants are where renewal can quietly become the default. Each future cycle should remain a genuine per-action decision, not a renewal-by-inertia — and the client-diversity item above is what keeps the renewal a choice rather than a hostage situation. This is recorded now, at the opening cycle, precisely so the movement between sorts across renewals can be read as the finding it would be, rather than discovered late.
There is also a light governance-hygiene observation, short of any of the above. The proposal bundles existential maintenance with discretionary feature work (the CIP-30 connector, hardware-wallet support, the architecture assessment) into a single T&M ask. This is not the bundling fail-state the framework arrests on — that reading is reserved for heterogeneous structural or constitutional changes fused into one indivisible, correction-foreclosing action. Here the budget summary is transparent that the features ride nearly for free on a maintenance team that must exist regardless, and monthly milestone-gated disbursement makes the scope severable in practice. It clears, and is noted only for completeness.
2.7 Fiduciary verification (external instrument)
This DRep's framework reads the relational and structural question — whether a commons relation is harmed — and by design does not read the capital-allocation question: price, instrument fit, size-calibrated discipline, upfront exposure, and opportunity cost. That axis is an acknowledged gap in our coverage, and under our own field-fitness discipline an unexamined region raises vigilance rather than lowering it. We therefore ran the proposal through the DRep Treasury Rule Book v17 (credit: @InputEndorsers, drep1y2hlgh9600zjlt39dh54z7z8d65kahneck8yhh7ugmzc9as0xrzqd), which we have separately reviewed with positive findings, as a fiduciary gate — one that can lower a merits-YES but cannot raise a merits-NO.
The gate clears. Classified Large by nominal request, the proposal meets every universal hard gate and clears the Large-band threshold on the Public-Good and Civic-Service scorecard with the recurring-maintenance module active; upfront exposure is staged monthly against independently verified work, well inside the rulebook's risk-calibrated caps. We record the pass and its structure rather than a single number, consistent with both instruments' shared position that a score is evidence for judgment, not a substitute for it.
The verification's substantive contribution is a convergence. The score's thinnest categories — continuity and succession, and neutrality and decentralization — are where the rulebook's maintenance module flags bus-factor and hereditary-capture risk, and these are the same concern this rationale logged in §2.6 as the single-maintainer and client-diversity trajectory item, reached from capital-stewardship rather than rights-derivation. Two independent instruments flagging one soft spot strengthens the case for that trajectory item. Had the fiduciary read instead surfaced excess exposure, unbenchmarked pricing, or a capture structure, it would have been dispositive on the allocation question notwithstanding the relational pass; here it was not, because the structure is sound.
3.0 Conclusion
We are voting YES. The action sorts shallow — a discrete, sunsetting, forkable-public-good maintenance grant that lapses on its own terms and reverses by inaction. The private-surplus burden, which is the test that governs a for-profit drawing on the treasury, is discharged on claim structure rather than dodged. The good, stated as a relation, is the maintained existence of the only non-custodial full-node desktop path to the chain — settlement access and exit integrity for the cohort that has no alternative preserving those standards — and funding it moves those rights in the protective direction while harming no commons relation. The administration is contestable and milestone-gated, and the reversibility is clean. The fiduciary axis our framework does not itself read was checked against an external instrument and cleared, as a gate that could have lowered this vote and did not. On the merits, this is what a treasury withdrawal should look like.
The YES ratifies the action; it does not ratify the vocabulary the action is dressed in. This DRep carries forward four trajectory items — the self-referential yardstick, the quantity framing, the single-maintainer dependency, and the renewal-decay caution — none of which the ballot can reach, and one of which, client diversity, is a candidate for a future proposal rather than a future vote. That is the division of labor the framework keeps: the vote answers the action, and the log answers the trajectory. This vote answers the action, and the action is sound.
DRep ID: drep1yfaq8dsam...3nq50q
DRep Profile: DRep Talk Profile
The Coordination Commons - DRep reference
Stay in touch. X: https://x.com/styg50
- 1.0 Introduction
- Yes126.4K ₳No rationale
- Yes125.1K ₳No rationale
- Yes121.8K ₳Rationale
I am voting yes because Daedalus remains a foundational piece of Cardano's infrastructure. As the ecosystem's only full-node wallet, it provides users with a uniquely self-sovereign experience by validating the blockchain directly, without relying on third-party APIs or backend infrastructure. Maintaining that option strengthens Cardano's resilience, decentralization, and client diversity as the network continues to evolve.
This proposal aligns with my broader support for maintaining critical ecosystem infrastructure. As major protocol upgrades such as Leios, Peras, and future hard forks are introduced, ensuring that Daedalus remains secure, compatible, and fully operational is essential for the users who depend on it. I also support expanding hardware wallet compatibility, implementing CIP-30 to enable dApp interactions for full-node users, and continuing support for global communities through localization and ongoing maintenance.
While Daedalus serves a smaller user base than light wallets, its value cannot be measured solely by user count. It represents an important public good for the Cardano ecosystem: open-source, independently auditable infrastructure that advances decentralization and preserves user choice. For these reasons, I believe continued maintenance and improvement of Daedalus is a worthwhile investment in Cardano's long-term health and resilience.
- Yes107.4K ₳No rationale
- Yes98.4K ₳No rationale
- No90.6K ₳Rationale
Review Methodology Disclaimer [EN]
Due not only to the unusually high volume of Treasury Withdrawal Governance Actions and budget proposals submitted in April and May 2026, but also to the lack of meaningful incentives for DReps to perform proposal analysis work, it is not feasible to apply my full standard review framework and reporting template to every proposal.
My standard analysis process usually requires approximately four hours of work per Governance Action. During that process, I research the proposal, review supporting materials, compare different perspectives from DReps and other ecosystem participants, and weigh both positive and negative arguments before reaching a reasonably qualified decision. Even with the use of artificial intelligence to automate parts of the workflow and improve productivity, a responsible evaluation still requires substantial human review, judgment, and contextual understanding.
In addition, this work does not end with the vote itself. It also involves writing and publishing rationales, preparing reports or summaries, communicating the reasoning publicly, and socializing the analysis through public channels and social media. This creates a significant workload, especially when dozens of proposals must be reviewed in a short period.
At present, this work carries no clear financial incentive and only limited reputational incentive, despite requiring substantial time, attention, and accountability. In practice, it is not sustainable to dedicate near full-time effort over several weeks or months to this activity without any form of compensation or institutional support.
Since I have a clear standard for my work and do not want to lower the quality of my judgment, I will reduce the scope of my analysis where necessary rather than rush decisions or produce superficial rationales. This means prioritizing focused due diligence over exhaustive review.
Under these constraints, my methodology during this period will focus on identifying critical strategic, operational, governance, reputational, or execution-related risks that could materially compromise a proposal’s viability, accountability, or successful delivery. In practical terms, this means narrowing my research toward the most critical gaps that may make approval unjustifiable. Where such a serious risk is identified, I may use it as the basis for a rejection vote.
This approach also helps reduce review overload: proposals with clear and material gaps would likely require rework regardless, so voting against them when those gaps are significant can be a responsible way to preserve review capacity while maintaining minimum due diligence.
Examples of such high-priority concerns may include, but are not limited to:
- Serious delivery failures in previous funded proposals;
- Significant unresolved delays in ongoing work;
- Major reputational or accountability issues within the ecosystem;
- Lack of credible execution capacity;
- Structural governance or transparency concerns;
- Severe budgetary or coordination risks.
Where I do not have sufficient time for a deeper evaluation, and no significant red flags or imminent execution risks are identified, I may abstain rather than issue an underdeveloped approval or rejection rationale.
This does not mean that other dimensions of proposal quality are unimportant. It means that, under current constraints, I will prioritize a narrower but still responsible review scope that preserves minimum due diligence, avoids rushed decisions, and keeps the quality of my judgment at an acceptable standard.
Governance Action Review [EN]
1. Introduction
This Treasury Withdrawal requests 1,785,333 ADA to fund Daedalus Wallet Maintenance and Improvements for 2026–2027, delivered by Se7en Labs, Inc. Daedalus is Cardano’s only full-node desktop wallet, running an embedded Cardano node and deriving wallet and governance data directly from the blockchain without relying on third-party APIs or trusted backends.
The engagement follows a time-and-materials model over a 12-month period. Its scope includes protocol maintenance, node and wallet integration, hard fork readiness, security and dependency updates, build and release infrastructure, support for Windows, Linux, and macOS, Japanese localisation, user support, Keystone and Flex hardware wallet integration, implementation of a CIP-30 dApp connector, and a public architecture assessment. The proposal requires compatible releases at least two weeks before each mainnet hard fork and cryptographic signing of all official releases.
The budget allocates 1,666,667 ADA to team labor, 33,333 ADA to test hardware, 33,333 ADA to a financial audit, and 52,000 ADA to Intersect administration. Funds would be held and disbursed monthly through Intersect against verified work, with unused labor, hardware, and audit funds returned to the Treasury.
2. Governance Action Analysis
Positive aspects
The team has an extensive history within the Cardano ecosystem and brings together relevant technical experience. Its members have participated in different initiatives, received funding for several projects, especially through Project Catalyst, and are currently responsible for maintaining Daedalus under contract with IOG. The proposal itself presents relevant recent deliveries, including Mithril integration, implementation of the UTxO-HD/LSM backend, native Apple Silicon support, modernisation of the Nix infrastructure, and development of new release tools. These results constitute favorable evidence that the team possesses the technical skills necessary to work on a complex application such as Daedalus.
The proposal also presents metrics and acceptance criteria related to technical execution. These include the publication of compatible releases at least two weeks before each hard fork, cryptographic signing of all official releases, maintenance of builds across four platforms, support for Keystone and Flex hardware wallets, implementation of the CIP-30 connector, and publication of an architecture assessment by the third quarter of 2027. These targets allow a relevant portion of the deliveries to be verified.
The planned control mechanisms, including monthly disbursements against verified work, Intersect oversight, and the return of unused funds, reduce the risk of disbursement without execution.
Maintaining a full-node wallet remains important for decentralisation, user sovereignty, and the preservation of a form of blockchain access that does not depend on APIs or backends controlled by third parties. The institutional merit of Daedalus and the relevance of this wallet model are recognised.
Negative aspects
Because this is a team with extensive experience in Project Catalyst and other ecosystem initiatives, a higher standard of budget transparency and results measurement would reasonably be expected. The proposal requests 1,785,333 ADA, of which 1,666,667 ADA, approximately 93% of the total, is concentrated in a single team work line. This block covers protocol maintenance, hard fork preparation, cardano-node and cardano-wallet integration, build infrastructure, multiplatform support, hardware wallets, CIP-30 implementation, user support, and architectural assessment. However, the number of professionals, FTEs, functions, seniority levels, hourly or monthly rates, estimated number of hours, dedication of each member, and financial allocation among the different workstreams and milestones are not provided.
The absence of this granularity prevents an adequate evaluation of the budget’s coherence. It is not possible to determine the effective size of the funded team, how much would be allocated to recurring maintenance, how much the new features would cost, or whether the amounts are compatible with market references. The planned control mechanisms do not resolve the absence of the information required for dReps to assess in advance whether the requested price is reasonable.
The main deficiency in the metrics concerns impact and operational-quality KPIs. No project-specific targets have been established for user growth or retention, CIP-30 usage, transaction volume generated through the new integration, reduction in synchronisation time, resource consumption, adoption of the new hardware wallets, user satisfaction, or support performance.
Expressions such as resolving vulnerabilities “in a timely manner” and keeping support channels “actively monitored” also remain vague, without SLAs or quantitative criteria. The general Cardano 2030 targets mentioned in the proposal, including growth in active users and transactions, do not constitute specific commitments undertaken by the project.
Risks and concerns
The positive history does not eliminate concerns regarding execution capacity. Some previously funded proposals involving members of the team were cancelled before completion, while others experienced recurring schedule delays. Although only two proposals are currently recorded as delayed, the historical recurrence of delays constitutes a warning sign, particularly because team members were simultaneously involved in multiple proposals during previous periods.
It is not possible to state that parallel participation in several projects was the direct cause of the delays, but this overlap increases uncertainty regarding availability, prioritisation, and the capacity to complete the full set of planned deliveries within the 12-month period.
There is therefore an important difference between technical capacity and confidence in the execution of this specific proposal. The team demonstrates sufficient knowledge and experience to perform the work, but its history of delays and cancellations increases uncertainty regarding schedule completion. At the same time, the lack of granularity in the main budget block prevents determining whether the requested amount is proportional to the resources mobilised, while the absence of project-specific impact targets limits understanding of the expected benefits beyond completion of the technical deliverables.
The importance of the product should not function as a substitute for the diligence required for a Treasury Withdrawal.
3. Vote and Rationale
Vote: NO
Given these uncertainties, the vote is NO. This position does not represent rejection of Daedalus’s continuation or absolute doubt about the team’s technical capacity. It reflects the inability to adequately confirm the reasonableness of the budget, the expected impact, and the capacity to execute within the deadline based on the information currently available.
The team demonstrates sufficient knowledge and experience to perform the work, but the history of delays and cancellations increases uncertainty regarding schedule completion. At the same time, the lack of granularity in the main budget block prevents determining whether the requested amount is proportional to the resources mobilised, while the absence of project-specific impact targets limits understanding of the expected benefits beyond completion of the technical deliverables.
A future proposal containing a more granular budget, team composition, FTEs or rates, cost allocation by workstream, and specific KPIs with measurable targets may be reconsidered favorably.
4. Conclusion
Daedalus remains institutionally relevant to decentralisation and user sovereignty, and the team has the technical competence required for the work. However, the available information does not allow adequate confirmation of budget reasonableness, expected impact, or execution capacity within the proposed period. The vote is therefore NO.
Nota sobre metodologia e escopo de análise [PT]
Devido não apenas ao volume excepcionalmente alto de Treasury Withdrawal Governance Actions e propostas orçamentárias submetidas em abril e maio de 2026, mas também à falta de incentivos significativos para que DReps realizem o trabalho de análise de propostas, não é viável aplicar meu framework completo de revisão e meu template padrão de relatório a todas as propostas.
Meu processo padrão de análise normalmente exige aproximadamente quatro horas de trabalho por Governance Action. Durante esse processo, eu pesquiso a proposta, reviso materiais de suporte, comparo diferentes perspectivas de DReps e de outros participantes do ecossistema, e peso argumentos positivos e negativos antes de chegar a uma decisão razoavelmente qualificada. Mesmo com o uso de inteligência artificial para automatizar partes do fluxo de trabalho e aumentar a produtividade, uma avaliação responsável ainda exige revisão humana substancial, julgamento e entendimento contextual.
Além disso, esse trabalho não termina no voto em si. Ele também envolve escrever e publicar rationales, preparar relatórios ou resumos, comunicar publicamente a justificativa e socializar a análise por meio de canais públicos e mídias sociais. Isso cria uma carga de trabalho significativa, especialmente quando dezenas de propostas precisam ser avaliadas em um curto período.
Atualmente, esse trabalho não possui incentivo financeiro claro e oferece apenas incentivo reputacional limitado, apesar de exigir tempo, atenção e responsabilidade substanciais. Na prática, não é sustentável dedicar um esforço próximo de tempo integral durante várias semanas ou meses a essa atividade sem qualquer forma de compensação ou apoio institucional.
Como tenho um padrão claro para o meu trabalho e não quero reduzir a qualidade do meu julgamento, irei reduzir o escopo da minha análise quando necessário, em vez de tomar decisões apressadas ou produzir justificativas superficiais. Isso significa priorizar uma diligência focada em vez de uma revisão exaustiva.
Sob essas restrições, minha metodologia durante este período se concentrará em identificar riscos críticos estratégicos, operacionais, de governança, reputacionais ou relacionados à execução que possam comprometer materialmente a viabilidade, a accountability ou a entrega bem-sucedida de uma proposta. Na prática, isso significa concentrar minha pesquisa nos gaps mais críticos que possam tornar a aprovação injustificável. Quando um risco sério desse tipo for identificado, poderei usá-lo como base para um voto de rejeição.
Essa abordagem também ajuda a reduzir a sobrecarga de revisão: propostas com gaps claros e materiais provavelmente exigiriam retrabalho de qualquer forma, então votar contra elas quando esses gaps forem significativos pode ser uma forma responsável de preservar capacidade de análise enquanto se mantém uma diligência mínima.
Exemplos dessas preocupações de alta prioridade podem incluir, mas não se limitam a:
- Falhas graves de entrega em propostas anteriormente financiadas;
- Atrasos significativos e não resolvidos em trabalhos em andamento;
- Problemas graves de reputação ou accountability dentro do ecossistema;
- Falta de capacidade crível de execução;
- Preocupações estruturais de governança ou transparência;
- Riscos severos de orçamento ou coordenação.
Quando eu não tiver tempo suficiente para uma avaliação mais profunda, e nenhum alerta significativo ou risco iminente de execução for identificado, poderei me abster em vez de emitir uma justificativa de aprovação ou rejeição pouco desenvolvida.
Isso não significa que outras dimensões da qualidade de uma proposta não sejam importantes. Significa que, sob as restrições atuais, priorizarei um escopo de revisão mais estreito, mas ainda responsável, que preserve uma diligência mínima, evite decisões apressadas e mantenha a qualidade do meu julgamento em um padrão aceitável.
Revisão de Ação de Governança [PT]
1. Introdução
Esta Retirada do Tesouro solicita 1.785.333 ADA para financiar a manutenção e as melhorias da carteira Daedalus durante 2026–2027, sob execução da Se7en Labs, Inc. O Daedalus é a única carteira desktop full-node da Cardano, executando um nó Cardano incorporado e obtendo os dados da carteira e de governança diretamente da blockchain, sem depender de APIs de terceiros ou backends confiáveis.
A contratação segue um modelo de tempo e materiais durante um período de 12 meses. Seu escopo inclui manutenção do protocolo, integração do node e da carteira, preparação para hard forks, atualizações de segurança e dependências, infraestrutura de builds e releases, suporte a Windows, Linux e macOS, localização para o japonês, suporte aos usuários, integração das hardware wallets Keystone e Flex, implementação de um conector de dApps baseado no CIP-30 e uma avaliação arquitetural pública. A proposta exige releases compatíveis pelo menos duas semanas antes de cada hard fork da mainnet e a assinatura criptográfica de todos os releases oficiais.
O orçamento destina 1.666.667 ADA ao trabalho da equipe, 33.333 ADA a hardware para testes, 33.333 ADA a uma auditoria financeira e 52.000 ADA à administração da Intersect. Os recursos seriam mantidos e desembolsados mensalmente pela Intersect mediante trabalho verificado, com a devolução ao Tesouro dos valores não utilizados para trabalho, hardware e auditoria.
2. Análise da Ação de Governança
Aspectos positivos
O time possui uma trajetória extensa no ecossistema Cardano e reúne experiência técnica relevante. Seus membros participaram de diferentes iniciativas, receberam financiamento para diversos projetos, especialmente por meio do Project Catalyst, e atualmente já são responsáveis pela manutenção do Daedalus sob contrato com a IOG. A própria proposta apresenta entregas recentes relevantes, incluindo integração com Mithril, implementação do backend UTxO-HD/LSM, suporte nativo a Apple Silicon, modernização da infraestrutura Nix e desenvolvimento de novas ferramentas de release. Esses resultados constituem evidência favorável de que a equipe possui as competências técnicas necessárias para trabalhar em uma aplicação complexa como o Daedalus.
A proposta também apresenta métricas e critérios de aceitação relacionados à execução técnica. Entre eles estão a publicação de releases compatíveis pelo menos duas semanas antes de cada hard fork, a assinatura criptográfica de todos os releases oficiais, a manutenção dos builds em quatro plataformas, o suporte às hardware wallets Keystone e Flex, a implementação do conector CIP-30 e a publicação de uma avaliação arquitetural até o terceiro trimestre de 2027. Essas metas permitem verificar parte relevante das entregas.
Os mecanismos de controle previstos, como desembolsos mensais mediante trabalho verificado, supervisão da Intersect e devolução de valores não utilizados, reduzem o risco de desembolso sem execução.
A manutenção de uma carteira full-node permanece importante para a descentralização, a soberania dos usuários e a preservação de uma forma de acesso à blockchain que não dependa de APIs ou backends controlados por terceiros. O mérito institucional do Daedalus e a relevância desse modelo de carteira são reconhecidos.
Aspectos negativos
Por se tratar de uma equipe veterana do Project Catalyst e de outras iniciativas do ecossistema, seria razoável esperar um padrão mais elevado de transparência orçamentária e mensuração de resultados. A proposta solicita 1.785.333 ADA, dos quais 1.666.667 ADA, aproximadamente 93% do total, estão concentrados em uma única linha de trabalho da equipe. Esse bloco cobre manutenção do protocolo, preparação para hard forks, integração do cardano-node e cardano-wallet, infraestrutura de builds, suporte multiplataforma, hardware wallets, implementação do CIP-30, suporte aos usuários e avaliação arquitetural. Entretanto, não são informados o número de profissionais, FTEs, funções, senioridade, taxas horárias ou mensais, quantidade estimada de horas, dedicação de cada membro ou distribuição financeira entre os diferentes workstreams e milestones.
A ausência dessa granularidade impede uma avaliação adequada da coerência do orçamento. Não é possível determinar qual seria o tamanho efetivo da equipe financiada, quanto seria destinado à manutenção recorrente, quanto custariam as novas funcionalidades ou se os valores estão compatíveis com referências de mercado. Os mecanismos de controle previstos não resolvem a falta de informação necessária para que os dReps avaliem antecipadamente se o preço solicitado é razoável.
A deficiência está principalmente nos KPIs de impacto e qualidade operacional. Não foram estabelecidos alvos próprios para crescimento ou retenção de usuários, utilização do CIP-30, volume de transações geradas pela nova integração, redução do tempo de sincronização, consumo de recursos, adoção das novas hardware wallets, satisfação dos usuários ou desempenho do suporte.
Também permanecem vagas expressões como resolução de vulnerabilidades “em tempo hábil” e manutenção de canais de suporte “ativamente monitorados”, sem SLAs ou critérios quantitativos. As metas gerais do Cardano 2030 mencionadas na proposta, como crescimento de usuários ativos e transações, não constituem compromissos específicos assumidos pelo projeto.
Riscos e preocupações
Esse histórico positivo não elimina preocupações relacionadas à capacidade de execução. Algumas propostas anteriormente financiadas envolvendo membros do time foram canceladas antes da conclusão, enquanto outras apresentaram atrasos recorrentes em seus cronogramas. Embora apenas duas propostas estejam atualmente registradas como atrasadas, a recorrência histórica de atrasos constitui um sinal de alerta, especialmente considerando que, em períodos anteriores, membros do time estiveram envolvidos simultaneamente em múltiplas propostas.
Não é possível afirmar que a participação paralela em diversos projetos tenha sido a causa direta dos atrasos, mas essa sobreposição aumenta a incerteza sobre disponibilidade, priorização e capacidade de cumprir o conjunto de entregas previstas dentro do período de 12 meses.
Assim, existe uma diferença importante entre capacidade técnica e confiança na execução desta proposta específica. O time demonstra conhecimento e experiência suficientes para realizar o trabalho, mas o histórico de atrasos e cancelamentos aumenta a incerteza sobre o cumprimento do cronograma. Ao mesmo tempo, a falta de granularidade do principal bloco orçamentário impede determinar se o valor solicitado é proporcional aos recursos mobilizados, enquanto a ausência de metas próprias de impacto limita a compreensão dos benefícios esperados além da conclusão dos entregáveis técnicos.
A importância do produto não deve funcionar como substituto para a diligência exigida em uma retirada do Tesouro.
3. Voto e Justificativa
Voto: NÃO
Diante dessas incertezas, o voto será NÃO. Essa posição não representa rejeição à continuidade do Daedalus nem dúvida absoluta sobre a capacidade técnica da equipe. Reflete a impossibilidade de confirmar adequadamente a razoabilidade do orçamento, o impacto esperado e a capacidade de execução dentro do prazo com as informações atualmente disponíveis.
O time demonstra conhecimento e experiência suficientes para realizar o trabalho, mas o histórico de atrasos e cancelamentos aumenta a incerteza sobre o cumprimento do cronograma. Ao mesmo tempo, a falta de granularidade do principal bloco orçamentário impede determinar se o valor solicitado é proporcional aos recursos mobilizados, enquanto a ausência de metas próprias de impacto limita a compreensão dos benefícios esperados além da conclusão dos entregáveis técnicos.
Uma proposta futura contendo orçamento mais granular, composição da equipe, FTEs ou taxas, distribuição de custos por workstream e KPIs específicos com alvos mensuráveis poderá ser reavaliada favoravelmente.
4. Conclusão
O Daedalus permanece institucionalmente relevante para a descentralização e a soberania dos usuários, e o time possui a competência técnica necessária para o trabalho. Entretanto, as informações disponíveis não permitem confirmar adequadamente a razoabilidade do orçamento, o impacto esperado ou a capacidade de execução dentro do período proposto. O voto, portanto, é NÃO.
- No86.8K ₳No rationale
- Yes65.9K ₳No rationale
- Yes63K ₳No rationale
- Yes62.6K ₳No rationale
- No56K ₳No rationale
- No50.9K ₳No rationale
- Yes45.3K ₳No rationale
- Yes26.7K ₳Rationale
Yes, make Daedalus useful.
- No19.4K ₳No rationale
- Yes8.2K ₳No rationale
- Yes6.8K ₳No rationale
- Yes5.5K ₳No rationale
- No4.6K ₳No rationale
- Yes2.5K ₳No rationale
- NoChanged292 ₳History
Earlier votes
Yes1mo agoSuperseded
No1mo agoSuperseded