Feature Request: Add User Wallet Address to Agent Chat Protocol for Token-Gated Services

[augustscher]

Prerequisites

• I checked the documentation and made sure this feature does not already exist
• I checked the existing issues to make sure this feature has not already been requested

Feature

Problem Statement:

When building token-gated or premium agents on Agentverse that integrate with ASI:ONE via @-handle, there's no mechanism for agents to access the user's wallet address. This prevents implementation of holder-based access control, premium tiers, or token-gated content delivery.

Use Case:

For building agents on Agentverse that:

• Are accessible via ASI:ONE @-handle
• Use agent-launch.ai for tokenization
• Provide token-gated or paid for premium answers to users and other agents
• Need to verify if users hold specific tokens or have paid for premium services

Current Limitations:

1. No wallet address in chat protocol: The Agent Chat Protocol only provides the sender's agent address, not the user's wallet address
2. Agent address ≠ wallet address: The sender parameter in ChatMessage handlers is the ASI:ONE platform agent, not the user's personal wallet
3. No user profile access: Agents cannot access user profile data, authentication method, or linked wallets
4. Login method agnostic: Whether users log in via wallet (ASI/Keplr), email, or Google, agents have no visibility into their wallet information

Technical Context:

@chat_proto.on_message(ChatMessage)
async def handle_message(ctx: Context, sender: str, msg: ChatMessage):
    # 'sender' is an agent address, not a user wallet
    # No way to access user's wallet address for token verification

Proposed Solution:

Add user wallet address to the Agent Chat Protocol message context, making it available to agents receiving messages. This would enable:

• Token holder verification
• Premium tier access control
• Agent-launch token gating
• Custom payment verification

Implementation Suggestion:

Extend the ChatMessage or Context object to include:

• User's wallet address (if logged in via wallet)
• Linked wallet addresses (for email/Google users who have connected wallets)
• Authentication method indicator

Impact:

This feature would enable a new class of Web3-native agents on Agentverse that can implement token-gated services, premium tiers, and holder-based access control - essential for the agent-launch.ai ecosystem and monetization of agent services.

Priority: High - Critical for token-gated agent economy and agent-launch.ai platform adoption

Additional Information (Optional)

No response