[2511 Grant Proposal] AutomationX – The AI-Powered Automation Layer for Rootstock DeFi

Grants & Incentives
1

Grant Proposal: AutomationX – The AI-Powered Automation Layer for Rootstock DeFi

Applicant: AutomationX Team
Grant Program: Rootstock Strategic Grants
Requested Funding: US$12,000
Proposed Timeline: 24 weeks
Categories: DeFi & Cross-Chain Automation, AI Integration, Developer Ecosystem

1. Project Summary

AutomationX is an AI-powered, modular automation protocol designed to serve as the “Zapier for the Rootstock ecosystem.”

It empowers users to execute complex DeFi strategies using simple natural-language commands (e.g., “When BTC price drops 5%, swap my RIF to rUSDT and lend on Tropykus”).

By abstracting away technical complexity, AutomationX makes Rootstock DeFi accessible to non-technical Bitcoin holders, drives capital inflows through automated cross-chain bridging, and provides an open-source SDK for developers to build and deploy their own automation modules.

This project will deliver:

  • An AI-Powered Automation Engine: Autonomously executes user instructions based on on-chain and off-chain triggers.

  • Cross-Chain Liquidity Bridge: Seamlessly brings ERC-20 assets from Ethereum into the Rootstock DeFi ecosystem.

  • A Modular, Open-Source Framework: Allows third-party developers to easily build and integrate new automation strategies.

  • A Developer SDK: Empowers the entire Rootstock community to contribute to a growing library of automation tools.

By funding AutomationX, Rootstock is not just funding a product; it is investing in foundational infrastructure that will unlock new users, attract significant TVL, and create a self-sustaining flywheel of developer activity.

2. Team Background

The AutomationX team is composed of seasoned Web3 builders with a proven track record in DeFi, AI, and scalable infrastructure. Our collective experience ensures we can deliver on this ambitious project with lean efficiency.

Ankit Choudhary (Blockchain & DeFi Lead):
Ankit brings 4+ years of deep expertise in smart contract architecture and DeFi protocol security. He has led the development of financial systems designed for high-value transactions.

Akash (Full-stack & AI Lead):
A previously successful exited founder, Akash has over 4 years of experience building autonomous agents and Web3 analytics platforms. His expertise lies in translating complex logic into reliable, AI-driven execution systems.

Dhruv Gera (Web3 & Infrastructure Lead):
A previously successful exited founder, Dhruv specializes in building scalable, resilient backend systems. With 3+ years in the DeFi space, he has architected infrastructure built to handle high-throughput, mission-critical operations.

Our team’s combined 8+ years of hands-on experience building and scaling successful Web3 products gives us the unique capability to build this critical infrastructure for the Rootstock ecosystem.

3. The AutomationX Value Proposition for Rootstock

AutomationX creates a powerful adoption flywheel, turning Rootstock into the premier destination for Bitcoin-secured DeFi.

AutomationX → The Rootstock DeFi Adoption Flywheel

By launching a user-friendly automation layer, AutomationX becomes an onboarding magnet for capital and developers, boosting on-chain activity and cementing Rootstock’s position as the leading Bitcoin sidechain.

How AutomationX Addresses Key Rootstock Challenges

Challenge How AutomationX Solves It
High Barrier to Entry for Mainstream Users Our natural language interface allows non-technical Bitcoin holders to access sophisticated DeFi strategies without needing to understand smart contracts or manually execute transactions.
Limited Cross-Chain Liquidity & Friction The integrated, automated bridge makes it effortless to move capital from Ethereum to Rootstock, directly increasing TVL in ecosystem protocols like Sovryn, Tropykus, and MoneyOnChain.
Need for More Developer Activity & Tools Our open-source SDK and modular architecture provide a powerful toolkit for Rootstock developers, encouraging them to build, innovate, and contribute to a shared, growing library of automation modules.
Underexposed Utility of Core RSK Components AutomationX strategies will directly utilize assets like RIF, RBTC, and RNS, embedding them into automated workflows and increasing their on-chain velocity and utility.

4. Milestones, Timeline, and Budget

Our plan is structured for rapid, iterative delivery with clear, measurable outcomes at each stage.

Milestone Deliverables Timeline Budget
M1: Automation Core (Testnet) 1. Core smart contracts on RSK testnet.2. NLP interface for command input.3. UI dashboard for task monitoring.4. Integration with 2 testnet DeFi protocols. 6 weeks $4,000
M2: AI Engine & Bridge Integration 1. ERC-20 <> Rootstock bridge on testnet.2. Live AI agent for intent parsing.3. Chainlink Automation integration.4. Performance & stress testing completed. 8 weeks $4,000
M3: Mainnet Launch & Developer SDK 1. Full deployment on Rootstock mainnet.2. Open-source SDK published on GitHub.3. Developer workshop hosted.4. Integration with ≥3 mainnet protocols. 10 weeks $4,000
Total 24 weeks $12,000

5. Success Metrics

KPI 30-Day Target (Post-Launch) 90-Day Target (Post-Launch) Data Source
Automated Transactions Executed 500+ 2,500+ On-Chain Data
Unique Wallets Using AutomationX 100 500 AutomationX Dashboard
TVL Bridged via AutomationX $50k $250k+ Bridge Contract
Developers Using/Forking SDK 15 50+ GitHub
Integrated Rootstock Protocols 3 5+ Project Docs

6. Return on Investment (ROI)

This $12,000 grant is a high-leverage investment in foundational infrastructure. The ROI for Rootstock will be delivered through three primary channels:

1. Direct Capital Inflow:
Based on our 90-day target of attracting $250k+ in TVL, this grant yields an immediate 20x+ return on capital brought into the ecosystem. This directly benefits all Rootstock dApps by increasing available liquidity.

2. Increased Network Activity:
With a target of over 2,500 automated transactions in the first 90 days, AutomationX will generate significant, sustained on-chain activity, increasing network fee revenue and demonstrating a vibrant, active ecosystem.

3. Developer Ecosystem Multiplier:
The SDK empowers the entire community. By funding this one project, Rootstock seeds an ecosystem where dozens of developers can build new products and strategies, creating a compounding return in ecosystem growth and innovation that far exceeds the initial grant amount.

For a modest $12,000 investment, Rootstock acquires a critical piece of infrastructure that makes the entire ecosystem more attractive to users, capital, and developers.

7. Technical Specifications

  • Frontend: React, Wagmi, Tailwind CSS → Deployed on Vercel

  • On-Chain (Rootstock): Solidity smart contracts (OpenZeppelin standards) for task scheduling, module registry, and execution

  • Off-Chain Services:

    • AI & NLP Engine: Node.js service using GPT libraries for intent parsing and module selection

    • Event Listener & Trigger: Go-based service monitoring on-chain events and off-chain APIs (e.g., price feeds)

    • Cross-Chain Relayer: Secure service for handling bridge events and submitting transactions

  • Infrastructure: Microservices architecture hosted on AWS/GCP, managed with Kubernetes for scalability

  • Monitoring: Grafana for system health, Forta for on-chain security alerts

  • Security: Smart contracts will undergo static analysis (Slither), internal QA, and a professional audit (budget permitting)

8. Demo

Thank you for your consideration.
We are confident that AutomationX will be a game-changer for Rootstock, unlocking its potential as the leading DeFi hub for Bitcoin.

Respectfully,
The AutomationX Team

2 Likes
2

Hey @ankit7241,

Interesting project. I have a few questions, if I may:

  1. I couldn’t find your profiles online. Could you share your LinkedIn profiles?
  1. Can you clarify about this integrated, automated bridge, and its technical foundation?
  1. Can you clarify about RNS usage into these workflows?
  1. Can you elaborate on how you got to these 30- and 90-day targets?
  1. These links seem to be broken. can you take a look?

https://automationx-zeta.vercel.app/
https://github.com/yourdevkalki/rootstock-agent

  1. Looking at the video demo, it’s not clear how the transaction signing works. More specifically, when does it happen?
    Do you approve spending of just the asset and value intended, after your prompt, or you give a pre-approval to spend your assets by your future prompts?
2 Likes
3

Thank you @ankit7241 for presenting a thoughtful and ambitious proposal to bring AI-powered automation to Rootstock DeFi. We see potential in lowering technical barriers and enabling more users to participate in complex DeFi strategies through natural-language commands. However, several areas require further clarification to ensure the project’s success and sustainability.

One key concern is the technical feasibility of the automation engine and cross-chain bridge. The proposal outlines high-level goals but does not provide enough detail on how the system will handle ambiguous or conflicting user instructions, nor how it will mitigate risks associated with cross-chain asset movement or DeFi protocol integrations. Could you elaborate on the architecture, error handling, and security measures planned for both the automation engine and the bridging component?

Another important aspect is the economic sustainability of AutomationX beyond the initial grant. While the funding request is modest, there is no breakdown of how resources will be allocated or how ongoing maintenance and development will be supported after the 24-week period. What is your plan for ensuring the protocol’s long-term viability, including potential revenue models or community funding mechanisms? In addition to that, similar to @ChronoTrigger 's feedback, how do you plan to achieve the target goals without explicit milestones that promote the protocol?

2 Likes
4

Good points from @ChronoTrigger and @Tane, I had similar thoughts while reading.

One thing I wanted to clarify: you mention Chainlink Automation integration in Milestone 2. From what I can see, Chainlink Automation doesn’t appear to be active on Rootstock yet, are you referring to a planned deployment, or did you mean something else by that integration?

Also, regarding the audit, since it’s listed as “budget permitting,” how are you planning to handle security review within the current scope, external audit, internal QA, or community testing?

The overall direction is promising, just trying to understand the technical setup a bit better.

3 Likes
5

Using AI to simplify DeFi is an exciting and important goal for the Rootstock ecosystem. I’m particularly interested in clarification on the user experience, as well as @Tane ‘s point about the long-term sustainability plan for after the grant period. It would also be great to get a bit more background on the team and to see updated demo and GitHub links. I appreciate the ambition of the project and look forward to your clarifications.

1 Like
6

Hello @ankit7241. To echo others, please provide working links to your demo and github repo. It would also be helpful to see your team’s social media profiles and additional links that show your prior work.

Additionally, could you share how you intend to achieve the target of 2,500 automated transactions within the first 90 days? For example, do you already have partnerships in place with existing Rootstock dApps?

Overall, the direction of the project is promising. That said, given that user funds will be handled, strong security practices and a rigorous technical implementation will be essential.

7

Hi @ChronoTrigger — thank you for taking the time to review our proposal and for the detailed questions. I’ll address each point below:

Team Profiles :

Here are our team’s verified profiles:

Ankit – https://www.linkedin.com/in/ankit7241

Akash – https://www.linkedin.com/in/akash-sharma-636aa51a0

Dhruv Gera – https://www.linkedin.com/in/dhruv-gera

We’ll update these links in the main post as well for visibility.

Integrated, Automated Bridge — Technical Foundation :

The cross-chain bridge in AutomationX is designed to build on Rootstock’s existing Token Bridge infrastructure:

Rootstock already enables ERC-20 ↔ RRC-20 bridging between Ethereum and Rootstock through a secure, federated multisignature model (RSK Token Bridge Docs).

AutomationX will not replace or recreate this bridge; instead, it will integrate bridge operations into automation workflows. For instance:

“If BTC drops 5%, bridge my USDT from Ethereum and lend on Tropykus.”

Technically, the automation engine listens for bridge confirmation events and executes downstream DeFi transactions once the cross-chain transfer completes.

The automation logic runs through verified smart contracts, ensuring all bridge interactions remain fully transparent and non-custodial.

This approach leverages Rootstock’s proven interoperability layer while adding automation logic to increase capital flow and TVL across the ecosystem.

RNS in Automation Workflows :

RNS (Rootstock Name Service) will serve as a usability and identification layer within AutomationX:

Each automation module or strategy can be assigned an RNS subdomain such as auto.username.rsk.

This allows both users and dApps to reference strategies through readable identifiers rather than raw addresses.

It also directly embeds Rootstock-native assets (RIF and RNS) into automation flows, increasing their on-chain velocity and practical use cases.

30-Day & 90-Day Targets — Basis :

The current KPIs are projections based on our ETHIndia 2025 MVP performance and ecosystem growth potential — not inflated user metrics.

At ETHIndia, our prototype successfully demonstrated the end-to-end automation logic: intent parsing → on-chain condition monitoring → DeFi action execution.

The project was built within a short timeframe and tested primarily by our team during the hackathon; no public wallet onboarding took place.

For Rootstock, the 30-day and 90-day targets are modeled on reasonable adoption patterns seen in early DeFi automation tools (e.g., Gelato, Keep3r).

