Proposal 9uhuy5uame2s60yrh6n8…

Proposal KPI Achievement Metrics

Formula proposal success: PS = v1*IF + v2*IS + v3*ISpeed (berbobot). Nilai yang ditampilkan sudah dinormalisasi 0-100%.

Scraped KPI & Milestone Evidence

KPI Items: 12 | Milestones: 12 | Completed Milestones: 3

• \n There are precedents that serve as reference points and helped us size our target annual billable rate:\n [ 'Input Output Engineering Core Development Proposal for 2025' ](https://explorer.
• We establish a contributor contract via the following steps:\n\n A scope owner formulates an objective and a list of deliverables.
• In particular:\n\n We still aim for a regular demo cadence (once every 2 months on average)\n We set common goals for the project\n Work items are planned in the form of deliverable milestones and typically assigned to one contributor.
• \n\n \n\n Core Development\n\n| 🎯 Main Objective | Owner |\n| | | \n| To reach feature parity with the Haskell node and keep up with the updates on the Cardano network/protocol | [Matthias Benkort](https://github.
• \n\n Key Performance Indicators (KPIs)\n\n| Indicator | Target |\n| | |\n| Ledger rules coverage (via acceptance test scenarios) | 100% |\n| Fuzzers coverage for serialisation / deserialisation of primitive types (c.
• \n\n Key Performance Indicators (KPIs)\n\n| Indicator | Target |\n| | |\n| Coverage of the new Plutus builtins in tests and benchmarks | 100% | \n| Single script evaluation (turbo benchmark) | 1 week | \n\n Estimated Effort \n\n1.
• \n\n Key Performance Indicators (KPIs)\n\n| Indicator | Target |\n| | |\n| Resident memory usage |
• 5 FTE \n Fixed Costs: $500k \n\n \n\n Operations & Use Cases\n\n| 🎯 Main Objective | Owner |\n| | | \n| To facilitate operations & management of the project and pursue interesting use cases.

• \n\n 2025 Retrospective\n\nWe provide a [full retrospective of our 2025 roadmap](ipfs://bafkreihjsdpolefycwjt75nnslqdbweu5pcyffzv6pjuknpc7bldmp2ch4) in annex of this document.
• This includes a head to head comparison with the roadmap items presented last year with their corresponding deliveries.
• The transaction must include the invoice and the milestone details.
• In particular:\n\n We still aim for a regular demo cadence (once every 2 months on average)\n We set common goals for the project\n Work items are planned in the form of deliverable milestones and typically assigned to one contributor.
• \n\nWe will likely adapt our current bi weekly (public) maintainer meeting into more frequent milestone oriented sprints, and we will capture work ahead and discussions in a more systematic manner on GitHub, while still using the website at https://amaru.
• \n [x] a period for delivery of proposed activities which the withdrawal shall be used for : all along 2026, with a [milestone breakdown](ipfs://bafybeidrfx7yxy54xg7crp2n4s2uxflmxaafebf5py4xi2ze75nya3sp5a) and rough timeline given in appendix;
• \n\nWe are immensely proud of what our team has accomplished and delivered in a short timeframe, and we remain conscious that we had to make adjustments to the initially projected roadmap.
• \n\n Key Results\n\n Remaining ledger rules & stabilizations of the phase 2 validations;

Proposal Title & Body

Title: Proposal 9uhuy5uame2s60yrh6n8…

Amaru Treasury Withdrawal 2026 GitHub: https://github.com/pragma-org/amaru-treasury

Voting Composition Chart

Vote Trend Chart

Tidak ada timestamp vote yang cukup untuk dibuat trend chart. Vote tanpa timestamp: 169.