{"signature": "0xd5c32e802a0c5c7d216f3965a3f3b92c71aff8f515c8b2775a7b43bfadeb52d37b46b197c6719adb2c6327accca935f917af43d40c2d1459aa4d65af6da4d4231c", "application": {"round": "0x20c94c8d87175abcac8892636cd23b25515e10f3", "answers": [{"type": "email", "hidden": true, "question": "Email Address", "questionId": 0, "encryptedAnswer": {"ciphertext": "rJcUAQSercmrgG6Zb/Yzdpblea+1e9CX8N655fPIDmhOsBMvgt8CTStKdIxvpK6r", "encryptedSymmetricKey": "c9805efe18ab25cc6b83c4c586975bb75594bdb8119336e81108028856f177a92c87833fd66d9f74d258ab61378cbf0f5f0184d542b866967c5f5159fcd2c874fa1bbd9761d24f87688573a647f0f91069b310d6598e332928517264cdf911a34138a30c2ba1f8f1f9e7f56d217f06cef8c19dc058c1ba28bced05624e965a75000000000000002001152d54080dd73c7e5fbc1c8d71bed596a67ae145ef02cc7452591204438702d21b4013043c059fd0d2216b65deebaf"}}, {"type": "short-answer", "hidden": true, "question": "Telegram Handle", "questionId": 1}, {"type": "short-answer", "answer": "https://github.com/trigg3rX/triggerx", "hidden": true, "question": "Project GitHub Repo", "questionId": 2}, {"type": "short-answer", "hidden": true, "question": "Link to your Public Group Chat", "questionId": 3}, {"type": "short-answer", "answer": "No", "hidden": true, "question": "Have you participated in a previous Gitcoin Grants Round? If so, please name the rounds or link the builder profile associated with previous rounds.", "questionId": 4}, {"type": "paragraph", "answer": "EigenLayer Micro Hacks Hackathon, June 2024 : https://docs.eigenlayer.xyz/eigenlayer/resources/avs-microhacks \n\nWinner Announcement - BuilOnEigen | Twitter Announcement : https://x.com/buildoneigen/status/1804495302746841160", "hidden": true, "question": "Which hackathon did your project participate in, and when? Please provide a link to your hackathon project page.", "questionId": 5}, {"type": "paragraph", "answer": "Since the last hackathon, TriggerX has undergone significant development, making it more robust, user-friendly, and scalable. Here’s an in-depth look at the milestones we've achieved:\n\n\nRebranding to TriggerX: We rebranded the project as \"TriggerX\" to reflect our mission of seamless task automation across multiple networks. This new identity aligns with our goal of providing advanced automation in decentralized finance (DeFi) and beyond. The name TriggerX embodies the project’s evolution from a prototype to a scalable solution for cross-chain automation.\n\n\nUI Development and User Experience Enhancements: In the initial version, TriggerX was a functional but minimal model without a user interface, limiting usability for non-technical users. Recognizing the need for an intuitive experience, we developed a full-featured UI to simplify task setup, management, and monitoring for users. This user interface provides straightforward access to TriggerX’s functionalities, making it easier to automate tasks without needing technical expertise. User’s have a dashboard available to them to monitor their jobs. We’re also working on additional UI tailored for keepers, which will help streamline registration and monitoring processes for network participants.\n\n\nIntegration of Multiple Keeper Functionality: The hackathon prototype operated with only a single keeper, limiting its ability to handle a high volume of tasks. Since then, we’ve scaled the architecture to support multiple keepers. This change was essential for handling larger workloads, distributing tasks efficiently across the network, and adding redundancy to enhance reliability, enhancing decentralisation and fault tolerance. \n\nMigration from Local Development to Testnet: A significant milestone was the transition from local development environment to public testnets. This move represents a crucial step toward production readiness, allowing us to test the system under more realistic network conditions. The testnet deployment enables proper validation of cross-chain interactions, keeper coordination, and transaction processing in an environment that closely mirrors mainnet conditions. This transition has been invaluable for identifying and resolving network-specific challenges that weren't apparent in local testing.\n\n\nCross-Chain Testing on OP Sepolia and TRON: Hackathon version was operating only on Ethereum network. Since then, we've expanded our testing to Optimism and Tron networks, allowing us to fine-tune TriggerX’s cross-chain functionality and ensure smooth operations across networks. This multi-network testing provides valuable insights into TriggerX’s scalability, enabling it to meet the demands of various DeFi ecosystems.\n\n\nCode Modularization for Maintainability: To make the project more maintainable and adaptable, we refactored and modularized the code structure. This approach simplifies code updates, promotes code reuse, and supports future expansions. The modularized structure also eases the integration of new functionalities, such as support for additional blockchains or more complex staking mechanisms.\n\n\nFee-Based Task Execution Model: To create a sustainable economic model, TriggerX operates on a fee-based structure. Each time a user sets up a task, they pay a nominal fee, which is then distributed among the keepers as an incentive. This model ensures ongoing compensation for keepers, fostering active participation in task execution.\n\nThese milestones have transformed TriggerX into a comprehensive, scalable solution that facilitates automated task execution across blockchain networks. Through ongoing testing, UI improvements, and an expanded keeper network, we are building a platform that offers reliable, decentralized automation with a user-friendly experience. TriggerX is now well-equipped to meet the growing demands of decentralized finance and beyond.", "hidden": true, "question": "Describe the progress and development of your project since the hackathon. What milestones have you achieved?", "questionId": 6}, {"type": "paragraph", "answer": "At its core, TriggerX is designed to empower the open-source community by extending the functionality of decentralized automation across blockchain networks. Our project not only utilises open-source technologies like Eigenlayer and Keeper Network but also actively builds upon it to introduce advanced, cross-chain automation capabilities. Here’s how TriggerX is contributing to the open-source ecosystem:\n\nEnhancing Decentralized Automation: By adapting and expanding the Keeper Network, TriggerX provides a flexible automation solution that can be applied across multiple chains. This adds significant value for developers looking to build cross-chain DeFi protocols without creating automation infrastructure from scratch.\nTriggerX’s open-source model invites other developers to build on top of or customise its functionalities, offering a foundation for innovations in multi-chain automation.\n\nSolving Cross-Chain Automation Challenges: The blockchain ecosystem currently faces significant limitations in interoperability and automation. Our solution bridges this gap by allowing decentralized, condition-based, event-based, and time-based tasks to operate seamlessly across chains, reducing the need for siloed, chain-specific tools.\nThis cross-chain flexibility helps foster an interoperable DeFi ecosystem, making it easier for open-source projects to introduce cross-network automation capabilities.\n\nEncouraging a Transparent, Community-Led Ecosystem: TriggerX operates on a fee model. With a staking and slashing mechanism, we create an accountability structure that rewards integrity and penalises malicious actions, fostering a secure and reliable automation solution.\nBy making this code available to the open-source community, we contribute a framework for decentralized task execution that prioritises both transparency and security—key values for any open-source project.\n\nFacilitating DeFi Development and Efficiency: With TriggerX, developers gain access to a robust, customizable automation service that significantly reduces operational overhead and complexity, enabling more efficient DeFi operations. \nOpen-source DeFi projects can leverage TriggerX to simplify routine tasks like staking, liquidity management, and price-based liquidations. This not only accelerates development but also enhances protocol efficiency.\n", "hidden": true, "question": "How does your project contribute to the OSS? What problem does it solve, or what value does it add?", "questionId": 7}, {"type": "paragraph", "answer": "As TriggerX evolves, our focus is on expanding compatibility, refining security mechanisms, and enhancing the overall automation experience. Below are the key areas we aim to develop further:\n\nNetwork Compatibility: We plan to expand TriggerX’s compatibility to support additional blockchain networks, enabling a truly cross-chain automation experience. This will allow seamless integration with popular and emerging blockchains beyond Ethereum, empowering users to automate tasks across a growing number of ecosystems and enhance interoperability.\n\n\nEnhanced Keeper Mechanism: To ensure the highest standards of security and reliability, we plan on introducing a Keeper Rating System that evaluates and ranks keepers based on their performance history, reliability, and consistency in executing tasks. Keepers with higher ratings will be eligible for greater incentivized rewards, encouraging all keepers to maintain top performance and contribute to the network's reliability. This system will be supported by a staking and slashing mechanism that penalises keepers for missed or failed tasks, further reinforcing accountability and network security.\n\n\nExpanded Automation Capabilities: TriggerX will continue to enhance its automation functionality by adding more sophisticated triggers. In addition to time-based, condition-based, and event-based automation, we aim to support complex conditional triggers (e.g., multiple conditions for execution) and integrate broader use cases, such as advanced DeFi applications, NFT operations, and cross-chain governance automation.\n\n\nImproved Analytics and Task Monitoring: We recognize the importance of transparency and control in automation. To support this, we’ll develop detailed analytics and monitoring tools that provide real-time insights into task statuses, success rates, keeper performance, and historical data. These tools will give users a deeper understanding of their automated tasks and optimise decision-making.\n\n\nSustainable Tokenomics: As we grow, our focus will be on implementing a sustainable tokenomics model that aligns the incentives of all participants. The introduction of Keeper X Token (KPRX) will continue to reward reliable task execution and support a self-sustaining ecosystem. By balancing token supply, fees, and rewards, we aim to ensure a long-term, value-driven economy within TriggerX that remains adaptable and resilient.\n\nThrough these developments, TriggerX is set to offer an increasingly robust, secure, and versatile automation platform for the decentralized finance ecosystem, driving adoption and efficiency across multiple chains.\n\nPlanned Allocation of Grant Funding\n\nOperational Support: Funds will be allocated to cover essential operational costs, including cloud infrastructure, development tools, and maintenance, ensuring continuous project momentum and stability. This investment supports the foundational resources needed to keep development and testing on track.\n\nTokenomics Modeling: A portion of the grant will be used to design a sustainable economic model for Keeper X Token (KPRX), focusing on aligning incentives effectively across users and keepers. This sustainable model will be essential for maintaining a self-sustaining ecosystem, where incentives drive long-term value and network growth.\n\nIncentive Program for Onboarding: To drive initial adoption, we’ll launch a strategic incentive program aimed at onboarding key participants—keepers (operators) and early users. This program will also reward our initial supporters, fostering an active, loyal community and setting a strong foundation for TriggerX’s growth.\n\n\nCommunity Education and Resources: Grant funds will support the creation of comprehensive educational materials, including tutorials, documentation, and user guides to help new users understand and adopt TriggerX. Additionally, we’ll establish an active online presence to engage with the community, provide support, and enhance user confidence and knowledge.\n", "hidden": true, "question": "What are your plans for further development, and how will the grant funds be used to achieve these goals?", "questionId": 8}, {"type": "paragraph", "answer": "0xc073A5E091DC60021058346b10cD5A9b3F0619fE, 11155420\n\nTJmohxC67WoA9GZyQK6Nwt85qpy5722BJL, 1001\n\n0xc073A5E091DC60021058346b10cD5A9b3F0619fE, 17000", "hidden": true, "question": "For any project deploying smart contracts on blockchain networks, please list all your deployer addresses and their corresponding blockchain networks. Use this format for each entry: [deployer_address], [chain_id]—for example, 0x123abc..., 42161 (This represents a deployer address on the Arbitrum network). Please include a separate line for each unique deployer address and blockchain combination.", "questionId": 9}], "project": {"id": "0xf43f0484bcd7afb2089b2e9da87eca40bef717a0d86dd98b696b24c9bc3e7356", "title": "TriggerX", "logoImg": "bafkreicedbscja7uvsekv4felzrqj3wxnyljw7v6bkik6nhqz54bp76ar4", "metaPtr": {"pointer": "bafkreicsan53fh2styygq3vznqgimxlsdd3eymkwf5ex2joafkie6ifvja", "protocol": "undefined"}, "website": "https://trigg3rx.vercel.app/", "bannerImg": "bafkreicnfrizj2ggv2v6gygv77idlhfltmbd4vzjybm5c34gjjzgnbnqda", "createdAt": 1730122606078, "userGithub": "Akash114", "credentials": {"github": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..nO4UrKpB5v4qRCMbizXshYn2tU1hP3g7S9bOjHEXX6MtGSknJhguw5gp2OuldU8MYXexJziVPTPmKKWo-IzvCA", "type": "Ed25519Signature2018", "created": "2024-10-28T16:43:38.078Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2024-10-28T16:43:38.078Z", "expirationDate": "2025-01-26T16:43:38.078Z", "credentialSubject": {"id": "did:pkh:eip155:1:0xD38874e814cc13Bc4e03317F4B1448a554dbF575", "hash": "v0.0.0:rlFezITo9kE6r/guf0GTnA1C+wGcj43lvcH/SbOFVQE=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextGithubOrg#trigg3rX#86950295"}}, "twitter": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..HJD8uOjKTrLNGjHUUD92m-jYwxSF82GysuNe3MNwTXnVlC0ADCwxutp1618QqXITAyk4Y8vpo_JhnqvF9mNGAA", "type": "Ed25519Signature2018", "created": "2024-10-28T16:46:12.063Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2024-10-28T16:46:12.063Z", "expirationDate": "2025-01-26T16:46:12.063Z", "credentialSubject": {"id": "did:pkh:eip155:1:0xD38874e814cc13Bc4e03317F4B1448a554dbF575", "hash": "v0.0.0:dHZo1oXglWCHdgWZgD5k93lywqnIkcKgYgtHKl1rPv4=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextTwitter#_TriggerX"}}}, "description": "TriggerX aims to bring advanced automation capabilities to other networks by extending the functionalities of Keeper Network. It shall utilise Keeper Network, an AVS developed on Ethereum using Eigenlayer, and forward its functionalities to the target network. Through this, we enable decentralized keepers to execute automated tasks based on time, conditions, or events across multiple chains.", "lastUpdated": 0, "projectGithub": "trigg3rX", "projectTwitter": "_TriggerX"}, "recipient": "0xD38874e814cc13Bc4e03317F4B1448a554dbF575"}}