-
Notifications
You must be signed in to change notification settings - Fork 142
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
Dart TonConnect huge update #862
Comments
@delovoyhomie @thekiba please review |
Interesting proposal. The dartTonconnect did, in fact, got somewhat stale and it would be nice to improve it by contributing said updates. However, the estimated reward seems a little high to me — the original submission stated $1400, and the work required for this one doesn't exceed the work made there. At least from my point of view. Of course, feel free to disagree :) |
Can I do this? I am Interested. I am a Flutter developer, and I observed low support for Flutter devs especially in web3. As a community host in my state too, I have met a few devs who fell the same, I would gladly do this for no compensation at all($1,400 is peng tho...) Also, I have worked with React, Typescript and Javascript. I want to be assigned to this task, to finish it in ~two weeks. or as agreed by the reviewer, def looking into it right now. |
Context as stated aap17 The development plan includes:
Estimated Suggested Reward |
@novusnota thank you for the response. I adjusted the award and ready to start. |
Thank you, @novusnota, for your feedback! Yes, @aap17, this is indeed a valuable and much-needed suggestion for updating TON Connect in Dart and it aligns perfectly with our previous implementations. This proposal addresses an important improvement and has now been approved. Could you please share your Telegram handle for further collaboration? |
@delovoyhomie we had a discussion previously |
@novusnota @delovoyhomie
https://github.com/aap17/dart_ton_plus/
|
thank you for this update, it works! |
@aap17 Looks fine, especially the buttons package. That said, why the standalone repo for the TON Connect SDK and not a PR to the existing repository? This would benefit much more people, since there are more educational materials and the bigger user base, that would've just |
Well, it was a tough decision :) The origin repo seems abandoned, and the author hasn't responded to issues since December 2023. PR requires communication, and the author may not agree with solutions. I wanted this repo for my own project task as soon as possible, so I just forked it. Sure, I may revert it to PR if you prefer. |
I have published the packages in pub.dev https://pub.dev/packages/flutter_ton_buttons My solution already in use by community, according to previous messages. What should I do to complete the issue and receive bounty? |
Summary
Flutter framework can be used for the creation Telegram MiniApps. It looks good and smooth, the only problem is monetization. Currently, there is no out-of-the-box solution for crypto payments for Dart projects. Existed project DartTonConnect provide some functions, but they're not working as well as TonConnect for Javascript development.
Flutter community will be boosted for Ton MiniApps creation when TON crypto payments become simple.
Context
I am eager to update existing projects to make payments flow easier. These improvements are to be made:
Update logic to last flutter version support. DartTonConnect doesn't work at all with the last Flutter version.
Make ton http bridge requests more easy and clear. It will work just as TonConnect for Javascript, just a few methods and it's done:
Before
payload
field to transactionAfter
String
to ton cellFlutter devs need UI for the wallet selection menu. DartTonConnect doesn't provide UI at all, add UI banners in Ton-js style to make it suitable for the existing design:
Before
No UI at all
After
Ready-to-use widgets:
Connect TON
button,Connect your wallet
pop-up,Confirm transaction
pop-upReferences
https://github.com/romanovichim/dartTonconnect
Estimate suggested reward
1400$
The text was updated successfully, but these errors were encountered: