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

Project Name: TriggerX - Ticks time, Triggers tasks, and Turbocharges TRON!

Project Track: DeFi

Team Name: KPRX Team

Team Members: 3 (@skye1 + 2)

DevPost Project Link: Trigg3rX | Devpost

Project Goal:

TriggerX aims to bring advanced automation capabilities to the TRON network by extending the functionalities of Keeper Network. It shall utilize Keeper Network, an AVS developed on Ethereum using Eigenlayer, and forward its functionalities to TRON. Through this, we enable decentralized keepers to execute automated tasks based on time, conditions, or events across multiple chains.

TriggerX will empower TRON developers and users by introducing seamless automation, thereby reducing manual intervention and enhancing operational efficiency on the blockchain.

Project Value:
TriggerX leverages both Ethereum and TRON ecosystems to create a cross-chain AVS solution for automating DeFi tasks and more. We transfer the utility of our existing Keeper Network (built on Eigenlayer) from Ethereum to TRON, bringing several benefits:

  • Cross-chain Automation: TriggerX allows decentralized keepers to monitor and execute tasks on the TRON network, similar to how it operates on Ethereum.
  • Decentralized Task Execution: Users can set up task automation for various DeFi operations on TRON, such as token swaps, staking, and price-based liquidations, which will be executed by keepers without human intervention.
  • Enhanced Network Efficiency: Automating time-based, condition-based, and event-driven tasks across TRON reduces operational complexity, boosts DeFi protocol efficiency, and opens up new possibilities for programmable automation.
  • Secure Keeper Network: With a staking mechanism, TriggerX ensures accountability, rewarding reliable task execution while penalizing malicious behavior, safeguarding network integrity.

Project Info:

  • TriggerX brings the power of decentralized automation to the TRON network by adapting a proven Ethereum AVS architecture. TriggerX enables smart contract interactions and monitoring to occur across Ethereum and TRON, ensuring a reliable, cross-chain automation service. The platform will support three main automation modes: time-based, condition-based (e.g., price feeds), and event-based (e.g., token transfers).
  • TriggerX will operate on a fee-based model for automating tasks. Users will pay a fee in TRX each time they set up a task for automation. These fees are then paid out to the keepers executing the tasks on Ethereum, ensuring a fair and decentralized reward mechanism.

Project Details:

Project Website: Trigg3rX | App

Project Test Instructions:

  1. Connect Your TronLink Wallet

  2. Navigate to the Create Job Page

  3. Fill Out the Job Creation Form

    • Job Type: Enter the type of job you want to create.
    • Timeframe: Specify the duration for which the job will run (in years, months, and days).
    • Contract Address: Input the address of the smart contract you want to interact with.
    • Contract ABI: ABI (Application Binary Interface) of the contract.
    • Target Function: Enter the function signature you want to call on the contract (e.g., getTask(uint256,uint256)).
    • Time Interval: Set the interval for the job (in hours, minutes, and seconds).
    • Argument Type: Choose the type of arguments you will be passing (None, Static, or Dynamic).
    • Arguments: If you selected Static, enter the arguments as a comma-separated list. If Dynamic, provide the API endpoint.
    • Demo Set of Values to test: These values are for a automation of linking a domain name to a wallet address, used in an app.
      • Contract Address: TN4MeYmA3CRmo6Uj6h4Yj2pPcnJiwGaFog
      • Target Function Signature: linkDomainToAddress(bytes32,address)
      • Argument Type: Static
      • Arguments: tronscan.nile.org,TEqqmXaynt9XmmcBNYbJh5tMVDmm183c2r
    • Some points to note are:
      • No spaces are allowed in the arguments.
      • The arguments are separated by commas.
      • Function signature should contain correct data types of values required.
      • The arguments types mentioned in function signature should be in the same order required by the function.
  4. Estimate the Fee

  5. Confirm Job Creation

  6. View Your Jobs

Additional Notes

  • Ensure that you have sufficient TRX in your wallet to cover the transaction fees.
  • If you encounter any issues, check the console for error messages.

Smart Contract links:

