Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A series of improvements to Tact Language #384

Open
8 of 9 tasks
Gusarich opened this issue Dec 1, 2023 · 7 comments
Open
8 of 9 tasks

A series of improvements to Tact Language #384

Gusarich opened this issue Dec 1, 2023 · 7 comments
Assignees
Labels
Approved This proposal is approved by the committee Developer Tool Related to tools or utilities used by developers

Comments

@Gusarich
Copy link
Collaborator

Gusarich commented Dec 1, 2023

Summary

Implement necessary improvements and features in Tact language used for writing TON smart contracts

Bounty Context

Why it's Important?
Tact language is the core for writing smart contracts in TON. This being the case, improving its functionality, user-friendliness, and the implementation of new features is crucial in ensuring the efficiency and user experience of contract creation in TON Blockchain.

Problem showcase
Currently, Tact language for TON is quite young in its development stage. There are a multitude of things that need implementation, fixing and improvement.

Potential Solution
The solution involves working on multiple pull requests with new features and improvements for Tact language. The pull requests will be based on the listed items from the public roadmap for the development of Tact language. By systematically implementing these requested changes, we can significantly enhance Tact language readiness for production and user-friendliness.

To-do list

This list may be filled with more features based on feedback from developers

References

REWARD

  • SBT Bounty Reward
  • 3000 USD in TON

🪄 Created with the help of TON Bounties Creator Bot.

@Gusarich
Copy link
Collaborator Author

Gusarich commented Dec 1, 2023

@delovoyhomie please assign me to this issue 🙂

@delovoyhomie delovoyhomie added Approved This proposal is approved by the committee Developer Tool Related to tools or utilities used by developers labels Dec 1, 2023
@delovoyhomie
Copy link
Collaborator

@anton-trunov, let's decide a reward for this bounty!

@Gusarich
Copy link
Collaborator Author

Gusarich commented Dec 4, 2023

@delovoyhomie I think something around 2-3k USD will be fair reward for this bounty.

@anton-trunov
Copy link

I think USD 3k is definitely fair for this amount of work

@delovoyhomie
Copy link
Collaborator

LGTM!

@howardpen9
Copy link

Go og go

@Sashka231
Copy link

Summary

Implement necessary improvements and features in Tact language used for writing TON smart contracts

Bounty Context

Why it's Important? Tact language is the core for writing smart contracts in TON. This being the case, improving its functionality, user-friendliness, and the implementation of new features is crucial in ensuring the efficiency and user experience of contract creation in TON Blockchain.

Problem showcase Currently, Tact language for TON is quite young in its development stage. There are a multitude of things that need implementation, fixing and improvement.

Potential Solution The solution involves working on multiple pull requests with new features and improvements for Tact language. The pull requests will be based on the listed items from the public roadmap for the development of Tact language. By systematically implementing these requested changes, we can significantly enhance Tact language readiness for production and user-friendliness.

To-do list

This list may be filled with more features based on feedback from developers

References

REWARD

  • SBT Bounty Reward
  • 3000 USD in TON

🪄 Created with the help of TON Bounties Creator Bot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Approved This proposal is approved by the committee Developer Tool Related to tools or utilities used by developers
Projects
None yet
Development

No branches or pull requests

5 participants