ArNotify

Onchain Transaction
Thumbnail
Connected Wallets
Welcome page
Sign Up
Landing Page

📙 Inspiration

I have always been fascinated by the idea of a permaweb, where data is stored permanently and immutably on a blockchain network. I wanted to explore the possibilities and challenges of creating applications that leverage the permaweb, and how they can interact with the web2, where most of the users and services are still located.

📣 What it does

Our project is called ArNotify, and it is a protocol that enables users to receive email notifications on Arweave transactions that involve their wallet address. By using the tools and libraries mentioned above, I created a seamless and secure user experience that bridges the gap between the permaweb and the web2. With ArNotify, users can easily monitor their Arweave activity and stay updated on their wallet balance, transaction status, and data storage.

🔨 How we built it

We built ArNotify using a combination of technologies and protocols that enable us to connect the permaweb with the web2. Here are the main components of our project:

Arweave JS SDK

This is the official JavaScript library for interacting with the Arweave network. It allows us to create, sign, and submit transactions to the network, as well as query data from it. We used this library to implement the core functionality of our protocol, such as creating notifications, subscribing and unsubscribing users, and fetching transaction details.

ArFS library

This is a JavaScript library that implements the Arweave File System (ArFS) standard, which is a way of organizing and structuring data on the Arweave network. It allows us to create folders, files, and drives on the permaweb, and store metadata about them. We used this library to store our notification data in a structured and standardized way, as well as to retrieve it efficiently. Stamp protocol: This is a protocol that enables users to pay for transactions on the Arweave network using any token that is supported by the protocol. It allows us to abstract away the complexity of dealing with different tokens and wallets, and provide a seamless user experience. We used this protocol to enable our users to pay for their notifications using any token of their choice, such as AR, ETH, or DAI. Email service: This is a web service that allows us to send emails to our users using a simple API. It allows us to deliver our notifications to our users in a convenient and familiar way. We used this service to send email notifications to our users whenever their wallet address is involved in a transaction on the Arweave network.

We also created a landing page for our project that explains what ArNotify is and how it works, and allows users to subscribe or unsubscribe from our notification system. We used HTML, CSS, and JavaScript to create a simple and elegant web page that showcases our project.

👨🏾‍💻 Challenges we ran into

Some of the challenges were technical, such as integrating different APIs and protocols, ensuring data integrity and security, and optimizing performance and scalability.

Some of the challenges were conceptual, such as designing a user-friendly interface, explaining the value proposition of my project, and pitching it to potential users and judges.

🎉 Accomplishments that we're proud of

We are proud of many aspects of our project, but here are some of the highlights:

We created a novel and useful protocol that connects the permaweb with the web2, and provides a valuable service for Arweave users and developers.
We leveraged various technologies and protocols that enhance the functionality and user experience of our project, such as the Arweave JS SDK, the ArFS library, the Stamp protocol, and an email service.
We designed and implemented a simple and elegant landing page that showcases our project and allows users to subscribe or unsubscribe from our notification system.
We tested and deployed our project on the Arweave network, and demonstrated its performance and reliability.
We received positive feedback and support from our mentors, peers, and potential users, who appreciated our project and encouraged us to continue working on it.

🧠 What we learned

We learned about the Arweave platform, its features and benefits, and how to build applications on top of it using the Arweave JS SDK.
We learned about the ArFS standard, its specifications and advantages, and how to use the ArFS library to store and retrieve data on the permaweb.
We learned about the Stamp protocol, its functionality and use cases, and how to use it to enable users to pay for transactions using any token that is supported by the protocol.
We learned about email services, their APIs and limitations, and how to use them to send email notifications to our users.
We learned about the challenges and opportunities of connecting the permaweb with the web2, such as ensuring data integrity and security, optimizing performance and scalability, designing user-friendly interfaces, explaining value propositions, and pitching projects.

🔜 What's next for ArNotify

We are very proud of what we have achieved with ArNotify, but we also have many ideas for improving and expanding it in the future. Here are some of the features and enhancements that we plan to work on:

Customization

We want to give our users more control and flexibility over their notifications. For example, we want to allow them to choose which types of transactions they want to be notified about, such as transfers, contracts, or data uploads. We also want to allow them to customize the frequency and format of their notifications, such as daily summaries or real-time alerts.

Security

We want to ensure that our protocol is secure and reliable at all times. For example, we want to implement encryption and authentication mechanisms for our notification data, as well as backup and recovery options for our users. We also want to monitor and audit our protocol for any potential issues or vulnerabilities.

Integration

We want to integrate our protocol with other platforms and services that are relevant and useful for our users. For example, we want to enable our users to receive notifications on other channels besides email, such as SMS, Telegram, or Discord. We also want to enable our users to interact with their notifications directly from their email client or messaging app, such as confirming transactions or viewing transaction details.