These targets represent achievable, data-driven projections rather than current usage metrics, and will be adjusted based on testnet feedback and user engagement post-launch.

Links & Demo :

The URLs you mentioned were temporary MVP deployments from the ETHIndia hackathon.

Those were built for live judging and are no longer active.

For reference, the official ETHGlobal project page with our documentation and video demo is here:

:link: https://ethglobal.com/showcase/automationx-etqcb

We’re currently refactoring the architecture for Rootstock integration, and all updated repositories will be made public once the contracts and UI reach testnet stability.

Transaction Signing Flow :

In the ETHIndia MVP, the transaction signing flow was intentionally simplified for demonstration purposes. The production design for Rootstock will work as follows:

Users grant explicit, limited approvals only for the specific asset and value defined in their automation strategy.

When the predefined condition (e.g., price drop, yield trigger) is met, the automation contract executes using that pre-approved allowance only.

No blanket pre-approvals or custodial permissions will ever be granted to the system.

This ensures full user custody and minimizes exposure — consistent with practices from established DeFi automation frameworks.

Thank you again for the thoughtful questions — I appreciate the detailed review.

Your feedback helps us refine AutomationX to better serve the Rootstock ecosystem.

— AutomationX Team

8

Hi @Tane — thank you for the thoughtful and detailed feedback. These are exactly the questions we’ve been focusing on internally as we refine the architecture. I’ll address each point clearly below.

1. Technical Feasibility and Architecture Overview

AutomationX is designed as a modular, event-driven automation framework operating on top of Rootstock’s EVM-compatible infrastructure.

At a high level, it consists of four coordinated components:

1. Intent Parser (AI Layer):

  • Built on top of lightweight GPT-based models (running off-chain).

  • Converts user natural-language instructions (e.g., “Bridge my USDT from Ethereum when BTC drops 5% and lend on Tropykus”) into a structured JSON “intent graph.”

  • Every output must conform to a strict JSON schema. If the command is ambiguous (e.g., missing target value or protocol), the parser rejects it and prompts the user for clarification.

  • This ensures no autonomous or arbitrary instruction execution — users always review parsed instructions before signing.

2. Automation Core (On-Chain Contracts):

  • Deployed on Rootstock; handles validated task creation, trigger registration, and condition checks.

  • Inspired by frameworks like Gelato Ops and Chainlink Automation, with Rootstock-optimized event monitoring.

  • Uses condition contracts that emit predefined events when an off-chain or on-chain trigger is satisfied.

3. Execution Layer (Off-Chain Executors):

  • A monitored off-chain service listens for on-chain and off-chain trigger events (e.g., oracle price updates, bridge confirmations) and executes corresponding actions through verified contracts.

  • During the MVP phase, this will operate as a controlled execution service managed by the AutomationX team.

  • In later iterations, we plan to open this up for community participation via verifiable automation relayers once Rootstock’s Keeper-equivalent infrastructure matures.

4. Bridge Integration Layer:

  • Built on top of the Rootstock Token Bridge.

  • The Automation Core does not move assets directly — it interacts with existing bridge contracts to initiate and verify transfer events.

  • Each bridge action is gated by event confirmations and manual approval boundaries to prevent any unintended transfers.

This architecture is intentionally modular so that Rootstock developers can extend or fork individual components — e.g., integrating a new bridge provider or oracle feed without modifying the core.

2. Error Handling and Risk Mitigation

We take potential automation and bridge errors seriously. Key safety measures include:

  • Pre-execution Validation:
    Every automation instruction is validated both off-chain (via schema and simulation) and on-chain (through condition contracts) before being queued.

  • Safe Transaction Templates:
    Each strategy runs within an isolated “sandbox” contract that uses predefined call templates — meaning no arbitrary contract calls or unlimited gas forwarding.

  • Execution Reversion:
    If any call within a sequence fails (e.g., bridge event pending or liquidity unavailable), the automation reverts gracefully without locking assets.

  • Bridge Security:
    Since Rootstock’s bridge is managed via a federated multi-signature and widely used in production, AutomationX never introduces a custom bridge layer — it simply listens for verified bridge events and automates follow-up actions.

  • Monitoring & Auditing:
    The off-chain executor logs and contract activity will be continuously monitored via Grafana + Forta for anomaly detection.
    Internal QA includes static analysis with Slither and simulation testing in a controlled environment before mainnet release.