Project Milestones:

  • AVS Core Integration: :white_check_mark:
    • Develop the core AVS contract for task registration, validation, and interaction with EigenLayer. Deploy contracts on TRON to send instructions and receive updates.
  • Keeper Registration & Staking: :white_check_mark:
    • Implement the keeper registration system, including staking logic for slashing and participation.
  • Time-Based Automation: :white_check_mark:
    • Build cron-like scheduling tasks, executed at specific intervals. Utilize block timestamps for executing scheduled tasks.
  • Rewards & Slashing Mechanism: :white_check_mark:
    • Build smart contract logic for rewarding successful task execution and penalizing misbehavior. Incentivize keepers through TRX rewards and penalties.
  • Frontend Interface: :white_check_mark:
    • Develop a basic UI for task submission and monitoring for end-users. Simple and intuitive interface for managing tasks.
  • Testing & Debugging: :white_check_mark:
    • Comprehensive testing for all features, including AVS contracts, keeper logic, and UI functionality. Conduct unit testing, integration tests, and stress testing.
  • Mainnet Deployment: :hammer_and_wrench:
    • Final deployment of the MVP onto the TRON mainnet. Setup production infrastructure for Tron deployment.

Future Plans:

  • Expanding Automation Capabilities:
    • Condition-Based Automation: Integrate with decentralized oracles to monitor specific conditions, such as price feeds.
    • Event-Based Automation: Implement event listeners using TronWeb for monitoring Tron blockchain events, including token transfers and contract interactions. Monitor on-chain activities for event-driven automation.
  • Integrating BitTorrent Chain (BTTC): We plan to expand cross-chain capabilities by integrating BTTC to allow even greater flexibility in task automation across multiple blockchains.
  • Enhancing Keeper System: We will introduce more sophisticated staking and slashing mechanisms to further strengthen the reliability and security of the decentralized keepers.
38 Likes

Welcome to season 7
TriggerX revolutionizes Tron automation, bridging Ethereum and Tron ecosystems via layerzero protocol is truly fantastic and outstanding.
Kudos 2u all

5 Likes

Welcome to Hackathon Season 7.
My jaw dropped from reading your offering, a decentralized automation solution that harnesses cross-chain capabilities from Ethereum’s Keeper Network via the LayerZero Protocol just sounds like a cross-chain bridge to me.
Is there a plan to introduce dynamic fees based on network activity?

2 Likes

Welcome to the Hackathon of season 7, it is good to see another project in the defi track and I have also read everything that you write, please tell me are you planning to do education content that will help the new users to understand very well your platform, thank you

1 Like

Thanks so much for the warm welcome! We’re excited to bring TriggerX to life and push the boundaries of cross-chain automation.

Thanks for the enthusiasm! :blush: We’re thrilled you’re as excited as we are about TriggerX’s cross-chain potential.

As for dynamic fees, indeed, task fees will adjust based on network activity and the availability of keepers, as we are using Ethereum based network where it does. We’re still working the parameters, but the goal is to ensure a fair and efficient system for all users.

Absolutely, we plan to provide comprehensive guides for every step of the process. Our goal is to ensure users not only understand how to use TriggerX but also feel confident in what they’re achieving with our service. Clear, simple education is key to making decentralized automation accessible to everyone!

Welcome to Grand hackathon S7, really love your project and what you are building
But what would be the supply of KPRX (KeeperX Token) ? Has this token already been launched?

1 Like

It’s really getting interesting with each one of your reply to be honest. You mentioned adjustment of fees based on network activity, how frequently will the fee adjustments occur, and how will you ensure that this process remains fair and transparent to users?

1 Like

I will start by saying thank you for replying to me, I really like it that you are taking comprehensive guides and user education seriously, we all know that Tron is very global so please tell me are you having the plan to do your guide and tutorial in multiple other language you know so that people from different places in the world can also take part, thank you

1 Like

Greetings everyone! Love to see your thoughts and insights on our project.

Hmmm, its our first time designing tokenomics. What we have planned for testing is that user shall create jobs, and we calculate the points / tokens required. User shall then deposit that amount of tokens on TriggerX. For testing, on testnet, we shall provide faucet to users.

Large part of that will be dependent on Ethereum network fees and number of (operators) keepers registered on our AVS on Eigenlayer, along with the complexity and time period of job user creates. We shall be using straightforward calculations, with shall be made publuc and anyone can verify.

