IFTTT for Web3, A Resilient Zapier for Web3. I am solving the problem of integrating web3 protocols for developers by simplifying the process with a no-code platform that allows them to create and integrate IFTTT (If This, Then That) recipes. This eliminates the need to learn new web3 protocols, which can be a time-consuming and challenging process with traditional integration methods.
2. How is Lit used for this project? (max 100 words)
We will natively support LIT Protocol in Zen.Watch IFTTT, making it easier for developers new to LIT protocol and web3 development to get started. With our no-code IFTTT templates, developers can seamlessly dive into LIT protocol development. Integrating LIT PKPs and LIT Actions is essential for Zen as a non-custodial IFTTT alternative for web3.
The main benefit of the proposed integration are as follows:
Enables developers who are new to LIT protocol to easily onboard to LIT
Enables developers to build advanced workflows interconnecting other protocols with LIT, such as 4337, without writing a lot of code, relative to starting from scratch
Enables developers to seamlessly integrate the aforementioned advanced workflows into their application flow using an easy-to-use SDK.
3. How will you improve your project with this grant? What steps will you take to meet this objective? (max 200 words)
The deliverables are listed below:
Expand native support for LIT Actions in Zen.Watch IFTTT with templatized functionality, allowing LIT developers to utilize IFTTT features and chosen PKPs non-custodially. This automates the submission of LIT action-signed payloads to respective blockchains.
Develop an open-source bot server that supports LIT templates, enabling LIT developers to avoid starting from scratch. They can fork the repository and begin with executable equivalents of the examples provided in the LIT documentation.
Create LIT recipes for recommended building blocks as suggested by the LIT Team. This allows LIT protocol to publish intriguing LIT building blocks for their new developers.
Establish an interactive web3 manual for LIT protocol within the Zen.Watch Admin tool. This provides new developers with a quick understanding of LIT development, aiding in their onboarding process. It also includes links to the LIT document and community page.
Architecture diagram
4. Is this project open source?
Yes, the project is already open-source under the Business Source License 1.1 (BUSL 1.1), similar to Uniswap V4 and MariaDB.
5. Do you agree to share grant reports upon request, including a final grant report at the end of the two month period?
Yes
6. Links and submissions
Not applicable
7. Total Budget Requested
Here is the proposed roadmap along with the requested budget for each milestone:
Milestone 1: Expand native support for LIT Actions in Zen.Watch IFTTT with templatized functionality
Developer: 1 (myself)
Time: 20 hours
Budget: $1333.34
Milestone 2: Develop an open-source bot server that supports LIT templates
Developer: 1 (myself)
Time: 20 hours
Budget: $1333.34
Milestone 3: Create LIT recipes for recommended building blocks as suggested by the LIT Team
Developer: 1 (myself)
Time: ~10 hours X number of recipes (starting with 2 recipes)
Budget: ~$666.67 (10 hours for 2 recipes)
Milestone 4: Establish an interactive web3 manual for LIT protocol within the Zen.Watch Admin tool
Developer: 1 (myself)
Time: 25 hours
Budget: $1666.67
Total budget requested: $5000
In addition to the mentioned milestones, Zen.Watch is committed to providing ongoing support and services to the LIT community:
Developer Integration & Onboarding:Zen.Watch will assist developers interested in using the tool with integration and onboarding. We aim to offer this support free of charge as much as possible.
Hosted Version of IFTTT: Zen.Watch will offer a paid, hosted version of IFTTT, allowing developers to easily access the cloud version and save time on self-deployment.
Collaboration with LIT Team:Zen.Watch will continue working closely with the LIT team to enhance features and onboard new recipes. Our goal is to make the developer onboarding process smoother and more accessible for LIT.
These additional initiatives demonstrate Zen.Watch's commitment to supporting the LIT community and ensuring the success of developers using the platform.
1. What is your project? (max 100 words)
IFTTT for Web3, A Resilient Zapier for Web3. I am solving the problem of integrating web3 protocols for developers by simplifying the process with a no-code platform that allows them to create and integrate IFTTT (If This, Then That) recipes. This eliminates the need to learn new web3 protocols, which can be a time-consuming and challenging process with traditional integration methods.
Github: https://github.com/Zen-Watch Website: https://zen.watch/ Demo: https://youtu.be/Fxd3QroXMIM
2. How is Lit used for this project? (max 100 words)
We will natively support LIT Protocol in Zen.Watch IFTTT, making it easier for developers new to LIT protocol and web3 development to get started. With our no-code IFTTT templates, developers can seamlessly dive into LIT protocol development. Integrating LIT PKPs and LIT Actions is essential for Zen as a non-custodial IFTTT alternative for web3.
The main benefit of the proposed integration are as follows:
3. How will you improve your project with this grant? What steps will you take to meet this objective? (max 200 words)
The deliverables are listed below:
Architecture diagram
4. Is this project open source?
Yes, the project is already open-source under the Business Source License 1.1 (BUSL 1.1), similar to Uniswap V4 and MariaDB.
5. Do you agree to share grant reports upon request, including a final grant report at the end of the two month period?
Yes
6. Links and submissions
7. Total Budget Requested
Here is the proposed roadmap along with the requested budget for each milestone:
Total budget requested: $5000
In addition to the mentioned milestones, Zen.Watch is committed to providing ongoing support and services to the LIT community:
These additional initiatives demonstrate Zen.Watch's commitment to supporting the LIT community and ensuring the success of developers using the platform.
Additional questions: