Proposal ggr2uz7prwn5l84cdn2k…

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: 9 | Milestones: 12 | Completed Milestones: 1

• It is imperative first with strong static typing and full type inference, compiling to the same UPLC target.
• The result is two compilers, both targeting UPLC and optimizing the same bytecode, offering different on ramps for different mental models without either subtracting from the other.
• \n\n Alignment with Core KPIs\n\n| KPI / Strategic Priority | 2030 Target / Goal | HLabs Contribution |\n| : | : | : |\n| Monthly Uptime | 99.
• 3) | \"More developers can onboard\" | Pebble provides EVM/TS developers a familiar syntax for Cardano smart contracts |\n\n Note : The first row is a formal Cardano 2030 KPI.
• 3 (Developer Experience → Education & migration), which is an explicit 2030 priority but not yet a numeric KPI.
• \n\nAcceptance criteria are written to be objective and inspectable from a public artifact (a tagged release, a UPLC CAPE submission, a published benchmark report, a committed test log) rather than self reported.
• \n Plutus V4 codegen support in the Pebble compiler , so Pebble contracts can target the post hard fork Plutus version end to end (compilation, execution on a Plutus V4 preview/preprod node).
• \n\n [x] Measurable adoption indicators have been defined to provide visibility into ecosystem level KPI contributions (TVL, monthly transactions, MAU).

• \n\n Milestones\n\nThis proposal spans an initial kickoff plus Q2 2026 through Q1 2027, organized into a kickoff milestone (Milestone 0) and four quarterly engineering milestones (Milestones 1–4).
• Each milestone unlocks a fixed share of the total ₳4,600,000 ask from the vendor.
• The kickoff milestone draws from the base only;
• 5% of base) + ₳150,000 contingency (25% of the contingency reserve)\n Milestone 1 is split into two independently payable sub milestones : 1.
• B can be co signed and paid independently as each sub milestone's deliverables are accepted.
• \n\nAcceptance criteria are written to be objective and inspectable from a public artifact (a tagged release, a UPLC CAPE submission, a published benchmark report, a committed test log) rather than self reported.
• \n\n Milestone 0 (kickoff, on chain enactment): Project Initialization & Governance Setup\n\nMilestone 0 is the kickoff milestone and carries no engineering deliverables.
• \n\n Disbursement on completion \n\n Base milestone payment: ₳400,000 (10% of the ₳4,000,000 base)\n Contingency portion: ₳0 (no contingency disbursed in this milestone)\n Total released: ₳400,000 \n\n Milestone 1.

Proposal Title & Body

Title: Proposal ggr2uz7prwn5l84cdn2k…

CIP108:body GitHub: https://github.com/HarmonicLabs/pebble

Voting Composition Chart

Vote Trend Chart

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