That would be a tough one, as my team is local. But we shall collaborate with others to publish guides in multiple languages. Initial interaction and information would be in English only.

1 Like

How do you plan to address potential fee volatility caused by fluctuations in Ethereum gas prices?

1 Like

From your project info

  • TriggerX brings the power of decentralized automation to the TRON network by adapting a proven Ethereum AVS architecture. Utilizing LayerZero, TriggerX enables smart contract interactions and monitoring to occur across Ethereum and TRON, ensuring a reliable, cross-chain automation service. The platform will support three main automation modes: time-based, condition-based (e.g., price feeds), and event-based (e.g., token transfers).
  • Tokenomics: TriggerX will operate on a fee-based model for automating tasks. Users will pay a fee in KPRX (KeeperX Token) each time they set up a task for automation. These fees are then paid out to the keepers executing the tasks on Ethereum, ensuring a fair and decentralized reward mechanism.

I will like you to explain on layerzero role in facilitating cross chain interaction between Ethereum and Tron, secondly will you ensure reliable task execution across chains.

1 Like

Your reply still confusing to, you mean the tokenomics has not been designed yet and which means your platform token has not not been launched yet?

3 Likes

Greetings Team KPRX and welcome to Tron Hackathon season 7. What you are building is good and I’ve developed interest in it. I just need clarity on some certain questions.

  1. What are the different automation modes supported by TriggerX, and how do they function?
  2. How does TriggerX’s staking mechanism ensure the security and reliability of the Keeper Network?
1 Like

Ok and I understand you very well

1 Like

Welcome to the hackathon season 7
I like what you are bringing to the blockchain space and to ensure that the network works in the best way, I have this question.

How do you choose keepers to execute tasks, how are they monitored to ensure that they act in the best interest of the users?

Are there any penalties for keepers who fail to execute tasks correctly?

1 Like

Yes, we agree that Ethereum’s gas prices are volatile, and our users may face the high fee when creating jobs. There will be a cap on fees, users need not pay the full fees each time. Also, we plan to batch the transactions on Ethereum to reduce fees further.

Its a work under progress, and the KPRX token has not been launched yet.

2 Likes

Layer Zero is a quite popular protocol for cross chain data and token transfer.
They provide endpoints for Tron Shasta testnet and mainnet. On Ethereum side, they cover Holesky testnet and mainnet. The Eigenlayer also supports Holesky, on which our AVS will work.

Layer Zero covers the networks we need. User shall create a job on Tron (JobCreator contract), whose data is sent to Ethereum, where a contract (Task Manager) creates tasks and operators (keepers) registered on AVS respond to that. Keepers execute the task on Tron, and AVS (ServiceManager contract) rewards/slashes them upon success/failure. This success / fail message is relayed back to Tron, where user can view on dashboard. Also, user can delete or update the job as per need, and this is also relayed using Bridge.

I realized most people are not aware of Eigenlayer and AVS, so follow my post below to know more.

Thanks for appreciation.

There are mainly 3 types of task we aim to include, namely:

  1. Time-Based Automation (Cron-like Jobs) - Schedule and execute tasks at regular intervals.

    • Examples: Scheduled token burns, recurring payments, and interest accruals.
    • Users would enter the Contract address and target function, if any, to call by the keeper at time specified by user.
  2. Condition-Based Automation (Triggering on Specific Conditions) - Execute tasks when predefined conditions are met.

    • Examples: DeFi liquidations, automated trading, and yield re-balancing based on price or collateral ratios.
    • User provides the conditions and means to monitor them (Oracles or APIs to apps), when they are triggered, Keepers perform the task.
  3. Event-Based Automation (Responding to On-Chain Events) - Trigger actions in response to specific blockchain events.

    • Examples: NFT minting upon milestone achievement, token distribution after sales, and governance actions when proposals reach quorum.
    • Similar to time based, a contract address and target function by user is provided. Keepers listen to events at those address or blockchain, and executes the task assigned by user when event occurs.

All these will require the user to create contracts and APIs (if needed) as per our specifications, which we shall provide in detail.

1 Like