TriggerX: Ticks time, Triggers tasks, and Turbocharges TRON!

TRON Hackathon Hackathon Season 7
82

Good work, Keep going!!

1 Like
83

@kishan1729 @manfred_jr @Lisa1 @ines_valerie @ArtQuest @tonystark @sc_00804

Thank you all so much for the incredible support and encouragement! :pray::tada: We’re thrilled that you’re enjoying the updates and recognizing the hard work we’ve been putting in. The job scheduling changes and increase in keepers were definitely game-changers, and we can’t wait to showcase everything in action! :rocket: Your feedback means a lot to us, and we’ll definitely check out your projects as well—let’s push through and make the most of voting! :muscle::fire: Keep building, and thanks again for all the love!

5 Likes
84

Welcome! Excited to see your updates and the impact of the job scheduling changes. Your hard work is inspiring—let’s make the most of voting together!

1 Like
85

thanks for the update, keep building

1 Like
86

Dynamic fees will adjust based on network activity and keeper availability, which is essential for maintaining an efficient system. It would be beneficial to communicate how often these adjustments will occur and outline the criteria used for setting fees. Transparency is key, so providing users with regular updates or a dedicated resource on fee structures could help build trust. Additionally, having mechanisms in place to address concerns about fairness would enhance user confidence in the system.

1 Like
87

Hardwork barely goes unnoticed, so the support is only testament to your level of consistency.

2 Likes
88

You are working very very hard, keep it up

1 Like
89

Wow!

EigenLayer being used for TRON is the kind of collaboration that the industry requires.

I wish your project goes live and developers get to use TriggerX in the next season & saves their development time.

:tada:

4 Likes
90

Great project! TriggerX is bringing some impressive automation tools to the TRON network—can’t wait to see it in action. All the best to the KPRX Team! :rocket:

1 Like
91

I bet this project is gonna be No 1 in judging :slight_smile: (Or maybe 2)

1 Like
92

Hello @skye1

Your product is meant to be used by the masses but imo the explanations are way too difficult for the majority. What’s keeper? AVS? Egenlayer?
If you want to maximise your chances to get a lot of votes the description should be simplified so even new web3 users can understand what the product does exactly and how to use it.

Small example: “fill ABI” → explain where to find the ABI. What about contracts that haven’t been verified? Is there an alternative?

KISS → keep it stupid simple

4 Likes
93

I have a few questions I’d like to ask, but I feel these points are particularly important for the TRON and BTTC communities to consider before fully utilizing your product. While TriggerX offers exciting potential for automation on TRON, there are several key areas I think the community would benefit from understanding further:

  1. How does TriggerX intend to monitor and mitigate any potential security risks within the keeper network itself, ensuring that keepers consistently perform tasks without compromise, especially in the event of network congestion or malicious attacks?

  2. Will there be a dynamic pricing model for task automation based on frequency, complexity, or other factors? How will TriggerX make sure that pricing remains fair and affordable, particularly for users who require high-frequency tasks or complex automation setups?

  3. As usage scales, what mechanisms are in place to prevent potential bottlenecks, such as high keeper demand or delays in task execution? Will there be prioritization or load-balancing mechanisms to manage high-demand periods effectively?

  4. In the case of unexpected downtimes or failures in keeper nodes, what backup or failover strategies does TriggerX have in place to ensure continuous service and prevent task disruptions?

  5. For users who are new to blockchain automation, does TriggerX plan to provide educational resources or onboarding guides? How will you ensure that non-technical users are confident and informed when using TriggerX for task automation?

  6. With rewards provided in TRX, how does TriggerX plan to maintain the economic stability of the reward model if TRX experiences high volatility? Will there be alternative reward structures to safeguard the reliability and security of the keeper system?

  7. What is the timeline or roadmap for TriggerX’s expansion to other blockchains beyond TRON and BTTC? Are there specific chains or ecosystems that TriggerX prioritizes in its cross-chain vision?

  8. Will TriggerX offer real-time monitoring, notifications, or error reporting for users to track the status of their automated tasks and address any potential issues promptly?

  9. To what extent will users be able to customize task conditions and execution parameters? Are there options for advanced customization to cater to a wider range of DeFi automation use cases?

  10. How does TriggerX plan to navigate potential regulatory challenges that may arise around automated DeFi services, particularly as cross-chain integrations and task automations expand?

1 Like
94

Interesting project to be honest!

I do not have the knowledge to exactly understand but I got that is a scheduler that executes tasks - and by task you mean triggering a smarty contract , any contract?

What will be the difference from implementing a self triggering with simple cron for example?

Thanks @skye1

1 Like
95

Hi team are you there? No updates since few days. I think your project can be useful for some.

1 Like
96

Thanks for the valuable feedback, @fabsltsa!

We agree—clear, accessible explanations are crucial, especially for new users in Web3. While we do have some initial test instructions available in our post and on Devpost, we recognize that the UI could benefit from more built-in guidance. For now, following the provided instructions should help users navigate the platform.

We’re actively working on enhancements, including a new Explore Page with tutorials and blog content tailored to new users. Additionally, we’re developing a Template Page that will allow users to select from various automation types, simplifying the onboarding process.

