{"id":23121035,"url":"https://github.com/prayag2003/across-protocol-discord-bot","last_synced_at":"2026-05-05T14:03:36.731Z","repository":{"id":258806393,"uuid":"875731635","full_name":"Prayag2003/across-protocol-discord-bot","owner":"Prayag2003","description":"R.O.S.S - Discord Bot for Across Protocol","archived":false,"fork":false,"pushed_at":"2025-04-14T17:12:45.000Z","size":22157,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-04-14T18:26:16.686Z","etag":null,"topics":["discord-bot","discord-py","feedback-learning","fine-tuning","openai","python","q-learning","rag","reinforcement-learning"],"latest_commit_sha":null,"homepage":"","language":"Python","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/Prayag2003.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2024-10-20T17:48:25.000Z","updated_at":"2025-04-14T17:12:49.000Z","dependencies_parsed_at":"2024-10-26T10:26:17.605Z","dependency_job_id":null,"html_url":"https://github.com/Prayag2003/across-protocol-discord-bot","commit_stats":null,"previous_names":["prayag2003/across-protocol-discord-bot"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/Prayag2003/across-protocol-discord-bot","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Prayag2003%2Facross-protocol-discord-bot","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Prayag2003%2Facross-protocol-discord-bot/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Prayag2003%2Facross-protocol-discord-bot/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Prayag2003%2Facross-protocol-discord-bot/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/Prayag2003","download_url":"https://codeload.github.com/Prayag2003/across-protocol-discord-bot/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Prayag2003%2Facross-protocol-discord-bot/sbom","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":264958194,"owners_count":23689010,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["discord-bot","discord-py","feedback-learning","fine-tuning","openai","python","q-learning","rag","reinforcement-learning"],"created_at":"2024-12-17T06:14:33.123Z","updated_at":"2026-05-05T14:03:31.693Z","avatar_url":"https://github.com/Prayag2003.png","language":"Python","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Ross - AI-Powered Assistant for Across Protocol\n\n## Architecture Diagram\n![alt text](assets/architechture.png)\n\n## Workflow Overview\n![alt text](assets/workflow.png)\n\n## **Priority 1: Key Functionality** (Estimated Time: 2 weeks)\n\n### **1.1 Accessibility through Wallet Connectivity \u0026 Financial Assistance**\n\n- **Web3 Wallet Integration**: Enable users to connect their wallets and access balances and transaction histories.\n- **Blockchain Data Insights**: Provide real-time token prices, transaction histories, and other financial data.\n\n### **1.2 Personalized User Experience**\n\n- **User-Specific Insights**: Tailor responses based on user expertise (community members, developers, investors, traders) to ensure relevance and enhance engagement.\n- **Developer Support**: Offer specialized guidance for developers on smart contracts and Across Protocol navigation.\n\n### **1.3 Information Hub Development**\n\n- **Blockchain Data Analytics**: Deliver insights into trading trends, protocol metrics, liquidity positions, and token activity for informed investment and trading decisions.\n- **Docs Explainer**: Simplify and explain Across Protocol documentation to support community understanding.\n\n### **1.4 Data Management \u0026 Learning**\n\n- **Daily Learning Cycles**: Ross will analyze and learn from messages written by trusted community members every 24 hours to provide accurate and up-to-date information.\n- **Selective Memory**: Ross will prioritize learning from specific roles (e.g., Admins, Developers, Bridge Guardians) to improve the accuracy of its responses.\n\n### **1.5 Data Interactions and Transaction Support**\n\n- **Detailed Transaction Breakdown**: Provide clear explanations of on-chain transactions and their components to enhance user comprehension.\n- **Transaction Status Queries**: Enable users to check the status of their bridge transactions in real time, promoting transparency.\n- **Liquidity \u0026 Delay Updates**: Notify users about route availability, liquidity, and delays in bridge transactions to facilitate informed decision-making.\n\n### **1.6 Bridge Transaction Support**\n\n- **Transaction Status Queries**: Allow users to check the status of their bridge transactions in real time.\n- **Liquidity \u0026 Delay Updates**: Notify users about route availability, liquidity, and delays in bridge transactions.\n\n### **1.7 Transaction Decoding**\n\n- **Detailed Transaction Breakdown**: Provide detailed explanations of individual components of on-chain transactions.\n- **Guidance on On-Chain Data**: Help users navigate transaction data, liquidity positions, fees, and other on-chain interactions.\n\n---\n\n## **Priority 2: Customization \u0026 User Experience** (Estimated Time: 3-4 days)\n\n### **2.1 Custom Responses for User Groups**\n\n- **User-Specific Insights**: Provide personalized responses based on the user’s expertise (community members, developers, investors, traders).\n- **Developer Support**: Assist developers with guidance on smart contracts, migration, and the Across Protocol.\n\n### **2.2 Interactive Feedback System**\n\n- **Feedback on Responses**: Allow admins and other trusted users to review Ross's responses and provide feedback for improvements.\n- **Human Moderation**: Enable human oversight of Ross’s learning process to ensure high-quality answers and maintain community trust.\n\n---\n\n## **Priority 3: System \u0026 Efficiency Features** (Estimated Time: 1-2 days)\n\n### **3.1 Credit System**\n\n- **Rate-Limiting Access**: Implement a credit-based system that regulates how many queries a user can make within a certain timeframe. Users earn additional credits through community engagement.\n\n### **3.2 Integration with Notion**\n\n- **Knowledge Base Integration**: Connect Ross with Notion to store FAQs, summarized interactions, and learnings from community discussions for easy access by users.\n\n---\n\n## **Additional Information Required from Across Protocol**\n\n1. **Across Protocol Documentation**: Access to all technical guides, smart contracts, and migration documents for the Docs Explainer feature.\n2. **Bridge Transaction Data**: Access to APIs or data sources that track bridge transactions and provide liquidity updates.\n3. **Roles and Permissions**: Define which community members (Admins, Devs, Bridge Guardians, etc.) should be prioritized for Ross’s learning process.\n4. **Credit System Framework**: Determine how users earn and spend credits when interacting with Ross.\n5. **Data Analytics Requirements**: Define the key metrics users want to track for trading, liquidity, and token-related activities.\n6. **Access to Discord Server**: Grant permissions to integrate Ross into the Discord server and manage its interactions with different roles and channels.\n7. **Learning Cycle Configuration:** Channels and messages to monitor for daily learning cycles and parameters for selective memory.\n8. **User Roles and Permissions:** Definitions and access levels for different user roles (e.g., Admins, Developers, Community Members).\n9. **Feedback System Design:** Guidelines for feedback submission, review process, and human moderation. Like who can moderate what exactly??\n10. **Frequency of Doc updatation:** How frequently the documentation needs to be updated and how should Ross pull the updates.\n\n---\n\n## **APIs and Resources Needed**\n\n### **1. Blockchain \u0026 Wallet Management**\n\n- **Ethers.js / Web3.js**: For blockchain interactions and wallet management.\n- **Alchemy / Infura**: For accessing Ethereum nodes.\n- **Etherscan API**: For fetching transaction histories and on-chain data.\n\n### **2. Token Price \u0026 Market Data**\n\n- **CoinGecko API**: For token prices and real-time market data.\n- **CoinMarketCap API**: For tracking token prices across different chains.\n\n### **3. Across Protocol / DeFi-Specific APIs**\n\n- **The Graph API**: For querying Across Protocol data.\n- **Zapper API**: For tracking DeFi portfolios, liquidity positions, and more.\n\n### **4. Transaction Decoding \u0026 Analytics**\n\n- **Tenderly API**: For simulating transactions and decoding smart contract interactions.\n- **Zapper API**: For providing detailed insights on transactions.\n\n### **5. Natural Language Processing (NLP)**\n\n- **OpenAI GPT API**: For natural language generation, summarizing documents, and generating conversational responses.\n\n### **6. Feedback System \u0026 Knowledge Base**\n\n- **Notion API**: For storing and retrieving FAQs and knowledge base articles.\n\n---\n\n## **Questions for Client**\n\n1. **Financial Assistance**: What exactly should Ross assist with after wallet connection? Do you want Ross to provide suggestions based on transaction history, or just present the data?\n2. **Prioritizing Input**: What specific types of input from trusted members should be prioritized? Is it purely based on reactions like thumbs up/thumbs down?\n3. **Personal Assistance**: Should we use a RAG (Retrieval-Augmented Generation) model to implement personalized responses and role-based notifications?\n4. **DAO Integration**: Could you clarify what you mean by Ross being \"callable\" in DAOs? How should this feature work?\n5. **Document Updates**: How should Ross pull documentation updates? Should we connect to a specific repository or content management system for this?\n6. **Credit System Rules**: How should credits be allocated and spent? For example, how many credits should each query cost, and how do users earn additional credits?\n7. **Selective Memory**: What is the best approach to implementing selective memory? Should it only be based on specific roles, or should there be other factors (e.g., recency, accuracy)?\n\n---\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fprayag2003%2Facross-protocol-discord-bot","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fprayag2003%2Facross-protocol-discord-bot","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fprayag2003%2Facross-protocol-discord-bot/lists"}