3. Economic Sustainability and Resource Allocation

We’ve designed the project to be sustainable beyond the grant period through a combination of developer ecosystem alignment and light monetization models.

Grant Allocation (US$12,000):

  • Core Development (Automation & Bridge Modules): $6,000

  • AI Intent Parser and Testing Infrastructure: $2,000

  • SDK and Documentation: $2,000

  • Community Integration + Testnet Launch Ops: $2,000

Post-Grant Sustainability:

  • Open-Source SDK & Ecosystem Growth:
    Developers will be able to build and publish new automation modules on AutomationX.
    A 1–2% transaction fee on third-party modules (configurable by users) sustains operations.

  • Protocol Partnerships:
    We are in early conversations to integrate with Rootstock-native DeFi protocols (e.g., Sovryn and Tropykus). These integrations could include small revenue shares or grants for specific automation use cases (like auto-rebalancing or yield monitoring).

  • Community Treasury / DAO Model:
    Once active users and developers reach critical mass, AutomationX will shift governance to a DAO framework — aligning incentives through tokenized participation or staking mechanisms.

Our long-term goal is for AutomationX to function as an open middleware protocol rather than a closed product — making it naturally self-sustaining as part of the Rootstock developer stack.

4. Achieving the Target Goals

While the initial grant focuses on technical milestones, community adoption is an equal priority. Our plan includes:

  • Running a public testnet campaign with Rootstock community members.

  • Hosting a developer workshop post-Milestone 3 to onboard early adopters of the SDK.

  • Partnering with Rootstock ecosystem teams for early automation use cases (e.g., Tropykus auto-lending or Sovryn collateral monitoring).

These combined efforts will organically drive the KPIs mentioned (transactions executed, developers onboarded, and TVL bridged).

In summary, AutomationX’s architecture has been deliberately designed to be secure, modular, and Rootstock-native. The automation logic is bounded by user consent and smart contract safeguards, while sustainability is ensured through developer participation and low-overhead monetization.

1 Like
9

Hi @Kaf_StableLab — thanks for the insightful questions. Let me clarify both points below:

1. Chainlink Automation Integration on Rootstock

You’re absolutely right — Chainlink Automation (formerly Keepers) is not yet deployed natively on Rootstock.

Our mention of Chainlink Automation in Milestone 2 refers to compatibility and architectural readiness, not direct integration at this stage.

Here’s what we mean in practice:

  • AutomationX uses an event-driven execution layer that’s designed to be Chainlink Automation–compatible once support goes live on Rootstock.

  • For the MVP and grant period, we’ll rely on RIF Oracles and a lightweight off-chain automation service that listens for events (e.g., price feeds, bridge confirmations) and triggers corresponding Rootstock contract calls.

  • Once Chainlink Automation becomes available, our existing event and condition schemas can plug directly into it without rewriting the automation contracts.

This approach keeps AutomationX future-proof and consistent with Rootstock’s existing oracle stack while remaining technically feasible right now.

Reference:

2. Security Review and Audit Process

Security is central to AutomationX, and we’ve structured our development and validation plan to ensure safety even within a lean budget:

a. Internal QA & Static Analysis

  • We’re following OpenZeppelin smart contract standards and running static analysis using Slither and Mythril during every iteration.

  • Automated test suites (Hardhat + Chai) will simulate on-chain condition triggers and bridge event flows.

b. Testnet Validation

  • Before mainnet deployment, all automation and bridge modules will undergo public testnet stress testing, allowing the Rootstock community and partners to verify reliability and transaction behavior.

c. External or Community Audit (Conditional)

  • If budget permits, we plan to engage a third-party security review for the core contracts before Milestone 3 mainnet launch.

  • Alternatively, we’ll run an open community review program (via GitHub Issues + bug bounty framework) to crowdsource testing and feedback.

By combining internal validation, transparent testnet deployment, and community verification, we aim to maintain a high security standard even within the limited initial grant scope.

We appreciate your kind words and thoughtful analysis — our goal is to ensure AutomationX’s technical foundation is realistic, modular, and aligned with Rootstock’s current infrastructure capabilities.

Thank you again for the valuable feedback and for helping us refine the implementation details.

— AutomationX Team

10

Hi @Eren_DAOplomats — thank you for the encouraging feedback and thoughtful questions. I’ll keep this response focused on what hasn’t already been detailed in the proposal.

