shabbiryk/autostark

AutoStark Enables

Enhanced Automation: Autostark's Web3 automation capabilities complement Starnet's decentralized infrastructure, enabling Stackware projects to implement complex and automated processes seamlessly. This can streamline various operations and enhance the overall efficiency of the ecosystem.

Gasless and Scalable Execution: By adopting Gelato's gasless and continuous off-chain execution model, Autostark reduces the burden of on-chain transactions, ensuring cost-effectiveness and scalability for Stackware projects. This can lead to more sustainable and scalable decentralized applications.

Seamless Integration: Autostark's developer-friendly environment and ease of integration with existing smart contracts ensure a smooth onboarding process for Stackware projects. This enables developers to leverage automation without the need for complex modifications or additional audits.

Cost Optimization: Autostark's stable and predictable cost structure, using stablecoins like USDC, offers Stackware projects cost predictability. This can mitigate the impact of token price fluctuations and provide a more reliable pricing mechanism for accessing off-chain computation resources.

Increased Security and Trust: Autostark's focus on decentralization and trust minimization aligns with Stackware's vision of a secure and resilient ecosystem. By eliminating reliance on centralized entities, Autostark ensures that automation processes are more robust and resistant to single points of failure.

Multichain Interoperability: Autostark's multichain support enables Stackware projects to access and execute Web3 Functions across various blockchains seamlessly. This fosters interoperability and expands the reach of Stackware applications to multiple networks.

Event-Driven Automation: Autostark's support for event-driven triggers allows Stackware projects to automate actions based on specific on-chain events or state changes. This grants greater flexibility in designing automation strategies tailored to individual project needs.

Reliable Infrastructure: Autostark's reliable and performant infrastructure ensures that Stackware projects can execute a large number of Web3 Functions concurrently without compromising on efficiency and reliability.

Overall, Autostark's integration with Starnet empowers Stackware projects with a powerful and scalable Web3 automation solution, reinforcing the ecosystem's capabilities and contributing to a more decentralized, efficient, and innovative Web3 ecosystem.

Local Setup

• Install Scarb Scarb Install
• Run scarb build
• If VS Code User, just install a cairo 1 extension
• Replace timepa inside task.cairo to our project name autostark

How It Works ?

Built for MVP. Very high level overview of how to create a task and execute it. There are others which are self-explanatory like cancel the job, get configs etc

Task Creation

For instance Alice wants to send xyz amount of eth to User1 and abc amount of eth to user2 after 20 days at some fixed time.

First Alice creates a task by calling a queue function where his intended calls are hashed and unique id is generated. His calls(in this case, transfer calls) total expenditure is calculated, assertion is made wether he holds the token to cover the expenditure or not. If he holds then we make a ERC20 approval to our contract(as spender). Now his id is stored. (only id not calls).

Task Execution

Task execution part is open to all, any one can call this function with exact set of calls of Alice. This approach sort of relax the part of relayers and necessity of maintaing network of bots. When execute function is called again id is generated from the supplied calls and checked against the id of Alice or other stored one's. If the id matches then time constrains are checked. Before execution of Alice calls ERC20 transferFrom is done to move the required assets from Alice to our contract as our contract would pay the fees and required token amounts. At last Alice calls would be executed and it's array of result would be returned.

Todo

Contract

• Testing: At least one e2e test
• Could move the transferFrom execution to separate function which can be called by only us(contract owner) just before time of exe
• Help Had mentioned in comments with todo and WIP. One real pain is to have a work around for felt252 to bool (mentioned in queue and execute function, task.cairo)
• Help Calculating the gas fees. How to get gasLimit and maxGasLimit(like in ethereum), in starknet. Needs this functionality to speculate how much gas would be required in the future for txn
• Introduce mapping of id to struct with single user as owner unlike currently where deployer is owner.(done)
• Deploy to testnet

Application (Front end and other)

• DB to store the serialized calls of the user.

  • Since at the time of creation, we don't store the calls (we store id). Have to store the actual calls(serialized) and make it accessible via the Frontend. So that everybody can call it. No need to show the actual calls but only the id of it would be enough.In future it can converted into sort of bot race and reward.

• Cron Job which keeps time and calls execute with above stored calls

• User Utility: connect to wallet, starknet js ...

• User Interface: Landing page, forms to create a task ...

autostark's Issues

Devconnect Sync-up

Discussed on UI/UX changes, tokenmics introduction and prepped fund-rasing deck

Roadmap till Starknet CC hacker House during Istanbul

Progress So Far:

Automation:
AutoStark streamlines the process of automating StarkNet smart contracts. It achieves this by executing transactions in an automatic, dependable, and decentralized manner, enhancing the overall developer experience.

What We Aim to Develop at StarkNet Hacker House Istanbul:

Web3 Functions:
Our goal is to enable smart contract developers to seamlessly integrate off-chain data and computational power into their applications by implementing decentralized cloud functions.

Off-chain Service Private Repository:
We intend to establish a secure and private repository to serve as the backbone for our network of bots and other off-chain services. This repository will facilitate the management and distribution of off-chain services, ensuring a robust and reliable ecosystem.

User Interface (UI):
AutoStark will boast an intuitive and user-friendly interface, offering a seamless interaction experience for developers and users. The UI will simplify the process of accessing and utilizing AutoStark's suite of services, making it accessible to a broader audience.

Utilizing Account Abstraction:
We will leverage account abstraction techniques to enhance the privacy and efficiency of transactions within the AutoStark ecosystem. This approach will contribute to improved security and scalability, aligning with the ethos of StarkNet.

Added documentation for new features and integrated chain functionality

We've gone multichain with NEO chain integration. I have just updated the documentation on what AutoStark does and how it was made.

Partnered with twi lending and borrowing service providers

we've partnered with two PENDLE project to automate their escrow txs