CashScript

The later official campaign reports all prior campaign deliverables complete; human review should match this claim to releases. [2][3]

Reported complete by the later campaign retrospective; independent release-level checking remains. [2][3]

Reported complete by the later campaign retrospective; independent acceptance review remains. [2][3]

The 2025–26 proposal states that all prior deliverables were completed. This is a creator report pending human reconciliation. [2][4]

Published as cashscript-py on PyPI (1.0.0: 22 March 2026; 1.0.3: 11 April 2026). The documented Python SDK consumes cashc contract artifacts. The funded scope was SDK support, not a Python compiler. Release-backed completion; no independent acceptance test performed. [5][9][6][7][8]

Published SDK documentation provides transaction construction, signatures and Electrum network access for UTXO queries and broadcasting. Supported by the released package and Chipnet walkthrough; no live transaction was executed for this review. [5][9][6][7][8]

Public SDK documentation and a Chipnet getting-started guide include contract transfer and timeout examples. This documentation deliverable is published; runtime correctness has not been independently certified. [5][9][6][7][8]

Released in CashScript v0.13.0 on 26 May 2026: boundedly-safe `for`, `while` and `do-while` loops in the compiler. The funded May 2026 target was met. Project release notes are the evidence; no independent acceptance test was performed for this review. [2][10]

Released in CashScript v0.13.0 on 26 May 2026: bitwise and arithmetic shift operators (`<<`, `>>`) plus bitwise inversion (`~`). The funded May 2026 target was met. Release-note evidence only. [2][10]

Released in CashScript v0.13.0 on 26 May 2026: the SDK added a `p2s` contract type and the default VM target moved to BCH_2026_05, aligning the toolkit with the May 2026 network upgrade. The funded May 2026 target was met. Release-note evidence only. [2][10]

Released in CashScript v0.14.0 on 6 October 2026: user-defined reusable functions, including multiple return values destructured at the call site, with functions debuggable and inlined where that is smaller than `OP_DEFINE`/`OP_INVOKE`. The funded October 2026 target was met. [2][11]

Released in CashScript v0.14.0 on 6 October 2026: top-level global constants including simple arithmetic and concatenation operations. The funded October 2026 target was met. The same release also added cross-file `import` directives resolved from `node_modules`, which is beyond the listed commitment. [2][11]

Listed in the funded 2025–26 programme; completion has not yet been reconciled with a release or acceptance artifact. [2]

No array type appears in any release note through v0.14.0. Tuple destructuring reassignment is not array support. Remains open with no evidence found. [2]

The SDK gained the substantive transaction utilities the programme described: `addBchChangeOutputIfNeeded()`, `addTokenChangeOutputIfNeeded()`, `gatherBchUtxos()` and `gatherFungibleTokenUtxos()`, `getTransactionSize()`, `calculateTransactionFee()`, `lockingBytecode` on all provider UTXOs, and standardised network error classes across v0.13.0 and v0.14.0. Release-backed; no independent test of correctness or completeness against the funded wording. [2][10][11]

Diagnostics advanced across the programme window: loop support in debug tooling (v0.13.0), debugging of user-defined functions (v0.14.0-next.1), and stack traces for failed `require` statements inside nested functions (v0.14.0-next.3). Release-note evidence only; the earlier Meep-replacement round remains separately classified. [2][10][11]

Editor tooling is actively maintained rather than merely promised: vscode-cashscript shipped v0.9.0 on 20 August 2026, v0.10.0 and v0.10.1 on 29 September 2026, and v0.10.2 on 6 October 2026 bundling the v0.14.0 compiler. Warning diagnostics, package-import completion and default-branch maintenance are evidenced; install counts and user experience were not assessed. [2][12]

Maintenance work is observable (removal of the deprecated transaction builder and `BitcoinRpcNetworkProvider`, dependency tidy-up, reduced package size) but is a continuous obligation rather than a completed deliverable. Remains open. [2]

Repository activity on 6 October 2026 is consistent with maintenance continuing alongside the v0.14.0 compiler release, but no formal release exists for the playground and no completion statement was found. Remains open. [2]

Partly addressed without a completion claim: vitest extensions (v0.12.1), a documented testing suite with contract artifacts (v0.13.0), and a `MockNetworkProvider` that validates sent transactions against the BCH VM by default (v0.14.0). Kept open because the funded wording is broader than the released evidence. [2]

Bug fixes shipped in the window (UTC parsing of date literals, `LockingBytecodeNullData` push opcodes, odd-length hex literals, public-key length validation, `getTransactionSize()` undersizing). A maintenance obligation with no defined endpoint; remains open. [2]

Ecosystem and Telegram support leaves no artifact trail in the reviewed sources. Not verifiable here; remains open. [2]

Documentation and migration notes are published and were updated alongside v0.14.0 breaking changes, but no documentation deliverable inventory was assessed. Remains open pending a docs-level review. [2]

A BLISS 2026 workshop repository was created on 12 May 2026 and last pushed 17 May 2026, and prior workshop repositories exist for 2024 and 2025. Delivery of a workshop is evidenced; the funded wording also covers talks, so this remains open pending an events list. [2]