1. User Experience (UX) Design Philosophy

AutomationX’s design principle is simplicity without compromising user control.
The end goal is for a user to express an intent once, review a clear execution summary, and then allow the automation system to handle the repetitive DeFi logic safely.

A few key UX design choices we’re incorporating:

  • Explainable Automation: Each automation will include a human-readable breakdown (“this rule will execute X on Y when Z happens”), ensuring transparency before activation.

  • Task Status Visualization: A live dashboard will display current automations, pending triggers, and last execution events in real time, using Rootstock explorer data.

  • Error Feedback Loop: If a condition fails (e.g., insufficient liquidity or oracle delay), the dashboard will provide actionable feedback rather than silent failures.

This design approach aims to make Rootstock DeFi usable for mainstream users while maintaining full non-custodial control.

2. Long-Term Sustainability

While the initial grant will fund development of the automation engine and SDK, our longer-term plan is to make AutomationX a shared infrastructure layer rather than a one-off product.

We intend to:

  • Integrate with Rootstock-native protocols (like Sovryn and Tropykus) to provide them with automation APIs that reduce user friction and deepen ecosystem stickiness.

  • Encourage external developers to publish community-built automation templates via the SDK — these can include performance-based fee sharing to sustain protocol operations.

  • Transition to a community-governed model once ecosystem adoption justifies decentralizing execution and governance.

This ensures AutomationX continues evolving beyond the 24-week scope of the grant without dependency on recurring funding.

3. Team and Deliverables Update

We appreciate the interest in seeing updated links. Our current GitHub repository and demo video are not yet public because we’re actively refactoring the ETHIndia MVP for Rootstock integration and conducting internal testing.

We plan to open-source the repository and publish the updated demo as soon as:

  • The RSK testnet contracts are stable and verified, and

  • The AI intent parser is adapted for Rootstock protocol data.

At that point, both links will be shared here for community review and technical validation.

We’re grateful for your interest and the opportunity to clarify our direction.

— AutomationX Team

11

Hi @404Gov — appreciate you taking the time to go through the proposal and share your thoughts. Let me clarify a few points.

1. Demo, GitHub Repository, and Team Links

The version of AutomationX you’ve seen was an MVP we built during ETHIndia 2025, mainly to validate the automation concept and natural-language workflow. It was built in a short hackathon window, so while it demonstrated the core idea, it wasn’t production-ready.

You can check out the original submission and demo video here:
https://ethglobal.com/showcase/automationx-etqcb

We’re now rebuilding the system specifically for Rootstock, including new contract architecture, a more reliable automation engine, and RSK integration.

The updated demo and GitHub repo aren’t public yet, as we’re still testing the RSK-compatible contracts internally. Once the testnet deployment is stable, we’ll open-source the repo and share the new demo link here for community feedback.

Team:

We’ll also add these verified links to the main proposal soon.

2. 2,500 Automated Transactions Target

That number isn’t based on any speculative assumptions or partnerships — it comes from a practical rollout plan.

Testnet Phase:
We’ll open community testing for Rootstock users and developers to try out automation workflows. Each setup generates measurable on-chain transactions.

SDK Release:
Once the SDK is live, developers can integrate automations into their own dApps, which will naturally increase transaction volume.

Gradual Onboarding:
Through open workshops and documentation, we’ll help early users set up automations and gather feedback to improve adoption.

So, the 2,500 figure reflects expected cumulative transactions from both testnet and mainnet activity during the initial 90 days — realistic and trackable, not just projection.

3. Security and User Protection

Security is central to what we’re building, especially since the system interacts with user assets.

Non-Custodial Setup:
AutomationX doesn’t hold user funds. Every action happens through the user’s wallet with limited, task-specific approvals.

Smart Contract Standards:
We’re following OpenZeppelin libraries and testing contracts with tools like Slither, Mythril, and Hardhat.

Transparency:

  • Every automation is fully visible on-chain.

  • Users can revoke or change automations any time.

  • Before mainnet, we’ll go through either a community review or external audit depending on the available budget.

Our goal is to make sure users keep full control, with everything visible and verifiable.

Thanks again for the thoughtful feedback — it helps refine how we present and prioritize things. We’ll post the updated testnet demo and GitHub link as soon as the Rootstock version is ready for review.

— AutomationX Team

1 Like