Framework for contract development

[ghost]

Summary

Hello. I propose to improve the framework for working with smart contracts by transferring the best practices from my framework for the Venom TVM blockchain - Vendee

Context

Three years ago I became interested in TVM. At that moment I made a choice towards Everscale. To work with the blockchain, I wrote my own scripts. This eventually turned into the jton library. Later, I collected all the code from jton into one framework and made a production version. Later, I decided to look at what tools are used in TON and found that my solution has more functionality and is also more convenient then blueprint.

Goals

Rewrite the framework to TON so that the community gets a good tool for working with contracts.

Deliverables

• Separate compilation. Compile only changed files
• Documentation site
• Interactive menu
• Scripts and interactive menu for giver mangment
• Automatic launch of Sandbox, without specifying in the code
• Automatic compilation, without specifying in the code
• Project configuration. Giver keys, compiler versions
• Automatic generation of wrappers from TLB.
• Less code in tests and scripts.
• Scripts for npm package creation
• Plugin support

Definition of Done

• [ ] Same functions like Vendee working in TON
• [ ] Documentation site
• [ ] Example on Nodejs
• [ ] Example on React

Reward

• $ 6,000 in TON equivalent
• Standard TON Footstep NFT

Oriental Release Date

2 month after approvement

[Gusarich]

I believe we don't need another development framework currently (we have toncli and blueprint). What if you just make some major upgrades for the blueprint?

Also I think it'll be good to see what @Naltox and @krigga would say about the takes on the blueprint.

[ghost]

What if you just make some major upgrades for the blueprint?

I had this option in mind. Yes.

And I also good to see @Naltox and @krigga.

[delovoyhomie]

Given that this proposal hasn't resonated with the community and there's currently no evident need for such a tool, I find it necessary to close it. Should you come across specific use cases for this framework or if the community expresses interest in a similar solution, please submit a new issue with a comprehensive context, and we will gladly review it again.