Scalus 2026: Maintenance, Dijkstra Readiness, Interoperability & Application Runtime

System4mo ago2 posts

144 DReps voted · 54 with a rationale · 2 changed their vote · 1 re-voted unchanged

Open a row to read the rationale.

Changed votes: 2 to yes, together voting with 4.9M ₳ of voting power.

Voting concentration

7 of 144 DReps cast half of the voted power.

Largest voter 13.8%, top 5 combined 44.3% of 4.2B ₳ voted.

The 7 largest voters together held as much voting power as the 67.0% threshold required in yes votes.

  • Yes3.9M ₳Rationale

    [Portuguese]
    Optamos por votar "SIM" nesta ação de governança "Scalus 2026: Maintenance, Dijkstra Readiness, Interoperability & Application Runtime" (gov_action1xg6...qa63yc), pois entendemos que a proposta assegura a continuidade e a evolução de uma infraestrutura já utilizada por diversos projetos e ferramentas do ecossistema Cardano. Além da manutenção da plataforma, a iniciativa prepara o Scalus para o hard fork Dijkstra e amplia sua interoperabilidade com os ecossistemas JVM e JavaScript/TypeScript, fortalecendo a base tecnológica para o desenvolvimento de aplicações descentralizadas. O valor solicitado, de aproximadamente ₳2,46 milhões para um período de nove meses, é significativamente inferior ao da proposta anteriormente apresentada e nos parece compatível com o escopo previsto, oferecendo uma boa relação entre custo e benefício. Também avaliamos positivamente a experiência da equipe e o potencial impacto da iniciativa para desenvolvedores e projetos que dependem dessa infraestrutura. Além disso, consideramos adequados os mecanismos de governança, controle e transparência previstos, incluindo pagamentos condicionados ao cumprimento de marcos, contratos de custódia auditados, supervisão por um conselho independente, auditoria técnica externa, relatórios trimestrais e registro público das movimentações financeiras. Esses elementos proporcionam maior segurança na utilização dos recursos da Tesouraria e permitem um acompanhamento transparente da execução do projeto.
    [English]
    We chose to vote "YES" on this governance action "Scalus 2026: Maintenance, Dijkstra Readiness, Interoperability & Application Runtime" (gov_action1xg6...qa63yc), because we believe the proposal ensures the continued maintenance and evolution of infrastructure already used by multiple projects and tools across the Cardano ecosystem. Beyond maintaining the platform, the initiative prepares Scalus for the Dijkstra hard fork while expanding interoperability with the JVM and JavaScript/TypeScript ecosystems, strengthening the technological foundation for decentralized application development. The requested budget of approximately ₳2.46 million over a nine-month period is significantly lower than the previous proposal and, in our view, represents a reasonable cost-benefit balance given the scope of work, the team's experience, and the potential impact on developers and ecosystem projects. We also view the proposal’s governance, oversight, and transparency mechanisms positively. These include milestone-based payments, audited escrow contracts, oversight by an independent council, external technical audits, quarterly reporting, and public disclosure of financial transactions. Together, these measures provide greater confidence in the responsible use of Treasury resources while enabling transparent monitoring of project execution.

  • Yes78.9M ₳Rationale

    I am voting YES to fund Scalus because this is a textbook example of how builders should engage with governance.

    A PDF version of this rationale is also made available.

    I am voting YES to fund Scalus because this is a textbook example of how builders should engage with governance.
    When DReps pushed back on their previous 8.5 million ADA ask, the team listened, rescoped the project, and reduced their budget by 71%.
    Maintaining essential JVM and JS/TS developer tooling ahead of the Dijkstra hard fork is exactly the type of foundational infrastructure the treasury should support.
    This is a highly strategic, fiscally responsible spend that directly empowers builders across the Cardano ecosystem.

  • Yes55.4K ₳Rationale

    I vote YES for this proposal

  • Yes10.2M ₳No rationale
  • No3.4M ₳Rationale

    I have reached the limit I am willing to spend on research-related products for this year's NCL. I don't see how this spend will have any financial benefit for Cardano.

  • Abstain35.1M ₳Rationale

    Vote: Abstain. This action requests 2,464,844 ADA over nine months for Scalus maintenance, Dijkstra readiness, interoperability, and a scoped application runtime.

    A PDF version of this rationale is also made available.

    Scalus is established open-source Cardano infrastructure with a credible delivery record. Its components are used directly and indirectly by several Cardano projects and development tools.
    The revised proposal responds seriously to earlier DRep concerns. The requested amount has been reduced by approximately 71 percent, the duration has been shortened, the contingency has been removed, and several broader workstreams are no longer included.
    Maintenance and Dijkstra hard-fork readiness are reasonable uses of treasury funding. Existing projects should not lose compatibility because shared infrastructure falls behind the protocol. The uncertainty is the decision to combine that maintenance with interoperability expansion and a new application-runtime step.
    The proposal does not yet show enough external demand for the runtime work to make it a clear treasury priority. A No vote would discount the value already delivered and the importance of compatibility work. A Yes vote would endorse an expansion whose adoption case remains unsettled.
    I will not oppose the continuation of Scalus, but I cannot give the complete scope an affirmative mandate.
    I vote Abstain.

  • Yes228.7M ₳Rationale

    They listened and the new proposal is much leaner. Easy YES now.

  • Abstain213K ₳Rationale

    Abstain due to personal involvement

  • Yes4.3M ₳No rationale
  • Yes73.3M ₳Rationale

    I'm voting Yes on the Scalus 2026 proposal.

    Scalus's script evaluation and node emulator components are already embedded in MeshJS, Lucid Evolution, Evolution SDK, and Cardano Client Lib. If that layer isn't maintained through the Dijkstra hard fork, which introduces Plutus V4 and nested transactions, the tools that rely on it and the teams building on those tools are all affected.

    This proposal cuts the ask by 71% and removes the L1 node, L2 integration, and formal verification from scope, focusing instead on maintenance, hard fork readiness, and interoperability. It's designed around 2.25 FTE with no contingency, and comes with SundaeSwap escrow, an independent oversight board, and third-party assurance.

    That said, the application runtime is a new expansion, different in nature from maintenance. I think that part needs to prove its necessity through actual adoption results in any future request.

  • No474.2K ₳Rationale

    A PDF version of this rationale is also made available.

  • Yes30.8M ₳No rationale
  • Yes142.7K ₳Rationale

    Scalus 2026 — Treasury Withdrawal (₳2,464,844) — Voting Rationale

    Governance Voting Rationale
    GAID gov_action1xg6...qa63yc
    Title Scalus 2026: Maintenance, Dijkstra Readiness, Interoperability & Application Runtime (Lantr Engineering)
    Type of GA Treasury Withdrawals
    Date submitted Epoch 640 (Jun 29, 2026)
    Expiration Date Epoch 647 (Aug 2, 2026)

    Contents

    1.0 Introduction {#1.0-introduction}

    1.1 Summary {#1.1-summary}

    We are voting YES on the Scalus 2026 treasury withdrawal — ₳2,464,844 over nine months to Lantr Engineering, to maintain the Scalus development platform, ready it for the Dijkstra hard fork, deepen its reuse across the JVM and JavaScript stacks, and ship a scoped first step toward an application runtime.

    The reason is straightforward, and its being straightforward is the point. Scalus is open-source infrastructure the ecosystem already depends on — directly, in the protocols built on it, and indirectly, through its components embedded in tooling many teams use every day (MeshJS, Lucid Evolution, Evolution SDK, the Cardano Client Lib, Yaci). Keeping a shared, freely forkable good like that maintained and current through a protocol transition is close to the clearest case there is for what the treasury exists to fund.

    There is a test this DRep applies to any treasury request from a for-profit entity, and it is worth naming because Lantr is one: a for-profit drawing treasury funds has to show its claim rests on maintaining something the whole ecosystem depends on and can freely use, not on growth it projects while keeping the upside. Scalus meets that test plainly — the good is a non-rival public asset under an open licence, and the ask funds the effort to maintain and extend it, with no private-surplus mechanism attached. The construction around the money is sound, the amount is modest, the exposure is staged, and the whole thing reverses simply by not being renewed. This is a proposal with little that could go wrong unseen, and that is exactly what a low-scrutiny reading means. The one thing worth carrying forward is not an objection but a note for future cycles, set out at the end.

    1.2 Description of Governance Action {#1.2-description-of-governance-action}

    This Treasury Withdrawals action requests ₳2,464,844 (about $394,375 at the proposal's $0.16/ADA reference rate) for nine months of milestone-based work, July 2026 through March 2027, with no contingency. Lantr Engineering is the sole vendor. The work spans three lines beyond continuous maintenance: readiness for the Dijkstra hard fork (Plutus V4, nested transactions, accounts, and the associated ledger and tooling changes), interoperability improvements across the JVM and JS/TS ecosystems, and a bounded first release of an application runtime, validated through reference applications and early users.

    The funds are held and released through the audited SundaeSwap treasury-contracts framework, with milestone-based vesting, an independent oversight board (members from Blink Labs, the Cardano Foundation, and IOG) that co-signs disbursements and can pause or halt funding, third-party technical assurance from No.Witness Labs, and an independent financial audit. Escrowed funds are set to auto-abstain in governance and cannot be delegated to a stake pool, and anything unspent at expiry sweeps back to the treasury automatically. The proposal is a reduced resubmission of an earlier, larger Scalus proposal (₳8.5M over twelve months), rescoped to answer the scale concerns raised in that vote. It discloses prior funding — earlier Catalyst awards and a 2025 treasury grant of ₳657,692 — and sits within the current 350M net-change limit at submission.

    2.0 Discussion {#2.0-discussion}

    2.1 The question a for-profit treasury request has to answer {#2.1-the-question-a-for-profit-treasury-request-has-to-answer}

    The treasury is a shared resource, held in trust for the whole ecosystem, and a for-profit company asking to draw from it raises a fair question about the shape of the claim. This DRep states that question as a standing test, published so it is applied the same way every time: the question is not whether the recipient is a company — it is whether the thing being funded is the maintenance of something the ecosystem collectively depends on and can freely use, or the funding of a private venture that keeps its own upside. The first is a claim rooted in the commons. The second is not, and arguments from projected growth do not convert one into the other.

    Scalus discharges that test about as cleanly as a for-profit request can. The good is open-source under Apache 2.0 — non-rival, freely usable, and forkable, so nothing here is enclosed or made exclusive. Its degradation would be felt across the ecosystem precisely because so much tooling embeds its components, which is the mark of a genuine commons relation rather than a private one. And the ask carries no private-surplus instrument: no performance fee, no equity, no revenue share. The funding buys engineering effort, priced as effort, against a public asset the ecosystem keeps regardless of how Lantr fares commercially. That the same team also builds commercial products on top of Scalus does not change this — the platform itself remains the shared, forkable good, and the treasury is paying to maintain that good, not to underwrite the products. This is worth saying with some care because the contrast is real: a request that asked the treasury to fund growth while routing the resulting upside to a private party would be a different proposal facing a much harder question. This one does not.

    2.2 Why this reads as a low-scrutiny proposal — and why that is the right reading {#2.2-why-this-reads-as-a-low-scrutiny-proposal}

    This DRep sorts every action before reading its merits, to decide how much scrutiny it earns — the goal being to spend the most attention where the most could go wrong without announcing itself. Scalus earns a light reading, and it is worth being explicit that "light" is a description of risk surface, not of quality. A few things account for it. This is a single, self-contained decision, not one half of a pair of actions arranged so the real commitment lands where scrutiny is lowest — a maneuver this DRep watches for, and which is simply absent here. It tunes a spend within the existing rules rather than changing any structural constraint or installing a standing default. If it proves a poor use of funds in eighteen months, reversing it costs nothing more than declining to renew: the term ends on its own, unspent funds return automatically, and because the code is open-source and forkable, the ecosystem keeps everything already built and no party is left holding leverage against the reversal. And if the work degraded, the degradation would show up loudly through ordinary channels — public repositories, releases, download counts, conformance tests, third-party assurance, and the many dependent projects that would notice breakage first.

    None of those readings requires trust in the proposer; they are properties of the action's structure, and they are the reason this proposal does not need the deeper machinery this DRep reserves for actions that can fail quietly or irreversibly. Most sound proposals read this way. A framework that manufactured suspicion here would be miscalibrated, and part of what this reading is for is to say plainly when there is little to contest.

    2.3 The construction, and the money it asks for {#2.3-the-construction-and-the-money-it-asks-for}

    This DRep's framework reads relations rather than pricing allocations, so the question of whether ₳2,464,844 is well spent — the right amount, the right instrument, a good use of finite treasury against everything else it could fund — is read through a separate capital-stewardship instrument maintained by a peer DRep. For open-source infrastructure, that instrument treats the continuity of the public asset itself as the principal return to the treasury, which is the right frame for what this is.

    On that reading the proposal is in good order. The amount is modest — roughly on par, in dollar terms, with the single 2025 grant, and a substantial reduction from the earlier version. The exposure is staged rather than released at once: milestone vesting, a board that must co-sign disbursements and any one of whose members can pause a milestone, and an automatic sweep of anything unused. The delivery record is real — every milestone of the 2025 cycle was delivered on time, with additional work beyond the committed scope. The ADA pricing is honest: the $0.16 reference rate sits slightly below the current market price of around $0.17, and the proposal commits to hedging into stable assets on receipt, a direct and candid response to the roughly fifty-percent purchasing-power loss the 2025 grant suffered as ADA fell during that delivery window. Most importantly for a capital-stewardship read, there is no private-capture structure for the instrument to flag — no upside routed away from the commons. The allocation reading concurs with the vote; it finds nothing that should lower it.

    2.4 What the vote does not reach {#2.4-what-the-vote-does-not-reach}

    A few observations belong in this DRep's longer-run record rather than in the vote, because they are about trajectory across cycles rather than about this action, which is sound.

    The first concerns the application runtime. It is the one workstream that reaches beyond maintaining what already exists toward building something new, and while it is bounded, open-source, and validated with real teams this cycle, it is the part most worth watching over time. An application runtime that the ecosystem comes to build on could, in a few cycles, become infrastructure whose health the ecosystem reads through — at which point a future Scalus proposal would earn a deeper look than this one does. That is a note for the next reading, not a reservation on this one.

    The second is about recurring funding generally. This is the second Scalus treasury withdrawal in twenty-four months, and a maintainer the ecosystem depends on can, over enough cycles, drift from being funded because it earns each round toward being funded because too much now depends on it to stop. The thing that keeps that exit genuinely open is the forkability of the code, and the honest discipline is to re-read at each renewal whether that exit is still real. Today it plainly is.

    The last is not about Scalus at all. The proposal's own retrospective describes a treasury process where a bundled budgeting path stretched five to six months from proposal to first payment, offered no protection against ADA's decline, and carried standing governance risk in the bundling itself — enough that this proposer, like others before it, chose to submit independently and on-chain instead. That teams capable of maintaining critical infrastructure are routing around the coordinated process is a signal about the process worth tracking on its own, separately from any single vote.

    3.0 Conclusion {#3.0-conclusion}

    We vote YES. Scalus is public infrastructure the ecosystem already relies on, the request maintains and extends it as a freely forkable common good, and the for-profit test that a treasury request of this kind must meet is met plainly — the claim rests on a maintained commons relation, not on a private surplus. The construction is sound, the amount modest, the exposure staged, the delivery record demonstrated, and the whole action reverses by simply not being renewed.

    The framework's work here was not to find fault but to confirm that the burden is discharged and the risk surface is genuinely shallow, and to say so without manufacturing scrutiny the action does not warrant. The one thing carried forward is a matter for future cycles rather than this vote: to re-read, as the runtime grows and the funding recurs, whether the ecosystem's exit from this dependency stays as open as the code's licence currently keeps it.

    Thank you for reading this rationale and for supporting it with your delegation. And the work continues...

    References / Sources {#references-sources}

    The following background may help a reader new to this DRep's approach:

    • The evaluation framework — this DRep's standing method of judging governance actions by their long-run trajectory and their risk of failing unseen, rather than by a single snapshot, first set out in the rationale on the Cardano Constitution. Coordination Commons
    • The claim a for-profit makes on the shared treasury — the published test distinguishing the maintenance of a non-rival, forkable good the ecosystem depends on from the funding of a private surplus. Private-Surplus Burden
    • The DRep Treasury Rule Book — the capital-stewardship instrument, maintained by a peer DRep, used here as the allocation check. DREP Treasury Rulebook v17

    DRep ID: drep1yfaq8dsam...3nq50q

    Stay in touch!
    X: https://x.com/styg50


  • Yes0 ₳No rationale
  • Yes29M ₳Rationale

    Scalus maintains a suite of heavily-used Cardano tools and pushes the frontier of innovation with things like Gummiworm. The team is well respected and the ask is reasonable. This is an easy YES vote for me.

  • Abstain12.5M ₳Rationale

    We recognize the importance of maintaining developer infrastructure, ensuring readiness for the Dijkstra era, and improving interoperability within the Cardano ecosystem. We appreciate the team's efforts to address concerns raised in previous discussions by significantly reducing the scope and budget of the proposal and by placing greater emphasis on maintenance and ecosystem support. We also acknowledge the value that Scalus and its associated tooling may provide to developers building on Cardano.

    However, we have decided to abstain because several critical questions remain insufficiently addressed, making it difficult to confidently assess the proposal's long-term impact and value to the ecosystem. While the proposal provides detailed technical milestones, it does not explicitly demonstrate the extent to which the wider ecosystem depends on Scalus or whether all proposed workstreams, particularly the application runtime represents the most effective use of treasury resources at this time.

    First, the proposal does not clearly establish how much of the current Cardano ecosystem would be materially affected if Scalus maintenance and development were to cease. Understanding the degree of dependency across projects, applications, and developer workflows is essential in determining whether the requested funding addresses critical infrastructure needs.

    Second, although the proposal highlights several integrations and downstream tools, it does not provide sufficient evidence regarding the number of developers and projects that actively use Scalus directly, nor does it identify external teams that have explicitly committed to adopting the proposed application runtime. Without clear indicators of demand and adoption, it is difficult to evaluate the necessity of this component.

    Third, the proposal does not define objective success criteria for the application-runtime workstream beyond activity-based indicators such as downloads and reference implementations. We would like to understand how the practical ecosystem impact of this investment will be measured and independently verified.

    Fourth, given that a significant portion of the budget supports experimental runtime functionality, the proposal does not adequately justify why treasury funding should extend beyond maintenance, Dijkstra readiness, and interoperability into areas where ecosystem demand remains uncertain.

    Finally, the proposal lacks a clear sustainability strategy beyond the proposed funding period. We believe it is important to understand how ongoing maintenance and future development will be supported without creating a recurring dependence on treasury funding.

  • Yes817.5K ₳No rationale
  • Yes16.4M ₳Rationale

    Vote: YES

    This is a Treasury Withdrawal, "Scalus 2026: Maintenance, Dijkstra Readiness, Interoperability & Application Runtime" (gov_action1xg6...qa63yc), submitted June 29, 2026 with voting closing August 2, 2026. Lantr Engineering requests ₳2,464,844 (approximately $394,375 at the $0.16/ADA reference rate) over nine months, July 2026 through March 2027, to maintain the Scalus toolchain — a JVM-native development stack for writing, evaluating, testing, and deploying Cardano smart contracts — keep it compatible with the Dijkstra hard fork including Plutus V4 and new builtins, improve Java/Kotlin and JavaScript/TypeScript interoperability, and deliver a scoped first application runtime. No ADA burning is involved.

    This is a resubmission that took DRep feedback seriously rather than repackaging it. The ask fell from ₳8,503,000 over twelve months to ₳2,464,844 over nine — a 71% reduction — with the team cut from 8.25 to 2.25 FTE, the standalone L1 node and L2 integration removed from scope, the formal verification track dropped, the contingency buffer eliminated entirely, and pricing set at a conservative $0.16/ADA. Few proposals in this cycle have responded to rejection by actually shrinking. The accountability apparatus matches the strongest structures Dracula DAO has seen: funds held in audited SundaeSwap escrow contracts, disbursements requiring approval from a three-member independent oversight board drawn from Blink Labs, the Cardano Foundation, and IOG, quarterly technical review by No.Witness Labs, public quarterly reports and transaction journals, and automatic return of unused funds to the treasury. Lantr's disclosed track record supports the request: ₳328,000 across two Catalyst F11 projects and ₳657,692 from the 2025 Treasury, both fully received with all milestones delivered. The tooling has real users — Scalus is already a dependency of Gummiworm L2, the Bifrost bridge, SugarRush DEX, Vela stablecoin, and DID/DIDComm work — so the maintenance milestone protects infrastructure the ecosystem already depends on rather than speculating on adoption that has not happened.

    The structural objection still applies. This is priced as 2.25 FTE of a named team's time for nine months, not as a grant paid against completed features, and there was no competitive bidding — Scalus is Lantr's own product, and the treasury is funding its upkeep. Dracula DAO names that gap plainly. The application runtime component is also the weakest part of the request: unlike maintenance and hard-fork compatibility, it is new scope whose demand is asserted rather than demonstrated, and it is the piece most likely to consume budget without producing something the ecosystem misses if it never ships. DRep sentiment is currently against, at roughly ₳1.97B no to ₳1.16B yes.

    Dracula DAO votes YES. Developer tooling that keeps working through a hard fork is unglamorous, foundational, long-term infrastructure — exactly the category this DREP exists to favor over tactical spending. If Scalus breaks at Dijkstra, every project built on it breaks with it, and the cost of that failure lands on builders who made no such request of the treasury. At ₳2.46M this is one of the smallest asks of the cycle, roughly a fifth of the Bifrost Phase 1 request and under half of the Hydra v2 hardening grant, for work with immediate and verifiable consequences. Money moves only when an independent board with no stake in the outcome signs off against a defined quarterly milestone, and undelivered funds return automatically. That is not the competitive completion-grant model Dracula DAO would prefer, but it is honest gating on real deliverables from a team that has delivered before.

    Dracula DAO will judge any 2027 continuation on whether the runtime component found genuine users and whether the Dijkstra compatibility work shipped on schedule. Maintenance funding earns renewal by keeping things working; new scope earns it by being adopted.

  • Abstain31.9K ₳No rationale
  • Yes150.5M ₳Rationale

    The Cardano Foundation votes YES. Scalus components are already embedded in tooling the ecosystem depends on, and this reduced, unbundled resubmission is proportionate to keeping that infrastructure maintained through the Dijkstra hard fork.

    A PDF version of this rationale is also made available.

    We recognise Lantr Engineering as a capable team with three years of continuous delivery behind Scalus. Having thoroughly assessed this governance action, our decision is driven by the following factors:

    1. A Proportionate Resubmission: The ask is 2,464,844 ada over nine months at a $0.16/ADA reference rate with no contingency, reduced from 8,503,000 ada over twelve months and from 8.25 to 2.25 FTE. The standalone JVM L1 node, full L2 integration, and the broad formal verification track have been removed from scope. This responds directly to the concerns raised on the previous submission rather than restating the same case at a lower price.
    2. Maintenance of a Dependency: Scalus's script evaluation, cost calculation, and in-memory node emulator are embedded in MeshJS, Lucid Evolution, Evolution SDK, Cardano Client Lib, and Yaci Dev Kit. Many teams therefore depend on these components without ever choosing Scalus. Our review found Scalus to be among the smart contract ecosystems on Cardano showing measurable adoption. Dijkstra introduces Plutus V4, new builtins, and updated cost models; if these components fall behind, the consequences reach teams who never selected this platform.
    3. Delivery Record: Lantr's 2025 treasury withdrawal of 657,692 ada is complete, with the final milestone delivered and publicly reported, and a retrospective published alongside this proposal. We view delivery against a prior withdrawal as material evidence of execution capability.

    To ensure transparency, we note that Matthias Benkort of the Cardano Foundation is named as a member of the proposal's independent oversight board.

    The Cardano Foundation votes YES. We commend Lantr Engineering for returning with a leaner, unbundled proposal and for the transparency of its 2025 retrospective, and we look forward to Scalus and the tooling built on it remaining current through the Dijkstra transition.

    ---

    > **_NOTE on 'Internal Voting':_**

    > The fields _constitutional_ and _unconstitutional_ below reflect the CF governance teams' individual opinions whether they are _for_ or _against_ the proposal. Reason for this inconsistency is, that CIP-136 is at the moment only applicable to CC rationales, but we want to record the internal opinions of our DRep assessment transparently as well.

  • Yes215.3M ₳No rationale
  • Yes0 ₳Rationale

    本提案に賛成します。Scalusは、CardanoにおけるJVMおよびJavaScriptエコシステム向けの重要な開発基盤であり、既存ライブラリの保守、Dijkstra対応準備、相互運用性の向上は、開発者エコシステム全体にとって価値があると考えます。また、本提案は前回からスコープと予算を大幅に見直し、保守やDijkstra対応準備を中心とした現実的な内容となっています。ガバナンスや監査体制も明確に示されており、要求されているTreasury資金は妥当であると考えます。そのため、私はこの提案に賛成します。\n\nI vote Yes on this proposal. Scalus is an important development platform for the JVM and JavaScript ecosystems within Cardano, and I believe that maintaining its existing libraries, preparing for Dijkstra, and improving interoperability will provide meaningful value to the broader developer ecosystem. This proposal has also significantly refined its scope and reduced its budget compared to the previous version, resulting in a practical proposal focused on maintenance and Dijkstra readiness. In addition, the governance and oversight framework is clearly defined, and I believe the requested Treasury funding is justified. Therefore, I vote Yes on this proposal.

  • Yes1.1M ₳No rationale
  • Yes184.8K ₳Rationale

    Voting YES. A strong example of addressing DRep feedback — budget cut 71% and refocused on core priorities like Dijkstra hard-fork readiness. Funds are held in an audited escrow with an independent oversight board and automatic sweep of unused funds back to the Treasury, giving solid protection on both disbursement and refund.

  • Yes614.1K ₳Rationale

    Vote Yes on Scalus 2026. Funds developer infrastructure and Dijkstra readiness for a platform used by Gummiworm, Bifrost, SugarRush, and embedded in MeshJS and Lucid Evolution. Ask reduced 71 percent from prior proposal. Strong accountability with independent oversight.

    A PDF version of this rationale is also made available.

    I am voting Yes on this proposal. Scalus is proven developer infrastructure with components embedded in tools that thousands of Cardano developers use every day. The 2.46 million ADA ask is proportionate and represents a 71 percent reduction from the prior proposal that DReps found too large. This shows the team listened to feedback and adjusted accordingly.

    The maintenance and Dijkstra readiness work alone justifies the ask. Without it, embedded Scalus components in MeshJS, Lucid Evolution, and other tools risk becoming incompatible with the next protocol version. That would create friction for developers across the ecosystem.

    I acknowledge Lantr Engineering has multiple active Treasury requests including Bifrost. I evaluated each proposal independently on its merits. Scalus stands on its own as a sound continuation of proven work with a reasonable price tag.

  • Yes32M ₳Rationale

    This proposal provides essential maintenance and Dijkstra hard‑fork readiness for Scalus, a public‑good infrastructure already embedded in major Cardano developer tools such as MeshJS, Lucid, Evolution SDK, Yaci, and Cardano Client Lib. The scope and budget have been significantly reduced in direct response to prior DRep concerns, focusing strictly on maintenance, interoperability, and hard‑fork alignment. Given the ecosystem-wide dependency on Scalus and the proven delivery record of the team, continued support is necessary to preserve developer experience and platform safety. The reduced budget is appropriate for the narrowed scope. I vote Yes.

  • Abstain83.3M ₳No rationale
  • Abstain347.8M ₳No rationale
  • Yes529.5K ₳No rationale
  • Yes181.4K ₳No rationale
  • Yes63.3K ₳No rationale
  • Yes229.7M ₳No rationale
  • Abstain29.1M ₳Rationale

    As this is a technical matter beyond my expertise, I am not comfortable voting either for or against the proposal. I will abstain.

  • Yes960.2K ₳No rationale
  • Abstain27K ₳Rationale

    Not going to pass

  • Yes202.9K ₳No rationale
  • Abstain170.3M ₳No rationale
  • No1M ₳No rationale
  • No57.9K ₳No rationale
  • Yes490.7K ₳No rationale
  • Yes146.3K ₳No rationale
  • Yes120.1M ₳Rationale

    SIPO DRep votes YES on the treasury withdrawal "Scalus 2026: Maintenance, Dijkstra Readiness, Interoperability & Application Runtime" (2,464,844 ada).

    This is the resubmission of a proposal SIPO supported at 8,503,000 ada and the wider DRep body rejected as too large relative to demonstrated demand and treasury capacity. The proposers answered that directly: the request is down about 71%, the term is nine months rather than twelve, staffing is 2.25 FTE rather than 8.25, contingency is 0% rather than 10%, and the production standalone L1 node, full L2 integration, advanced devnets, and broad formal verification have been deferred to a later phase. The remaining scope is three goals: maintain the existing Scalus infrastructure and make it ready for the Dijkstra hard fork; deepen interoperability for JVM and JavaScript/TypeScript developers; and deliver a first, limited application runtime. The on-chain recipient is a script credential at stake17xzhu4tdpl4gdsupfmn3yjlngt2f3mjes3v6wwg9yd767ps8k5qvl.

    SIPO supports this. It is the public-good and builder-infrastructure category SIPO backs: essentially all spend is engineering, maintenance, and developer enablement, with no brand-marketing component, and the funds return to a builder inside the ecosystem rather than leaving it. Scalus is a live dependency, and maintaining what already exists across a hard fork is not optional work. Bringing Java, Kotlin, and TypeScript developers onto Cardano through the toolchains they already use is among the cheaper ways to widen the builder base. The oversight board carries independent technical credibility from IOG, the Cardano Foundation, and Blink Labs. Treasury funds sit under an escrow that enforces auto-abstain DRep delegation and no stake pool delegation, so they cannot convert into governance power or staking rewards. Development is verifiably active.

    SIPO also supports it because the iteration deserves to be answered. The proposers asked DReps whether the scale was wrong, were told that it was, and returned smaller rather than repackaging the same request. If governance is to produce better proposals rather than merely rejected ones, that behaviour needs to be met with support.

    Two notes on the numbers. The $0.16 reference price now sits essentially at market - ada trades at about $0.1646 - so the ada quantity is not inflated, though it no longer carries the margin in the Treasury's favour that it did when the resubmission was filed. With contingency at 0%, further ada weakness is absorbed by the proposers rather than the Treasury; SIPO expects scope to be held rather than a top-up request, and would treat a later top-up as a material change of terms. SIPO also expects Dijkstra readiness to land ahead of the hard fork rather than after it, and notes that Lantr Engineering is also delivering Bifrost Phase 1 in this same batch, so reporting should evidence that the two are separately staffed. This vote is SIPO DRep's recorded position.


    SIPO DRep は、トレジャリー引き出し提案「Scalus 2026: Maintenance, Dijkstra Readiness, Interoperability & Application Runtime」(2,464,844 ADA)に賛成(YES)を投じます。

    本件は、SIPO が 8,503,000 ADA の時点で支持し、DRep 全体としては実証された需要とトレジャリー容量に対して規模が大きすぎるとして否決された提案の、再提出版です。提案者はその論点に正面から応答しました。要求額は約 71% 減、期間は 12 ヶ月から 9 ヶ月、人員は 8.25 FTE から 2.25 FTE、コンティンジェンシーは 10% から 0%、そして本番用スタンドアロン L1 ノード、完全な L2 統合、高度な devnet、広範な形式検証は後続フェーズへ繰り延べられています。残る範囲は 3 つの目標です。既存の Scalus インフラを保守し Dijkstra ハードフォークに対応させること、JVM および JavaScript/TypeScript 開発者に向けた相互運用性を深化させること、そして限定的なアプリケーションランタイムの初版を提供することです。オンチェーン受領先は script credential(stake17xzhu4tdpl4gdsupfmn3yjlngt2f3mjes3v6wwg9yd767ps8k5qvl)です。

    SIPO はこれを支持します。SIPO が支持する公共財・ビルダーインフラの類型に該当し、支出のほぼ全額がエンジニアリング、保守、開発者支援に向かい、ブランドマーケティング的要素を含みません。資金はエコシステムの外へ流出するのではなく、内部のビルダーへ還流します。Scalus は現に使われている依存物であり、既存のものをハードフォークをまたいで維持することは任意の作業ではありません。Java・Kotlin・TypeScript の開発者を、彼らが既に使っているツールチェーン経由で Cardano に迎え入れることは、ビルダー層を広げる手段として相対的に安価な部類に入ります。監視ボードは IOG、Cardano Foundation、Blink Labs による独立した技術的信認を備えます。トレジャリー資金は、auto-abstain の DRep 委任とステークプール非委任を強制するエスクロー下に置かれ、投票力にもステーキング報酬にも転化しません。開発活動は検証可能な形で継続しています。

    SIPO が支持するもう一つの理由は、この反復に応えるべきだからです。提案者は規模が過大かどうかを DRep に自ら問い、過大であると告げられ、同じ要求を包み直すのではなく縮小して戻ってきました。ガバナンスが単に否決された提案ではなく、より良い提案を生み出す仕組みであるべきなら、この振る舞いは支持で応えられる必要があります。

    数値について 2 点付記します。参照価格 $0.16 は現在ほぼ市場価格と一致しています(ADA は約 $0.1646)。したがって ADA 数量の水増しはありませんが、再提出時に有していた国庫側に有利なマージンはもはや存在しません。コンティンジェンシーが 0% であるため、ADA のさらなる下落は国庫ではなく提案者が吸収します。SIPO は範囲が維持され追加要求が行われないことを期待し、後日の増額要求は条件の実質的変更として扱います。また SIPO は、Dijkstra 対応がハードフォーク後ではなくそれに先行して完了することを期待します。加えて Lantr Engineering は同じ batch で Bifrost Phase 1 も担当しているため、両者が別個の人員体制で遂行されていることが報告で示されるべきです。本投票は SIPO DRep の記録上の立場表明です。

  • Yes4.5M ₳No rationale
  • Yes109.5K ₳No rationale
  • Yes1.8M ₳Rationale

    I voted no last time, but this is a different proposal with a reduced scope and ask.

    What’s left is worth funding: including keeping the widely-used Scalus components maintained, and making them easier to reuse.

  • Abstain102.1K ₳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 Report

    1. Introduction

    Scalus is an established open-source Cardano development platform created by Lantr Engineering and developed continuously over three years. Its components support complex protocols and applications such as Gummiworm L2, the Bifrost bridge, SugarRush DEX, Vela stablecoin, and DID/DIDComm identity infrastructure. They are also reused through developer tools including MeshJS, Evolution SDK, Lucid Evolution, Cardano Client Lib, and YaciDevKit.

    The governance action requests ₳2,464,844, approximately US$394,375 at a reference rate of US$0.16 per ADA, for nine months of milestone-based work. The scope covers maintenance of the existing infrastructure, preparation for the Dijkstra hard fork, interoperability across JVM and JavaScript/TypeScript ecosystems, and a first scoped application-runtime release. The standalone L1 node, full Gummiworm integration, broad formal verification, and contingency reserve included in the previous version have been removed. Delivery is administered through SundaeSwap treasury contracts, an independent oversight board, third-party technical assurance, quarterly reporting, and public transaction records.

    2. Governance Action Analysis

    Positive aspects

    The new version represents a substantial improvement over the previous proposal. The main concern regarding the excessively broad scope was largely mitigated. The budget was reduced by approximately 71%, the scope was significantly narrowed, development of the L1 node, full integration with Gummiworm, and the broader formal verification work were removed, and the proposal became focused on maintaining the existing infrastructure, preparing for the Dijkstra hard fork, interoperability, and a first stage of the application runtime. This significantly reduces execution risk and makes the proposal much more proportional.

    The KPIs also evolved compared with the previous proposal. There are objective and verifiable targets for interoperability, documentation, adoption, and hard fork readiness.

    The overall quality of the proposal is high. The document is well structured, responds directly to the criticisms received during the previous submission, and demonstrates concern for governance, accountability, and transparency. The team’s track record also inspires confidence, both because of its accumulated experience and its history of previous deliveries within the Cardano ecosystem.

    Negative aspects

    The budget, on the other hand, continues to be based on a compensation methodology positioned in the upper range of the market. The rate of approximately US$210,000 per FTE per year, approximately US$101 per hour, remains high even when compared with benchmarks from developed countries with traditionally high compensation levels. This, by itself, does not mean that the costs are inflated or inappropriate, especially considering the level of specialization expected for the work. However, it also does not characterize a particularly cost-effective proposal or an exceptional opportunity for the Treasury. It is a premium budget for a highly specialized team.

    Agora also does not regard positively the decision to eliminate the budget contingency entirely solely to reduce the requested amount. The existence of a risk-mitigation reserve is a common practice in software development projects and contributes to increasing execution resilience in the face of unforeseen events. Although removing the contingency made the proposal leaner, reducing the budget at any cost is not, in itself, regarded as desirable. Under certain circumstances, an appropriately justified contingency reserve may represent more prudent risk management than an excessively compressed budget.

    Although the KPIs have evolved, they remain relatively modest and are concentrated mainly on delivery and initial-adoption indicators, providing limited evidence regarding broader ecosystem impact.

    The broader context of resource allocation also needs to be considered. Treasury distribution data indicate a strong concentration of resources in infrastructure proposals during both this cycle and the previous one. This allocation bias reduces the marginal competitiveness of new initiatives in the same category, since other strategic areas of the ecosystem remain relatively less supported and compete for the same limited budget.

    Risks and concerns

    The point that continues to generate the greatest uncertainty is the proposal’s strategic thesis itself. Although the document presents plausible arguments for expanding the Scalus platform and strengthening its integration with the JVM ecosystem, Agora does not find that the pitch demonstrates sufficiently convincingly the need for this implementation or the adoption potential that would justify prioritizing it over other competing initiatives. The proposal presents evidence of use and technical reuse, but it still does not provide Agora with sufficient conviction regarding future demand or the strategic priority of this investment for the ecosystem as a whole.

    3. Vote and Rationale

    Vote: ABSTAIN

    It is also recognized that Agora is not the most qualified party to assess, with a high degree of confidence, the technical merit and strategic importance of this specific technological direction.

    The new version substantially mitigates the previous concerns regarding breadth, proportionality, and execution risk. The proposal has evident qualities, objective KPIs, a well-structured governance and accountability model, and an experienced team with a history of delivery. However, the premium compensation methodology remains, the KPIs provide limited evidence of broader ecosystem impact, Treasury resources are already strongly concentrated in infrastructure, and the necessity, future demand, and strategic priority of this implementation have not been demonstrated with sufficient conviction.

    Faced with evident qualities, but also relevant limitations and uncertainties, sufficient conviction was formed neither to support the proposal nor to reject it. For these reasons, the position remains ABSTAIN.

    4. Conclusion

    The narrower scope and reduced execution risk materially improve the proposal. However, the premium budget, modest impact indicators, existing concentration of Treasury funding in infrastructure, and uncertainty regarding demand and strategic priority prevent a definitive position in either direction. The vote therefore remains ABSTAIN.


    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.

    Relatório de Ação de Governança

    1. Introdução

    Scalus é uma plataforma open source de desenvolvimento para Cardano estabelecida pela Lantr Engineering e desenvolvida continuamente ao longo de três anos. Seus componentes apoiam protocolos e aplicações complexas, como Gummiworm L2, a bridge Bifrost, SugarRush DEX, Vela stablecoin e a infraestrutura de identidade DID/DIDComm. Também são reutilizados por ferramentas de desenvolvimento como MeshJS, Evolution SDK, Lucid Evolution, Cardano Client Lib e YaciDevKit.

    A ação de governança solicita ₳2.464.844, aproximadamente US$394.375 com uma taxa de referência de US$0,16 por ADA, para nove meses de trabalho baseado em milestones. O escopo inclui a manutenção da infraestrutura existente, preparação para o hard fork Dijkstra, interoperabilidade entre os ecossistemas JVM e JavaScript/TypeScript e uma primeira versão de escopo limitado do application runtime. O node L1 independente, a integração completa com Gummiworm, o trabalho amplo de formal verification e a reserva de contingência presentes na versão anterior foram removidos. A execução será administrada por contratos de tesouraria da SundaeSwap, um conselho de supervisão independente, garantia técnica de terceiros, relatórios trimestrais e registros públicos das transações.

    2. Análise da Ação de Governança

    Aspectos positivos

    A nova versão representa uma melhoria substancial em relação à proposta anterior. A principal preocupação sobre o escopo excessivamente amplo foi amplamente mitigada. O orçamento foi reduzido em cerca de 71%, o escopo foi significativamente enxugado, o desenvolvimento do node L1, a integração completa com Gummiworm e o trabalho mais amplo de formal verification foram removidos, e a proposta passou a concentrar-se na manutenção da infraestrutura existente, preparação para o hard fork Dijkstra, interoperabilidade e uma primeira etapa do application runtime. Isso reduz significativamente o risco de execução e torna a proposta muito mais proporcional.

    Os KPIs também evoluíram em relação à proposta anterior. Existem metas objetivas e verificáveis para interoperabilidade, documentação, adoção e preparação para o hard fork.

    A qualidade geral da proposta é elevada. O documento é bem estruturado, responde diretamente às críticas recebidas na submissão anterior e demonstra preocupação com governança, prestação de contas e transparência. O histórico da equipe também inspira confiança, tanto pela experiência acumulada quanto pelo histórico de entregas anteriores no ecossistema Cardano.

    Aspectos negativos

    O orçamento, por outro lado, continua baseado em uma metodologia de remuneração posicionada na faixa superior do mercado. O rate de aproximadamente US$210 mil por FTE/ano, cerca de US$101 por hora, permanece elevado mesmo quando comparado a benchmarks de países desenvolvidos com remunerações tradicionalmente altas. Isso, por si só, não significa que os custos estejam inflados ou sejam inadequados, especialmente considerando o nível de especialização esperado para o trabalho. No entanto, também não caracteriza uma proposta particularmente eficiente do ponto de vista de custo-benefício ou uma oportunidade excepcional para o Tesouro. Trata-se de um orçamento premium para uma equipe altamente especializada.

    Agora também não considera positiva a decisão de eliminar integralmente a contingência orçamentária apenas para reduzir o valor solicitado. A existência de uma reserva para mitigação de riscos é uma prática comum em projetos de desenvolvimento de software e contribui para aumentar a resiliência da execução diante de eventos imprevistos. Embora a remoção da contingência tenha tornado a proposta mais enxuta, a redução do orçamento a qualquer custo não é, em si, um aspecto que Agora considera desejável. Em determinadas circunstâncias, uma reserva de contingência adequadamente justificada pode representar uma gestão de riscos mais prudente do que um orçamento excessivamente comprimido.

    Embora os KPIs tenham evoluído, permanecem relativamente modestos e concentram-se principalmente em indicadores de entrega e adoção inicial, oferecendo evidências limitadas sobre impacto mais amplo para o ecossistema.

    O contexto mais amplo de alocação de recursos também precisa ser considerado. Os dados de distribuição do Tesouro indicam uma forte concentração de recursos em propostas de infraestrutura tanto neste ciclo quanto no anterior. Esse viés de alocação reduz a competitividade marginal de novas iniciativas da mesma categoria, uma vez que outras áreas estratégicas do ecossistema permanecem relativamente menos contempladas e disputam o mesmo orçamento limitado.

    Riscos e preocupações

    O ponto que continua gerando maior incerteza é a própria tese estratégica da proposta. Embora o documento apresente argumentos plausíveis para a expansão da plataforma Scalus e para o fortalecimento da integração com o ecossistema JVM, Agora não considera que o pitch demonstre de forma suficientemente convincente a necessidade dessa implementação nem o potencial de adoção que justificaria priorizá-la frente a outras iniciativas concorrentes. A proposta apresenta evidências de utilização e reutilização técnica, mas ainda não transmite a Agora convicção suficiente sobre a demanda futura ou sobre a prioridade estratégica desse investimento para o ecossistema como um todo.

    3. Voto e Justificativa

    Voto: ABSTAIN

    Também se reconhece que Agora não é a parte mais qualificada para avaliar, com elevado grau de confiança, o mérito técnico e a importância estratégica dessa direção tecnológica específica.

    A nova versão mitiga substancialmente as preocupações anteriores relacionadas à amplitude, proporcionalidade e risco de execução. A proposta possui qualidades evidentes, KPIs objetivos, um modelo bem estruturado de governança e prestação de contas e uma equipe experiente com histórico de entregas. No entanto, permanecem a metodologia de remuneração premium, a capacidade limitada dos KPIs de demonstrar impacto mais amplo para o ecossistema, a forte concentração de recursos do Tesouro em infraestrutura e a ausência de convicção suficiente sobre a necessidade, a demanda futura e a prioridade estratégica dessa implementação.

    Diante de qualidades evidentes, mas também de limitações e incertezas relevantes, não foi formada convicção suficiente nem para apoiar a proposta nem para rejeitá-la. Por essas razões, a posição permanece ABSTAIN.

    4. Conclusão

    O escopo mais enxuto e a redução do risco de execução melhoram materialmente a proposta. No entanto, o orçamento premium, os indicadores modestos de impacto, a concentração existente de recursos do Tesouro em infraestrutura e as incertezas sobre demanda e prioridade estratégica impedem uma posição definitiva em qualquer direção. O voto permanece ABSTAIN.

  • No6.6M ₳No rationale
  • NoChanged0 ₳History

    Earlier votes

    Yes4mo agoSuperseded

    No4mo agoSuperseded

  • Abstain21.5M ₳No rationale
  • No394.8K ₳No rationale