As for the ABI input, we’ve streamlined it on testnet: users only need to provide the contract address, and the system fetches the ABI automatically. For mainnet deployment, we’ll review this further to ensure it’s intuitive and aligned with user needs—even when contracts aren’t verified.

Appreciate the reminder on the KISS principle! It’s a solid approach, and we’ll definitely keep it in mind as we continue to improve. Thanks again for your insights!

1 Like
97

Thanks for the interest and great question!

Yes, it’s essentially a task scheduler, where any user can set up automated tasks. Right now, it supports basic contract calls on TRON, but what sets it apart is our focus on cross-chain and dynamic capabilities. While a simple cron job can trigger tasks, it’s limited by the network it’s running on and lacks the flexibility needed for complex, multi-chain operations.

We’re aiming to expand TriggerX to support more advanced DeFi automations, like automated swaps, liquidity rebalancing, liquidation protection, and much more. Stay tuned as we continue building—we have some exciting features in the pipeline! Thanks again for your question and support!

1 Like
98

Thank you for these thoughtful questions! Each of these points is essential as we work to make TriggerX a secure, efficient, and user-friendly platform. Here’s an overview of how we’re addressing each area:

  1. Security in the Keeper Network:
  • Ensuring the security of our keeper network is a top priority. We’ve built a system where keepers stake assets, which can be partially or fully forfeited if they fail tasks or act maliciously. During network congestion or attacks, keepers are allocated in a way that balances the workload, reducing risk. We also have real-time monitoring and validation in place to catch issues early.
  1. Dynamic Pricing Model:
  • We’re designing a dynamic pricing model for task automation, adjusting based on factors like task frequency and complexity. Higher-frequency or resource-intensive tasks will have fees reflecting their usage, while routine tasks remain affordable. This will help keep TriggerX accessible to all users while ensuring the system’s sustainability.
  1. Scalability and Bottleneck Prevention:
  • To handle high keeper demand, we use load-balancing and task prioritization. During peak times, tasks are queued and executed in priority order. Although we haven’t implemented a priority fee mechanism yet, we’re working on it so users can eventually pay an additional fee to prioritize their tasks. As we grow, we’ll also scale up the keeper network to prevent bottlenecks and ensure smooth service.
  1. Backup and Failover Strategies:
  • In case of any unexpected downtime or keeper node failures, we plan to implement standby keeper nodes as backups. If a primary keeper has issues, these backup nodes will take over to prevent interruptions. A task retry mechanism will also ensure that tasks resume after any temporary downtime.
  1. Educational Resources for New Users:
  • For users new to blockchain automation, we’re creating onboarding guides, tutorials, and other interactive resources. We’re also building an Explore Page and knowledge hub with step-by-step instructions for setting up automations. Our goal is to make the learning curve easier and help users at all skill levels manage tasks with confidence.
  1. Economic Stability of TRX Rewards:
  • To manage potential volatility in TRX rewards, we’re exploring options to stabilize our reward model. This could involve pegging rewards to a stable value or creating a tiered reward structure. By making rewards predictable, we can better support keepers, even if TRX prices fluctuate.
  1. Timeline for Cross-Chain Expansion:
  • While we’re focused on TRON and BTTC right now, we plan to expand to other major DeFi blockchains, prioritizing Ethereum, Binance Smart Chain, and Polygon. Our roadmap includes gradual steps to integrate new chains, so TriggerX can offer smooth cross-chain functionality as we grow.
  1. Real-Time Monitoring and Notifications:
  • Real-time monitoring and notifications are a key future feature for TriggerX. Users will be able to track task status, get alerts for any issues, and access a dashboard with performance updates, so they can quickly respond to any problems.
  1. Customization for Task Conditions and Parameters:
  • TriggerX will eventually offer more extensive customization options, so users can define detailed task conditions and parameters. Advanced options will allow users to automate strategies like setting price thresholds or transaction timing, making TriggerX flexible for various DeFi scenarios.
  1. Navigating Regulatory Challenges:
  • As DeFi automation grows, we’re keeping an eye on regulatory developments to ensure TriggerX remains compliant. Our expansion will follow standards for transparency, security, and regulatory adherence to adapt smoothly as the ecosystem evolves.

We appreciate your insights and are committed to building a robust, accessible platform. Thanks to the community’s input, we’re excited to keep bringing TriggerX to the next level!

99

Thank you so much! We’re thrilled to bring EigenLayer’s capabilities into TRON through TriggerX. Collaborations like this are exactly what drive innovation in the space, and we’re excited to see the positive impact it can have for developers.

Thank you for the encouragement! We’re excited to bring TriggerX’s automation tools to life on TRON and can’t wait to show you everything in action. Big thanks from the KPRX Team for the support! :rocket:

100

Haha, we’ll gladly aim for No. 1! :smile: But hey, we’ll take a strong No. 2 if that’s what it comes down to. Thanks for the vote of confidence—it keeps us pushing forward! :rocket::muscle:

101

Yes, apologies for going quiet! We got caught up in the Festival of Lights celebrations. Rest assured, we’re still hard at work and have some exciting updates coming soon—thank you for checking in! :sparkles::blush:

1 Like