- Web3 Wallet Integration: Enable users to connect their wallets and access balances and transaction histories.
- Blockchain Data Insights: Provide real-time token prices, transaction histories, and other financial data.
- User-Specific Insights: Tailor responses based on user expertise (community members, developers, investors, traders) to ensure relevance and enhance engagement.
- Developer Support: Offer specialized guidance for developers on smart contracts and Across Protocol navigation.
- Blockchain Data Analytics: Deliver insights into trading trends, protocol metrics, liquidity positions, and token activity for informed investment and trading decisions.
- Docs Explainer: Simplify and explain Across Protocol documentation to support community understanding.
- 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.
- Selective Memory: Ross will prioritize learning from specific roles (e.g., Admins, Developers, Bridge Guardians) to improve the accuracy of its responses.
- Detailed Transaction Breakdown: Provide clear explanations of on-chain transactions and their components to enhance user comprehension.
- Transaction Status Queries: Enable users to check the status of their bridge transactions in real time, promoting transparency.
- Liquidity & Delay Updates: Notify users about route availability, liquidity, and delays in bridge transactions to facilitate informed decision-making.
- Transaction Status Queries: Allow users to check the status of their bridge transactions in real time.
- Liquidity & Delay Updates: Notify users about route availability, liquidity, and delays in bridge transactions.
- Detailed Transaction Breakdown: Provide detailed explanations of individual components of on-chain transactions.
- Guidance on On-Chain Data: Help users navigate transaction data, liquidity positions, fees, and other on-chain interactions.
- User-Specific Insights: Provide personalized responses based on the user’s expertise (community members, developers, investors, traders).
- Developer Support: Assist developers with guidance on smart contracts, migration, and the Across Protocol.
- Feedback on Responses: Allow admins and other trusted users to review Ross's responses and provide feedback for improvements.
- Human Moderation: Enable human oversight of Ross’s learning process to ensure high-quality answers and maintain community trust.
- 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.
- Knowledge Base Integration: Connect Ross with Notion to store FAQs, summarized interactions, and learnings from community discussions for easy access by users.
- Across Protocol Documentation: Access to all technical guides, smart contracts, and migration documents for the Docs Explainer feature.
- Bridge Transaction Data: Access to APIs or data sources that track bridge transactions and provide liquidity updates.
- Roles and Permissions: Define which community members (Admins, Devs, Bridge Guardians, etc.) should be prioritized for Ross’s learning process.
- Credit System Framework: Determine how users earn and spend credits when interacting with Ross.
- Data Analytics Requirements: Define the key metrics users want to track for trading, liquidity, and token-related activities.
- Access to Discord Server: Grant permissions to integrate Ross into the Discord server and manage its interactions with different roles and channels.
- Learning Cycle Configuration: Channels and messages to monitor for daily learning cycles and parameters for selective memory.
- User Roles and Permissions: Definitions and access levels for different user roles (e.g., Admins, Developers, Community Members).
- Feedback System Design: Guidelines for feedback submission, review process, and human moderation. Like who can moderate what exactly??
- Frequency of Doc updatation: How frequently the documentation needs to be updated and how should Ross pull the updates.
- Ethers.js / Web3.js: For blockchain interactions and wallet management.
- Alchemy / Infura: For accessing Ethereum nodes.
- Etherscan API: For fetching transaction histories and on-chain data.
- CoinGecko API: For token prices and real-time market data.
- CoinMarketCap API: For tracking token prices across different chains.
- The Graph API: For querying Across Protocol data.
- Zapper API: For tracking DeFi portfolios, liquidity positions, and more.
- Tenderly API: For simulating transactions and decoding smart contract interactions.
- Zapper API: For providing detailed insights on transactions.
- OpenAI GPT API: For natural language generation, summarizing documents, and generating conversational responses.
- Notion API: For storing and retrieving FAQs and knowledge base articles.
- 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?
- Prioritizing Input: What specific types of input from trusted members should be prioritized? Is it purely based on reactions like thumbs up/thumbs down?
- Personal Assistance: Should we use a RAG (Retrieval-Augmented Generation) model to implement personalized responses and role-based notifications?
- DAO Integration: Could you clarify what you mean by Ross being "callable" in DAOs? How should this feature work?
- Document Updates: How should Ross pull documentation updates? Should we connect to a specific repository or content management system for this?
- 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?
- 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)?