-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
TON Connect integration in TON Plugin #2984
Comments
Hello @delovoyhomie! Welcome to the elizaOS community. Thank you for opening your first issue; we appreciate your contribution. You are now an elizaOS contributor! |
I would like to claim this task to implement TON Connect integration for the TON Plugin. Technical Approach
Implementation Strategy
Commitment
I look forward to contributing to the TON ecosystem and creating a seamless integration between TON Connect and elizaOS. |
I finished task and wrote the plugin, how to commit? |
Hi, @delovoyhomie , I create this PR for this issue |
Working on this task! |
Hi @delovoyhomie, I have a question regarding this requirement:
Does this mean that we should support simultaneous connection to multiple wallet types (like tonkeeper, tonhub, etc.) or does this mean that we should just support all of them but only be connected to one at a time? BR, |
Description
Enhance the TON Plugin to support seamless integration with TON Connect, enabling AI agents to interact securely with blockchain accounts. This feature will allow AI-driven applications to authenticate and manage user sessions programmatically through TON Connect.
The implementation should be integrated into the elizaOS TON Plugin repository.
What is TON Connect?
TON Connect is a standardized protocol that allows dApps (decentralized applications), web services, and bots to connect seamlessly to a user’s TON wallet. It works similarly to WalletConnect in Ethereum-based ecosystems.
TonConnect.mp4
Key Requirements
Useful Resources
Definition of Done
Bounty
Estimated Reward: $1700 in TON
For questions or further discussion, feel free to reach out in the bounty program working group:
Telegram: @ton_ai_bounty
The text was updated successfully, but these errors were encountered: