You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My main goal is to solve this problem (and some more problems), to make a specification (let's call it OpenContract) for contract schemas, describing supported internals, authors, get_methods and much more
And, of course, to make a toolset for such tasks: to make a contract documentation with ease, to make a TL-B constructor, TL-B decoder and editor, available on web
Context
Let's take a simple Jetton transfer base64-encoded body.
For example:
But how can you extract, for instance, the forward_ton_amount value from payload with ease? No, you will probably start writing code for a such simple task. And that's not cool.
Open-source treasure of contract schemas and own specification (let's call it OpenContract) for this goal, codegen from TL-B, sandbox for making transactions with ease, decode BoC using specification, 9500 USD
Contribute schemas for most popular contracts on TON, 1000 USD
Codegen tool from OpenContract schemas for Go, TypeScript, Python, Swift, Kotlin, 6000 USD
TL-B constructor from the scratch, 1750 USD
YAML-editor for OpenContract specification, 1750 USD
Electron build for TL-B constructor and playground React apps, 1000 USD
Estimate suggested reward
21000$ in TON
The text was updated successfully, but these errors were encountered:
voloshinskii
changed the title
Swagger-like toolset for interaction with contracts and TL-B
Swagger-like toolset for interaction with contracts and TL-B editor
Sep 29, 2024
voloshinskii
changed the title
Swagger-like toolset for interaction with contracts and TL-B editor
Swagger-like toolset for interaction with contracts and TL-B
Sep 30, 2024
Thank you for submitting your proposal, and apologies for the delayed response. We regret to inform you that we cannot proceed with it under the Bounty program, as it is designed for grants up to $10k.
We encourage you to submit your application via Questbook under the "TON Grants" category. Before doing so, please ensure you review the grant guidelines thoroughly: Grant Program Guidelines.
Thank you for your interest and efforts, and we look forward to seeing your refined submission.
Summary
My main goal is to solve this problem (and some more problems), to make a specification (let's call it OpenContract) for contract schemas, describing supported internals, authors, get_methods and much more
And, of course, to make a toolset for such tasks: to make a contract documentation with ease, to make a TL-B constructor, TL-B decoder and editor, available on web
Context
Let's take a simple Jetton transfer base64-encoded body.
For example:
te6cckEBAQEAVAAApA+KfqUAAAAAAAAAARAYAexswf8o/L/N2pUe5T42Sd8LKS+gkHVVOzXJCChS+Jw3AD2NmD/lH5f5u1Kj3KfGyTvhZSX0Eg6qp2a5IQUKXxOGwgIkIasC
But how can you extract, for instance, the forward_ton_amount value from payload with ease? No, you will probably start writing code for a such simple task. And that's not cool.
References
MVP tool:
https://voloshinskii.github.io/demo-dapp-with-react-ui/?encoded=W3siYWRkcmVzcyI6IkVRREpmU2JzN3N2WHhBNDk3MnlVaXFnSnM5T3V6d0tsX0QzUUdJNkQ1dk5IT0lhViIsImFtb3VudCI6IjUwMDAwMDAwIiwicGF5bG9hZCI6InRlNmNja0VCQWdFQVdnQUJvVi9NUFJSVWJlVHZXOEJ3L0lBZXhzd2Y4by9ML04ycFVlNVQ0MlNkOExLUytna0hWVk96WEpDQ2hTK0p3M0FEMk5tRC9sSDVmNXUxS2ozS2ZHeVR2aFpTWDBFZzZxcDJhNUlRVUtYeE9Hd2dPQUVBQ0FBQUFBRG5rM202In1d
Milestone
Estimate suggested reward
21000$ in TON
The text was updated successfully, but these errors were encountered: