概要
SIPO DRepレビュー支援用の日本語作業訳です。正式な内容はHydra Voting上の英語原文を参照してください。
MLabsは、PlutarchとPlyの12か月保守・互換性対応・開発者体験改善に1,162,746 ADAを求めています。PlutarchはHaskell eDSLとしてUPLCへ効率的にコンパイルするCardanoスマートコントラクト開発ツールで、PlyはCIP-57 blueprint style artifactsとのシリアライズや型推論を支援します。MLabsは少なくとも26チームが利用しているとし、Dijkstra eraを含むledger/Plutus/UPLCの変化に四半期単位で対応する計画です。SIPOとしては、既存アプリと開発者基盤を守る公共インフラ性を評価します。一方で、過去Catalyst/Intersect資金とのscope分離、26チーム利用の検証可能なbaseline、四半期ごとの優先順位と成果KPI、Dijkstra対応の範囲、NoWitnessLabs auditの実質的検証内容、MLabs複数提案の同時実行能力、ADA価格上昇・未使用資金返還条件を確認する必要があります。
英語原文を表示
This proposal seeks annual funding for the maintenance and enhancement of Plutarch and Ply. Plutarch is a Haskell eDSL for creating efficient Cardano smart contracts via controlled compilation into UPLC. Ply helps serialize Plutarch scripts to and from CIP-57 blueprint-style artifacts with inferred types, protecting the on-chain/off-chain boundary without forcing users to manage low-level type details. Both tools have been extensively used throughout the Cardano ecosystem. During a recent internal audit, MLabs counted at least 26 teams building with Plutarch and Ply. Their continued maintenance is crucial for project teams that require reliable smart contract tooling that tracks protocol evolution. Plutarch also remains efficient and performant. In MLabs’ public cross-language benchmarks (https://mlabs-haskell.github.io/uplc-benchmark/comparison.html), Plutarch scripts rank among the smallest in the benchmark suite while requiring comparatively low on-chain compute and memory. The next funding period is expected to cover ongoing Cardano ledger, Plutus, and tooling evolution, including protocol-era compatibility for major ledger updates such as the Dijkstra era, if relevant changes land during the funding period. Because upstream timing and scope cannot be fully known in advance, this proposal uses a quarterly maintenance model with a clear priority hierarchy. We will allocate proposal resources towards the following areas, in the following order of priority: 1. Critical breakages and serious vulnerabilities 2. Protocol-era and hard-fork compatibility 3. Bug fixes, correctness improvements, and optimizations 4. Documentation, examples, technical blog posts, and developer-experience improvements Overall, this budget will keep Plutarch and Ply reliable, compatible, and useful for Cardano builders while giving maintainers the capacity to respond to real ecosystem needs. The proposal aligns with Cardano 2030 by strengthening open-source smart contract tooling.