TriggerX automates tasks across both Ethereum and TRON by deploying smart contracts on each chain. These contracts record and maintain the jobs created by users. Our backend, upon receiving new jobs, gets the keeper network to execute the tasks.
We leverage a decentralized network of keepers - independent nodes or actors responsible for monitoring on-chain events and executing tasks. These keepers monitor conditions on Ethereum and TRON blockchains and trigger task execution when the pre-set criteria are fulfilled.
Keepers in TriggerX are secured through a combination of smart contract logic and economic incentives. Smart contracts on both chains ensure that the keepers follow predefined protocols for task execution. Any misbehavior can be penalized through slashing mechanisms, where malicious or faulty keepers lose their stake.
Since the network of keepers is decentralized, no single point of failure exists, reducing the risk of manipulation or centralization. Multiple keepers can be assigned to monitor the same task, ensuring redundancy.
Keepers are rewarded based on the tasks they complete. The reward structure is typically tied to the gas fees and complexity of the task, ensuring that high-value tasks offer greater rewards, and all keepers are compensated appropriately for their work.
Yes, users can set their own triggers. TriggerX allows users to define conditions like price thresholds, specific time intervals, or events (like when a token reaches a certain price). These conditions are monitored by the keepers, who execute the tasks as soon as the triggers are met.
The system is highly flexible, allowing users to create various types of triggers.
Welcome to TRON Hacktron Season 7!
Your project, TriggerX, sounds fantastic, especially with its focus on cross-chain automation.
How do you plan to handle potential latency issues between Ethereum and TRON when executing time-sensitive tasks?
Also, what strategies do you have in place to ensure the security of automated tasks against malicious actors?
TriggerX sounds like an exciting leap for automation in the TRON network!
Iâm particularly interested in how you plan to handle cross-chain compatibility with Ethereum.
What challenges have you encountered in integrating the Keeper Networkâs functionalities, and how do you plan to address them?
Great questions! Handling latency between Ethereum and TRON for time-sensitive tasks is definitely a challenge we aim to overcome.
To handle that, we implement a robust cross-chain messaging protocol that minimizes delays. Additionally, we will deploy keepers with capability to interact with both chains to monitor and execute tasks, reducing reliance on cross-chain communication for urgent tasks. Prioritizing tasks and optimizing gas fees for quicker confirmations will also help ensure timely execution, even under high network traffic conditions.
We will implement metrics for tasks executed, and the keepers should adhere to those thresholds. Not achieving that would result in slash of stakes and eventual freezing of keeper from our network.
To ensure the security of automated tasks against malicious actors, we implement several key strategies:
Decentralized Keeper Network: By distributing task execution across a decentralized network of keepers, we avoid single points of failure and reduce the risk of collusion or manipulation.
Slashing and Penalties: Keepers are required to stake tokens, which can be slashed if they act maliciously. This economic incentive discourages misbehavior and ensures honest task execution.
Multi-Signature Verification: Critical tasks may require multiple keepers or validators to sign off on execution, ensuring that no single actor can hijack the process.
Monitoring and Alerts: Continuous monitoring of task execution ensures that anomalies are detected early, triggering automated alerts to admins and users for security.
We encountered some interesting challenges. Some of them are:
Cross-chain Communication: Our AVS is on Ethereum, with keepers working there. To extend their functionality on Tron blockchain. We modified the keepersâ configuration, our back end server to interact with Tron contracts.
Initially, we planned to use Layer Zero Protocol for implementing the back end architecture on Tron and Ethereum contracts only, but that led to unnecessary delay in messaging and high transaction costs. So we switched to Node.js back end.
Optimizing Job Fees: Optimizing the fees required for executing jobs was quite high as we have to include Ethereum transactions in the cycle.
We introduced a cap on fees, along with batching of transactions on Ethereum. Improving the economics in users favor is and will be a task we shall keep working on.
Performance Metrics: The keepers need to be monitored closely for security and efficiency reasons. Designing and implementing a performance metric was challenging. We use key metrics such as task execution time, success rate, and gas usage currently. If a keeper falls below any threshold fixed, they are frozen and asked to look into their execution. Of course, slashing is done on wrong execution of a task on top of metrics monitoring.
TriggerX is an impressive initiative for automating tasks in the TRON ecosystem!
Iâm impressed by the cross-chain capabilities and the integration with decentralized oracles for condition-based automation.
How will you ensure the reliability of the data for these tasks?
Our keeper network is a decentralized network. Any off-chain data will be verified using consensus mechanism. Such jobs will be assigned to quorum of keepers, and correct response shall be selected based on polling, ensuring that reliable data is provided to the users.
Itâss an impressive project!
Iâm curious, how do you plan to handle the fee structure to keep it attractive for users while ensuring fair rewards for keepers?
Welcome to Hackathon Season 7, KPRX Team! Your project, TriggerX, looks exciting and has the potential to significantly improve automation on the TRON network. Extending the Keeper Networkâs capabilities to TRON with cross-chain automation can open up new opportunities for developers and users alike. Iâm particularly interested in seeing how your project will enhance DeFi operations by reducing manual intervention and boosting network efficiency. All the best for the hackathon!
Users pay for the transaction fees we shall incur while performing jobs for them. We shall provide a decent estimate, which shall cover the job. If any amount is left, user can withdraw or use it for future jobs.
We are leveraging EigenLayer on Ethereum blockchain, which has programmatic incentives program, in which rewards are given to AVS, and their operators (keepers in our case) and staker based on performance and TVL in the AVS. EigenLayerâs economic security design is similar to Ethereumâs, operators are rewarded for execution or validation activities.
So keepers would also be awarded from this source.
We are also actively trying to improve the cost efficiency in certain ways:
Thank you so much for the warm welcome and encouragement! Weâre excited to showcase TriggerX and its cross-chain automation capabilities. Looking forward to sharing our progress throughout the hackathon!
Haha, appreciate the vote of confidenceâlooks like our professionalism is paying off! Weâll gladly take that vote in the DeFi category next week and make it count! Part of the grand master plan, right?
As for future plans⊠phew where do we start? Itâs a long list! Weâre talking more templates for every kind of automation you can imagine. Expanding cross-chain capabilities, boosting efficiency, tightening security, and making the UX even smoother. Plus, weâre all about helping new users get onboarded with some top-tier education. So yeah, weâre aiming for world dominationâbut in a super efficient, automated way.
Efficient scaling is crucial for maintaining reliability and user satisfaction, especially as your user base grows, and itâs also reassuring to hear that youâve proactively planned for scalability, particularly with task distribution across keepers and limits based on network capacity.
How will you communicate task limits to users, especially during periods when the network is at full capacity?
We plan to implement a clear and user-friendly warning system, similar to Ethereumâs high transaction fee alerts. During periods of high network congestion, users will be notified if the network is at full capacity, allowing them to decide whether to proceed.
Users can still create tasks during these times, but theyâll be informed that execution might be delayed. For those in a hurry, weâll offer an option to stake higher fee for priority task execution.
Transparency is keyâwe want users to feel in control, even in high-traffic periods!
TriggerX is an incredibly innovative project! The cross-chain automation capabilities between Ethereum and TRON are impressive, especially the seamless task automation without human intervention. Iâm excited to see how this will enhance operational efficiency on TRON, especially with DeFi tasks like staking and liquidations. Best of luck to the KPRX team as you continue to build and refine this amazing tool!
Welcome to Season 7! Excited to see TriggerX bring advanced automation to the TRON network. The cross-chain capabilities and enhanced efficiency will undoubtedly turbocharge the DeFi ecosystem. Looking forward to seeing this innovative solution in action!
Your project, TriggerX, looks exciting and has the potential to significantly improve automation on the TRON network. Extending the Keeper Networkâs capabilities to TRON with cross-chain automation can open up new opportunities for developers and users alike. Iâm particularly interested in seeing how your project will enhance DeFi operations by reducing manual intervention and boosting network efficiency. All the best for the hackathon! 
Weâll gladly take that vote in the DeFi category next week and make it count! Part of the grand master plan, right?
