Helios debugger plugin for VSCode

[GENERAL] Name and surname of main applicant

Christian Schmitz

[GENERAL] Are you delivering this project as an individual or as an entity (whether formally incorporated or not)

Individual

[GENERAL] Requested funds in ada

71000

[GENERAL] Please specify how many months you expect your project to last (from 2-12 months)

5

[GENERAL] Please indicate if your proposal has been auto-translated into English from another language.

No

[GENERAL] Summarize your solution to the problem (200-character limit including spaces)

A conventional stepping debugger plugin for VSCode, that uses code-mapped UPLC scripts, along with knowledge of the input arguments, to step through Helios scripts (and set breakpoints etc.)

[GENERAL] Does your project have any dependencies on other organizations, technical or otherwise?

No

[GENERAL] If YES, please describe what the dependency is and why you believe it is essential for your project’s delivery. If NO, please write “No dependencies.”

No dependencies

[GENERAL] Will your project’s output/s be fully open source?

Yes

[GENERAL] Please provide here more information on the open source status of your project outputs

This plugin will be part of the existing Helios VSCode IDE plugin, which can be found here: https://github.com/Hyperion-BT/helios-ide-plugins

The license will be BSD-3-Clause

[SOLUTION] Please describe your proposed solution.

The solution will be adding features to the current Helios VSCode IDE plugin. VSCode plugins are automatically updated, and users will be able to use the debugger immediately upon publication.

This proposal isn't targeting other IDEs because VSCode is the dominant IDE for Javascript/Typescript tech stacks, which is what Helios targets.

Besides developing the plugin this proposal also includes creating a debugger cloud service, which, when hooked into a bundled smart contract generated by the Helios CLI, will display failed transactions in the IDE plugin, thus making it much easier to debug Cardano smart contracts in production.

[IMPACT] Please define the positive impact your project will have on the wider Cardano community.

Developers inevitably make mistakes that aren't caught by typecheckers. With this plugin developers using Helios will be able to iterate much faster: it will take minutes to track down bugs (even exotic ones), instead of currently tens of minutes to hours.

Ideally, developers will be able to quickly create dApps that aren't even upgradeable, because they will be so well inspected and tested before mainnet launch using tools such as this.

[CAPABILITY & FEASIBILITY] What is your capability to deliver your project with high levels of trust and accountability? How do you intend to validate if your approach is feasible?

The IDE plugin already exists, the debugging functionality would be an addition to that plugin.

The Helios compiler already produces UPLC scripts with code mapping to the original Helios sources.

The UPLC CEK machine in the Helios library is fully asynchronous and already keeps track of the live stack. This can easily be extended to include scope information like current values of variables.

The cloud-based debugging service would be a minimal AWS Lambda+DynamoDB application, a technology I have plenty of experience with.

The challenge lies mostly in familiarizing myself with the VSCode debugger API.

[Project Milestones] What are the key milestones you need to achieve in order to complete your project successfully?

First, familiarize myself with the VSCode debugger API. Investigate if VSCode supports backstepping.

Design and implement a VSCode widget that allows running any Helios entry point script in the current VSCode workspace. The user will be able to enter either JSON or CBOR-hex argument data into input fields.

The result of an evaluation will be printed in the debugger console.

The Helios scripts will be compiled JIT, and the resulting UPLC will be cached in a user-specific location.

Acceptance criteria:

A video showing the ability to launch any entry point script from within VSCode, and then display the UPLC result.

Import the UPLC CEK machine into VSCode dynamically and allow VSCode to hook into it using callbacks upon starting a UPLC evaluation. The plugin will be able to access the code-map sites through these callbacks.

These code-map sites will then be used to detect when breakpoints are hit and display progress when stepping through an evaluation.

Acceptance criteria:

A video showing the ability to launch an entry point script and stop at a breakpoint set in any of the Helios scripts that formed part of the compilation input for a given entry point. Subsequently, show the ability to step manually to the end.

Display live stack/scope info in the relevant VSCode widgets. Be able to interact with the variables in the debugger console.

Acceptance criteria:

Be able to do everything that is currently possible in the Helios playground. Then deprecate the Helios playground and replace it with a preconfigured version of VSCode-web.

Create a cloud service that stores the details of failed transactions in an AWS DynamoDB table. Implement an AWS Lambda function (behind AWS APIGateway) to allow polling the failed transactions table. Implement another AWS Lambda function that pushes failed transactions into the table.

Allow creating authentication tokens via the HyperionBT or Helios (WiP) website, using the wallet Cip-30 connector to authenticate the users initially. These authentication tokens will then be stored in another DynamoDB table.

Modify the Helios CLI to connect the JS contract bundle to this service. Modify the VSCode plugin to auto-detect Helios debugging service authentication tokens, and then poll frequently for failed transactions which are then used to auto-populate the debug launch widget.

Acceptance criteria:

A public video demo of the complete debugging process with a contract running in production.

[RESOURCES] Who is in the project team and what are their roles?

Christian Schmitz: creator of Helios

https://www.linkedin.com/in/christian-schmitz-ba0a23b9/

I will try to dedicate 0.5 FTE to this, but if I can't find enough time I will reach out to other Cardano developers through the Helios discord.

Required skills for working on the plugin: proficient in Javascript/Typescript, able to use IDE debuggers effectively, familiar with the VSCode API (bonus).

Required skills for working on the debugging cloud service: proficient in using the JS/TS CDK for AWS Cloudformation.

[BUDGET & COSTS] Please provide a cost breakdown of the proposed work and resources.

Milestone 1: 10 FTE days

Milestone 2: 10 FTE days

Milestone 3: 10 FTE days

Final milestone: 15 FTE days (10 for cloud service, 5 for replacing Helios playground with VSCode web)

45 FTE days => 360 FTE hours @ 8 hours per day => 27000 USD @ 75 USD/hour => 71000 ADA @ 0.38USD/ADA

Timeline: all milestones run sequentially, I will make sure that 0.5 FTE is available to work on this (myself + hired engineer(s)) => 4.5 months => rounded up to 5 months

[VALUE FOR MONEY] How does the cost of the project represent value for money for the Cardano ecosystem?

Whilst working on PBG token for the last 6 months I've spent about 1 FTE week in total debugging "exotic" transaction failures of the contract in preprod. Assuming that this plugin would've been able to reduce that to 1 FTE day, then the saving per major project using Helios is about 8 FTE days per year. At a rate of 75 USD/hour, we can estimate the productivity loss per team at 4800 USD per year.

If 5 or more teams are building on Cardano using Helios this proposal will pay itself back in a little over 1 year.

I think this is a conservative estimate.

[IMPORTANT NOTE] The Applicant agrees to Fund Rules and also that data in the submission form and other data provided by the project team during the course of the project will be publicly available.

I Accept