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

TON Connect integration in TON Plugin #2984

Closed
delovoyhomie opened this issue Jan 29, 2025 · 6 comments
Closed

TON Connect integration in TON Plugin #2984

delovoyhomie opened this issue Jan 29, 2025 · 6 comments
Labels
enhancement New feature or request ton-plugin-bounty

Comments

@delovoyhomie
Copy link

delovoyhomie commented Jan 29, 2025

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

  • Action to initialize a TON Connect session.
  • Support for multiple wallets and seamless wallet switching.
  • Ensure persistent and session-based connections for AI agents.
  • Ensure compatibility with elizaOS modules, allowing AI-driven automation of blockchain interactions.
  • The integration should use the official TON Connect library from https://github.com/ton-connect to ensure compatibility and reliability (forks are not allowed).
  • Documentation on how AI agents utilize actions and how users can interact with them.

Useful Resources

Definition of Done

  • Fully integrated TON Connect actions for authentication and session handling.
  • Verified compatibility with TON Connect standard and security best practices.
  • Documentation on how AI agents can use each action.

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

@delovoyhomie delovoyhomie added the enhancement New feature or request label Jan 29, 2025
Copy link
Contributor

Hello @delovoyhomie! Welcome to the elizaOS community. Thank you for opening your first issue; we appreciate your contribution. You are now an elizaOS contributor!

@kunal-drall
Copy link

I would like to claim this task to implement TON Connect integration for the TON Plugin.

Technical Approach

  1. Direct integration with official TON Connect library (https://github.com/ton-connect)
  2. Implementation of persistent session management for AI agents
  3. Development of secure multi-wallet support system
  4. Creation of elizaOS-compatible action interfaces

Implementation Strategy

  • Utilize TON Connect's official SDK for core functionality
  • Build robust session management system for AI agent persistence
  • Implement comprehensive wallet state handling
  • Create detailed documentation for AI agent interactions

Commitment

  • Follow TON Connect Developer Guidelines strictly
  • Maintain compatibility with elizaOS architecture
  • Provide thorough documentation and examples
  • Ensure comprehensive test coverage

I look forward to contributing to the TON ecosystem and creating a seamless integration between TON Connect and elizaOS.

@QBe1n
Copy link

QBe1n commented Feb 4, 2025

I finished task and wrote the plugin, how to commit?

@allen-hsu
Copy link

Hi, @delovoyhomie , I create this PR for this issue
elizaos-plugins/plugin-ton#5

@DrtIggi
Copy link

DrtIggi commented Feb 11, 2025

Working on this task!

@dijor0310
Copy link

Hi @delovoyhomie,

I have a question regarding this requirement:

  • Support for multiple wallets and seamless wallet switching.

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,
Diyor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request ton-plugin-bounty
Projects
None yet
Development

No branches or pull requests

7 participants