{"@context":{"CIP100":"https://github.com/cardano-foundation/CIPs/blob/master/CIP-0100/README.md#","hashAlgorithm":"CIP100:hashAlgorithm","body":{"@id":"CIP100:body","@context":{"comment":"CIP100:comment"}}},"hashAlgorithm":"blake2b-256","body":{"comment":"I am voting YES on “Scalus 2026 Maintenance, Dijkstra Readiness, Interoperability & Application Runtime.” Scalus is already established open-source infrastructure in the Cardano ecosystem, with three years of continuous delivery, active use in serious protocols and applications, and indirect reuse across widely used tooling such as MeshJS, Lucid Evolution, Evolution SDK, Cardano Client Lib, and YaciDevKit. This proposal is not asking the Treasury to fund a speculative new platform from scratch, but to maintain and extend infrastructure that other teams already depend on.\n\nMy earlier reservations about Scalus were primarily about the size and breadth of the previous proposal rather than the quality of the work itself, and this resubmission responds to that feedback in a credible way. The ask has been reduced substantially, the scope is narrower and more disciplined, and the most contested items from the earlier version — including the standalone L1 node, full L2 integration, and broad formal-verification track — have been removed from the funded scope.\n\nThe funded work is focused on three concrete priorities: keeping existing Scalus infrastructure maintained and ready for the Dijkstra hard fork, improving interoperability across the JVM and JavaScript/TypeScript ecosystems, and delivering a bounded first application runtime that helps teams move from protocol development toward running applications in production. Those are all reasonable next steps for infrastructure that is already in active use, and they are paired with milestone-based delivery, independent oversight, and third-party assurance.\n\nI also view the budget as proportionate in its revised form. At 2,464,844 ADA over 9 months, with no contingency and only 2.25 FTE of staffing, this is a much more defensible continuation request than the earlier, broader platform expansion. Under current NCL pressure, every YES requires discipline, but this proposal clears the bar because it protects prior public investment, reduces ecosystem breakage risk ahead of Dijkstra, and supports infrastructure that already compounds across multiple teams and tools.\n\nFor those reasons, I am voting YES. This is the kind of scaled-down, feedback-responsive, technically credible infrastructure continuation that Treasury funding should be able to support, even in a tighter budget environment."}}