Jumpa bot

What is Jumpa Bot 

Jumpa is a Dex Telegram-based group trading and finance platform that makes it easy for people to invest together. Users can form groups, pool funds, assign traders to manage trades, and automatically share profits or losses transparently. Beyond group trading, Jumpa functions as a neo-bank, allowing users to seamlessly buy crypto with local currency and withdraw funds directly to their bank accounts all within Telegram. You retain full control only you have access to your private key. 

Features of Jumpa 

• Multi-Chain Support: Trade on Solana and EVM-compatible chains

• Collaborative Trading: Create groups and make collective trading decisions

• Multi-Wallet Management: Support for multiple Solana and EVM wallets

• Secure Key Storage: Encrypted private key storage

• Fiat On/Off Ramp: NGN withdrawal support via integrated payment gateway

• On-Chain State: Anchor smart contract integration for transparent group management

• Social Trading: Referral system and community-driven decision making

•  Prediction Market - Coming soon .

How Amadeus Is Used

Jumpa integrates with the Amadeus Protocol to enable AI-agent blockchain operations and provide users with secure, verifiable on-chain identity. This integration fulfills multiple aspects of decentralized agent infrastructure.

1. MCP (Model Context Protocol) Integration

Jumpa connects to the Amadeus MCP server at https://mcp.ama.one to provide the AI agent with real-time blockchain capabilities:

• Dynamic Tool Loading: The MCPRegistry dynamically fetches available tools from the Amadeus MCP server, allowing the AI to execute blockchain operations like creating transactions, querying balances, and claiming testnet tokens.
• Tool Execution: When users request blockchain actions in natural language, the AI agent automatically selects and invokes the appropriate MCP tools.
• Configuration: See mcp.config.ts for MCP server configuration.

Implementation Files:

• MCPRegistry.ts - MCP client registry and tool orchestration
• agent.config.ts - AI agent system prompts and MCP tool integration

2. Agent Identity & Memory

Each user in Jumpa has a persistent Amadeus wallet that serves as their on-chain identity:

• Database Schema: Amadeus wallets are stored in MongoDB with encrypted private keys. See the amadeusWalletsfield in the User model.
• Automatic Wallet Creation: When a user registers, an Amadeus wallet is automatically generated and associated with their account.
• Multi-Wallet Support: Users can manage up to 3 Amadeus wallets per account.
• Session Persistence: The AI agent remembers the user's Amadeus address across conversations, enabling continuous identity tracking.

Agent Identity Injection:

// The AI agent is provided with the user's Amadeus addressconst userAddress = user.amadeusWallets[0].publicKey;systemInjection = `OFFICIAL SIGNER ADDRESS: ${userAddress}`;

3. Wallet Management & BLS12-381 Cryptography

Amadeus uses BLS12-381 signatures for transaction signing:

• Keypair Generation: Wallets are generated using the Amadeus SDK's generateKeypair() function.
• Signature Creation: Transactions are signed using the signTransactionfunction, which implements BLS12-381 long signatures with domain separation.
• Private Key Encryption: All private keys are encrypted using AES-256 before storage.
• Key Derivation: The SDK derives secret keys from Base58-encoded seeds using deriveSkAndSeed64FromBase58Seed().

Implementation Files:

• amadeusFunctions.ts - Wallet generation, balance queries, and transaction signing

4. AI-Driven Transaction Flow

The AI agent orchestrates a two-step transaction process for Amadeus blockchain operations:

Step 1: Transaction Creation

• User requests an action (e.g., "Send 10 AMA to [address]")
• AI agent calls the create_transactionMCP tool
• Amadeus MCP server returns signing_payload and blob
• AI pauses and requests user confirmation

Step 2: Signature & Submission

• User confirms transaction
• Application signs the signing_payload using BLS12-381
• AI agent calls submit_transactionwith the signature and blob
• Transaction is submitted to the Amadeus network
• AI returns the transaction hash with an explorer link

Implementation Files:

• AIAgentCallback.ts - Handles AI agent transaction flow, signature confirmation, and submission
• agent.config.ts - System prompts defining the transaction creation protocol

Example Transaction Parameters:

{  signer: "user_amadeus_address",  contract: "Coin",  function: "transfer",  args: [    { b58: "RECIPIENT_ADDRESS" },    "10000000000",  // 10 AMA (1 AMA = 1,000,000,000 base units)    "AMA"  ]}

5. State Proofs & Verification

• On-Chain Verification: All transactions are recorded on the Amadeus blockchain with cryptographic proofs.
• Explorer Integration: Transaction hashes link to the Amadeus testnet explorer at https://testnet.explorer.ama.one/network/tx/[TxHash] and mainnet explorer at https://explorer.ama.one/network/tx/[TxHash].
• Balance Queries: The getAmadeusBalance() function queries on-chain wallet state directly from Amadeus nodes.

6. WASM Runtime (SDK Integration)

The Amadeus TypeScript SDK (@amadeus-protocol/sdk) serves as a high-level wrapper over the Amadeus WASM runtime, providing:

• Keypair generation and key derivation
• Balance queries from Amadeus nodes
• Transaction utilities and serialization
• Base58 encoding/decoding for addresses

SDK Version: ^1.0.2 (see package.json)

7. Future Roadmap

The following Amadeus features are planned for future integration:

• uPoW (Useful Proof of Work): Integrate Amadeus's uPoW consensus mechanism for agent participation in network security
• Oracle Streams: Connect to Amadeus oracle networks for real-time off-chain data feeds
• Swarm Coordination: Enable multi-agent coordination and consensus 
• using Amadeus's swarm protocols

Prediction Prototype - https://www.loom.com/share/4e8dd5d63d384f4c8360b9900963a9c7

Git Hub - https://github.com/arkade-01/jumpa#readme

Pitch deck - 
Pitch deck -   https://pitch.com/v/jumpa-qi8dry

https://pitch.com/v/jumpa-qi8dry