This workshop will be a hands-on introduction to building apps with Abstract. We'll be completing a dollar-cost-averaging app that will allow users to set up recurring purchases of a token of the ir choice. The goal of the workshop is to have the app's tests passing by the end of the workshop, setting you up to build your own apps with Abstract.
solutionbranch contains the quests with the solutions.questsbranch contains the quests without the solutions.
Have a brief look at the required prerequisites here. The recommended tools won't be required for this workshop.
You can run
cargo checkto make sure that the application compiles. You can then runcargo testto see the failing tests.
A high-level introduction to Abstract will be given, followed by the use-case of the application and a brief overview of the codebase. We'll then dive into the code and complete the app together in Quests.
The application we're building is a dollar-cost-averaging application that allows the owner of an Abstract smart-contract wallet to set up recurring purchases of a token of their choice. The user will be able to set the amount of tokens they want to purchase, the frequency of the purchases, and the token they want to purchase. The application will then automatically purchase the tokens for the user at the specified frequency.
The working codebase can be found in our monorepo.
The quests consist of a series of missing code snippets that you'll need to complete in order to get the application to work. The quests are numbered by #{quest_number}. At the beginning of each quest you can search for that and find the locations that need fixing.
Module dependencies define what other modules the application requires to perform its logic. This segregation of concerns allows for more modular applications that can be reused in different contexts.
To find the code that needs work, search for
#0in your IDE of choice.
Each application has an admin that is able to perform administrative actions on the application. In this case, the admin is the owner of the Abstract smart-contract wallet that the application is installed on. We need to make sure that the admin is the one calling the administrative functions.
To find the code that needs work, search for
#1in your IDE of choice.
The abstract-sdk allows developers to create APIs for their modules. These APIs allow users (contracts) of that module to interact with it in an intuitive way. In this quest we'll be using the Dex and CronCat APIs to set up token swaps and schedule recurring transactions.
Abstract applications have some base functionality that is shared across all applications. This includes the ability to set the admin of the application, and the ability to transfer ownership of the application. In this quest we'll see how that effects the entry point messages that the application exposes, which is important to know for interacting with the application.
Testing is an important part of building applications. In this quest you'll deploy the required infrastructure to test the application.
Testing abstract modules is made easy through the use of
cw-orchestrator, our flagship dev-tooling product.
In order to speed up both deployment and testing of the application, we've created cw-orchestrator. In this quest you'll use the auto-generated methods on the app interface to interact with it in a testing environment. The same interactions can be executed on any other CosmWasm-supporting environment!
Wow, congrats you got this far!
This task will show you how you can use cw-orchestrator to deploy your application to any testnet or mainnet. You'll need to have some tokens to complete this quest.