project mod

[subtly]

Grant Application Checklist

• The application-template.md has been copied, renamed ( "project_name.md") and updated.
• A BTC address for the payment of the milestones is provided inside the application.
• The software of the project will be released under the Apache license version 2.0 as specified in the terms and conditions.
• The total funding amount of the project is below 30k at the time of submission.

[CLAassistant]

All committers have signed the CLA.

[Noc2]

Thanks for the application. As I already wrote you via email, we generally want teams to finish the first grant before we follow-up with an additional grant to get a better understanding of the team. Also the links to the previous code currently don’t work. I’m also not sure how this differentiates from your previous grant via the general grants program and what’s the additional benefit of this project. Furthermore, I like to point out that our budget currently gives us less room to finance educational grants via the open grants program. It might be easier to apply for these kinds of grants via the kusama treasury or the general grants program.

[subtly]

Thank you for reviewing.

Project mod is to implement CLI tools written in Rust; you can see example commands for mod at the end of milestone 2. One benefit is being able to create, validate and sign transactions from an offline terminal.

It isn't an educational grant application; I've made updates to reflect that and fixed the links to previous code. As per your other questions, we were advised by several people to apply for a grant here.

Is there something specific about the team you'd like to better understand?

[Noc2]

To be honest, I was expecting a CLI tool written in rust as part of your previous grant and if I remember correctly you told me that you potentially would switch to a rust CLI (or otherwise you need to integrate rust bindings) for your second milestone. Together with the fact that you haven’t updated the repos of your current ongoing grant since the delivery, looks to me like if you basically want to receive a grant to work on something, for which you already received a grant. So, I think you should finish your current grant first and after this potentially reapply for another grant.

[subtly]

To be honest, I was expecting a CLI tool written in rust as part of your previous grant and if I remember correctly you told me that you potentially would switch to a rust CLI (or otherwise you need to integrate rust bindings) for your second milestone.

It sounds like you'd like us to implement a CLI tool written in rust? We can do that with this grant.

Regarding not updating our repos: We read that the approval and payment for the Open Grants program would be fast, and so that's why we've applied for this grant. Our previous efforts consisted entirely of JavaScript. So I don't see this as receiving a grant for work which we've already received a grant for.

[Noc2]

Our previous efforts consisted entirely of JavaScript. So I don't see this as receiving a grant for work which we've already received a grant for.

This application also consisted of javascript, until your last commit 9924158, which you added after your commented and it wasn’t clear to me that your previous application was about javascript. As I said before, I think at this point it makes a lot of sense that you finish your previous grant, before we discuss any follow-up grant (especially if they are so closely related). I therefore will close this application for now. Of course, anyone from the committee can reopen it, in case they think, we should go ahead with the application at this stage.