What it does
Combines a compiler, transaction-building SDK, network providers, and debugging tools for BCH contract developers. [1]
A contract language and TypeScript toolkit for building applications on Bitcoin Cash.
Project overview & BCH-1 report · combines linked funding rounds, commitments and results. Each campaign retains its own proposal review; funding success does not establish delivery.
A separate funding request for this project. Status: running.
Partial funding history: known rounds need reconciliation. The BCH and historical USD figures cover linked records, not lifetime project funding. Review 1 unresolved funding entries.
5 of 5 recorded funded campaigns priced at their own dates. 0 use archive dates rather than confirmed funding dates. Daily reference prices, not actual USD proceeds or today’s value.
Combines a compiler, transaction-building SDK, network providers, and debugging tools for BCH contract developers. [1]
The 2025–26 campaign prioritises language features and continued maintenance. Harness reviews should compare each promised feature with tagged releases. [2]
Revision 9 applies canonical Autonomous Review V2 to the accepted CashScript evidence. All five recorded rounds are beyond six months using retained funding-transaction timestamps. Delivery observations keep their original source dates; this reassessment does not claim new independent acceptance tests or a complete scope re-audit. Unknown scope is not non-delivery. [16][17][2][19][18]
Project Assessment Score: 9/10 under canonical Autonomous Review V2. All five recorded rounds contribute; Reach / Scalability is separately scored at 8/10. No automatic planned/unknown backlog deduction applies. The unresolved earlier 100 BCH lead and the 420 BCH request remain outside recorded funding and scoring. Funding success does not establish delivery. BCH-1 human review remains required. [16][18]
The Python SDK, transaction/network tooling and documentation are published. PyPI records 1.0.0 on 22 March 2026 and 1.0.3 on 11 April 2026; the SDK guide and Chipnet examples support all three extracted outcomes. The earlier unresolved classification missed these artifacts. This is a Python SDK port by Andrew and contributors, not a promise to implement a Python compiler. [9][6][7][8]
Retained v0.13.0 and v0.14.0 evidence supports loops, shifts, P2S, functions and constants. The retained 2026–27 retrospective additionally reports delivered testing tools, Playground improvements, documentation and funded-period maintenance. Twelve of seventeen programme items now have reported completion evidence. Arrays and some refactors were explicitly deferred; type-system scope, support and the full events commitment remain unassessed. This is not independent verification. [2][10][11][12][13][14][18]
CashScript began in 2019 as Rosco Kalis’s thesis project at Bitcoin.com. The earliest recovered crowdfunding receipt in this report is September 2023, not the project’s creation date. Earlier employment or organisational support has not been quantified as a separate CashScript award. [15][16]
Five recorded funded rounds total 580.00164214 BCH. This includes the recovered 120 BCH September 2023 campaign and the 220 BCH 2025–26 round that was already discussed in research but absent from funding history. The 2023 archive also reports an earlier 100 BCH CashTokens fundraiser; its own receipt and date remain unresolved. The current 420 BCH request is separate. Neither amount is included in the recorded subtotal, which is not a complete lifetime funding figure. [16][2][18]
The recovered 120 BCH proposal targeted libraries and contract interactions. v0.9.0 supports the advanced transaction builder; the 2024 retrospective establishes continuing simple-builder support and explicitly explains the pivot from reusable functions toward debugging, postponing v1.0. Retained v0.14.0 evidence supports eventual functions/imports in October 2026. Three of nine extracted commitments have reported delivery evidence; six remain unassessed. Creator disclosure of a changed priority does not prove donor approval or original-deadline completion. [16][17][11][19]
CashScript combines a high-level language, compiler, SDK and development workflow. Libauth supplies complementary lower-level TypeScript infrastructure; Spedn is an overlapping high-level language alternative with different design choices. The official showcase documents use in AnyHedge, Moria, Tapswap and wallet P2P exchanges. This supports broad relevance within BCH, not an exclusive-provider claim or a quantified active-user total. Reusable tooling enables additional applications without rebuilding the compiler for each integration. Comparable adoption, retention and funded-period cost data for alternatives remain unestablished. [1][20][21][22]
The five eligible rounds total 580.00164214 BCH, approximately $214,463.97 at historical daily BCH prices. This is historical funding value, not verified spending or lifetime cost. Their 33 tracked commitments comprise 22 reported-complete, two explicit deferrals and nine unassessed items. These counts describe research coverage, not an equal-weight completion percentage. The delivery judgment prioritizes substantive language and SDK outcomes and counts shared library work once. No source-specified economic weights or matched peer-efficiency ranking are established. Two older rounds retain a display date-classification gap; underlying transaction timestamps place them well outside grace, and the gap does not remove completion credit. [23][16][2][3][4][5][18]
Extracted commitments and source-reported achievements. A passed target date or funded campaign does not establish delivery.
Tracked-item counts do not measure full scope coverage or the relative value of each outcome.
3 items not yet assessed. Missing evidence review does not establish non-delivery.
Included in score · eligible 2026-04-30
Campaign 76b99b1bb09195ae · 2025-10-31
Autonomous summaryTwelve of seventeen commitments have reported delivery evidence, including documentation, testing, Playground improvements and funded-period maintenance. Arrays and some refactors were explicitly deferred; three other items remain unassessed. None is independently verified by this review.
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]
Source target: May 2026Released 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]
Source target: May 2026Released 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]
Source target: October 2026Released 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]
Source target: October 2026Listed in the funded 2025–26 programme; completion has not yet been reconciled with a release or acceptance artifact. This remains unassessed against the complete funded scope; it is not a finding that no work was delivered. [2]
Source target: No date statedThe 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]
Source target: No date statedDiagnostics 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]
Source target: No date statedEditor 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]
Source target: No date statedThe 2026–27 retrospective explicitly says some planned refactors were deferred and carried into the new maintenance scope. Preserve this as a carried-forward obligation; do not count a new funding request as receipt or an automatic discharge of the old promise. [2][18]
Source target: No date statedThe 2026–27 creator retrospective reports autocomplete, hover hints and live error diagnostics delivered in the Playground and VS Code extension. This supports reported delivery of tooling work in the funded period; no independent acceptance testing. [2][18]
Source target: No date statedThe creator retrospective reports Vitest testing extensions delivered, supplementing the previously reviewed testing suite and MockNetworkProvider releases. Recorded as reported completion of testing improvements, not certification of exhaustive test or lint coverage. [2][18][10][11]
Source target: No date statedThe funded-period retrospective reports seven releases, eight prereleases and 64 closed issues, alongside the specific bug fixes retained in the earlier release review. This supports reported delivery of ongoing maintenance during the period, not a claim that all bugs are resolved. [2][18][10][11]
Source target: No date statedEcosystem and Telegram support leaves no artifact trail in the reviewed sources. Not verifiable here; remains open. This remains unassessed against the complete funded scope; it is not a finding that no work was delivered. [2]
Source target: No date statedThe creator retrospective identifies delivered Contract Design guides on modular design, concurrency and optimisation, a deployment guide and documentation for new language features. The previous open classification reflected an unperformed inventory review, not evidence of missing documentation. [2][18]
Source target: No date statedA 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. This remains unassessed against the complete funded scope; it is not a finding that no work was delivered. [2]
Source target: No date statedTracked-item counts do not measure full scope coverage or the relative value of each outcome.
Included in score · eligible 2025-12-10
Campaign 1184a1a4645ed824 · 2025-06-10
Autonomous summaryAll three extracted SDK, transaction/network and documentation outcomes are supported by the published cashscript-py release and public guides. Marked reported complete with release evidence. The funded proposal did not require a Python compiler or full parity with advanced TypeScript debugging.
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]
Source target: No date statedPublished 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]
Source target: No date statedPublic 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]
Source target: No date statedTracked-item counts do not measure full scope coverage or the relative value of each outcome.
Included in score · eligible 2025-04-10
Campaign 77d93c2dbef3cb57 · 2024-10-10
Autonomous summaryCashScript reports its 2024–25 programme complete and uses it as the base for the next development cycle. The round is summarized as delivered on creator evidence; a reviewer should still connect each original promise to releases and tests.
Tracked-item counts do not measure full scope coverage or the relative value of each outcome.
Included in score · eligible 2024-05-16
Campaign 700fa5cab65569b1 · 2023-11-16
Autonomous summaryThe later CashScript campaign reports the debugging programme complete, including source-to-script mapping and more capable developer diagnostics. These are meaningful improvements to contract development, though the completion claim still needs release-level human review.
Tracked-item counts do not measure full scope coverage or the relative value of each outcome.
6 items not yet assessed. Missing evidence review does not establish non-delivery.
Included in score · eligible 2024-03-09
Campaign 34a925a6d3c3a5bb · 2023-09-09
Autonomous summaryThree of nine extracted commitments have reported delivery evidence: multi-contract transactions, retained simplified support and eventual reusable functions/imports. The 2024 retrospective explains the shift toward debugging and delayed v1.0. Six items remain unassessed; they are not established failures. Original deadlines and donor acceptance of changed scope remain separate questions.
Retained v0.14.0 release evidence provides reusable functions and imports from node_modules. Evidence is dated October 2026, not proof of meeting the May 2024 target. Overlaps later reusable-functions scope. The 2024 retrospective documents deprioritisation of reusable functions and postponement of v1.0; this is a disclosed scope change, not proof of donor agreement. [16][11][19]
Source target: 15 May 2024Imports and reusable functions do not alone prove that the promised standard library was published. [16]
Source target: 15 May 2024No historical documentation inventory was reconciled against this funded commitment. [16]
Source target: 15 May 2024Later editor releases exist, but the historical library-specific commitment and its timing have not been reconciled. [16]
Source target: 15 May 2024The 2024 retrospective explicitly reports debugging shipped for the Simple Transaction Builder while advanced-builder debugging remained the next priority. This establishes retained simplified transaction support by that retrospective, without independently proving every original deadline. [16][19]
Source target: 15 May 2024No dated guide inventory has been checked against the original interaction documentation promise. [16]
Source target: 15 May 2024Includes the cited estimated-fee bug and maintenance/support through May 2024. No item-specific reconciliation was performed. [16]
Source target: 15 May 2024A funded code-maintenance output, with no accepted completion evidence identified in this targeted recovery. [16]
Source target: 15 May 2024View commitments and delivery → Campaign 76b99b1bb09195ae
View commitments and delivery → Campaign 1184a1a4645ed824
View commitments and delivery → Campaign 77d93c2dbef3cb57
View commitments and delivery → Campaign 700fa5cab65569b1
View commitments and delivery → Campaign 34a925a6d3c3a5bb
These sources are shown separately while campaign identity, attribution or funding evidence is checked. They do not add to the recorded totals above.
Flipstarter · Creator-reported funding: 100.00 BCH. The later 2023 campaign describes the earlier CashTokens fundraiser as successful and gives its amount as 100 BCH. Its own fulfillment transaction and date remain unverified.
Checked 2026-11-18 · Source checked. Repository activity does not establish milestone delivery.
Profile revision 9 · updated 2026-10-29 · Initial research snapshot
Primary project page reviewed for this initial profile; descriptions are paraphrased and claims are attributed.
Official archive reports 220 BCH funded and links transaction 8c06ee6ee65673f182599deff5eb4f6021e72749c53539016666591cfe61ad30. Blockchair records block 922888 on 31 October 2025; the archive displays 1 November 2025. Funding does not prove delivery.
Atlas campaign record for the 75 BCH debugging-tools round.
Atlas campaign record for the 140 BCH development round.
FundMe campaign record for the 25.00164214 BCH Python implementation round.
Published Python SDK distribution; PyPI JSON confirms 1.0.0 on 22 March 2026 and 1.0.3 on 11 April 2026. Release artifacts inspected; package not executed.
Published guide documents Contract, TransactionBuilder, NetworkProvider and SignatureTemplate, using artifacts compiled by cashc.
Published Chipnet transfer and timeout walkthrough with runnable example reference. No transaction executed.
Fresh public get-campaign/37 retrieval. Andrew proposes a Python SDK and documentation; advanced debugging and alternative providers are optional if time permits. Not a Python compiler commitment.
Tagged release published 26 May 2026. Compiler loops (for/while/do-while), bitwise and arithmetic shift operators and bitwise inversion, strict function parameter types and bounded-bytes narrowing; SDK p2s contract type and a default VM target of BCH_2026_05. Inspected, not executed.
Tagged release published 6 October 2026. User-defined reusable functions with multiple return values, top-level global constants, and import directives resolved from node_modules. Release notes state breaking changes with published migration notes.
Published 6 October 2026, bundling the v0.14.0 compiler; fourth editor-tooling release since 20 August 2026 (v0.9.0, v0.10.0, v0.10.1, v0.10.2).
Default branch last pushed 6 October 2026. Repository activity is not by itself a released feature and no formal release is published for this repository.
Repository created 12 May 2026 and last pushed 17 May 2026, consistent with a workshop delivered around BLISS 2026. Attendance and content quality were not assessed.
Describes creating CashScript at Bitcoin.com during the 2019 thesis project, with work in Tokyo beginning in April.
Official archive: 120 BCH fulfilled by 952effe2fb91175da93002a7eac15bb4acb2d240f98551afe6c0496a9f429853, block 809937, 9 September 2023. Earlier 100 BCH CashTokens round is creator-reported here, with no separate fulfillment receipt recovered.
Fresh GitHub release API inspection: published 16 October 2023; TransactionBuilder combines UTXOs from multiple contracts and P2PKH inputs. Source evidence only; no execution.
Fresh proposal Markdown inspection: retrospective reports documentation, testing, editor/Playground improvements, seven releases and 64 closed issues. Explicitly defers arrays and some refactors. The 420 BCH request remains outside funded accounting; funding status was not refreshed in this delivery review.
Fresh archive inspection: reports interactions and simple-builder debugging delivered; explicitly deprioritises reusable functions and postpones v1.0. Creator statement of changed priorities, not evidence of donor approval.
Official application examples; project-reported integrations, not a measured active-user dataset.
Alternative/complement: lower-level TypeScript primitives rather than the same high-level language workflow. No matched funding or active-user benchmark established.
Overlapping high-level contract language with explicit typing and a different language design. Comparable current adoption and cost were not established.
Retained 2026-10-12 daily-price snapshot, not freshly retrieved: funding-date USD equivalents total $214,463.97. Historical funding is not actual expenditure.
Retained Atlas recovery transaction metadata inspected for this assessment; no fresh explorer retrieval claimed. Transaction timestamp 2023-09-09T19:45:24.000Z. Existing confirmed funding evidence retained.
Retained Atlas recovery transaction metadata inspected for this assessment; no fresh explorer retrieval claimed. Transaction timestamp 2023-11-16T17:03:33.000Z. The archive display lacks explicit confirmed-date classification; retained transaction ID, block height and timestamp establish the historical round for this assessment.
Retained Atlas recovery transaction metadata inspected for this assessment; no fresh explorer retrieval claimed. Transaction timestamp 2024-10-10T11:03:13.000Z. The archive display lacks explicit confirmed-date classification; retained transaction ID, block height and timestamp establish the historical round for this assessment.
Retained Atlas recovery transaction metadata inspected for this assessment; no fresh explorer retrieval claimed. Transaction timestamp 2025-06-10T10:15:32.000Z. Existing confirmed funding evidence retained.
Retained Atlas recovery transaction metadata inspected for this assessment; no fresh explorer retrieval claimed. Transaction timestamp 2025-10-31T06:26:13.000Z. Existing confirmed funding evidence retained.