DeenVerse

Demo

About

The problem it solves Many people today have never truly experienced web3. Including Muslims Not because they don't care, but because the door is locked behind technical obstacles. Crypto wallet, seed phrases, gas costs, and jargons that feel like foreign languages. For ordinary Muslims, who have no technical or financial interests. Maybe only they want to do ordinary activities such as studying the Qur'an, calculating zakat, or giving Sadaqah, without the need to think of additional concepts. And that is a missed opportunity. Because web3 is built based on the principles most concerned by the Muslim community: - **Trust** : Knowing your charity reaches the right hand. - **Transparency**: Able to verify each transaction step. - **Integrity**: Ensuring knowledge and resources cannot be changed or lost. - **Ownership**: Empowering the community to control their own digital assets. The current digital Islamic landscape itself is still dominated by a closed system, giving a little visibility to where donations leave for example. This is where Deenverse tries to fill, Deenverse Solves These Challenges by: 1. **One-stop platform for Islamic knowledge**: Qur'an, hadith, and fiqh in one intuitive app. 2. **Blockchain-powered Transparency in Charity**: Every Zakat, Sadaqah, and Infaq is Traceable and Verifiable On-Chain. 3. **SEAMLESS WEB3 EXPERIENCE**: A Familiar Islamic App Interface that Hides Web3 Complexity While Delivering Its Benefits.

How it's made

Challenges we ran into ## Challenges I Ran Into During the development of DeenVerse, I encountered several challenges both technical and non-technical: 1. **Finding Reliable APIs for Islamic Data** Building a comprehensive Islamic app requires accurate Qur’an, Hadith, and Fiqh resources. Finding APIs that are reliable, up-to-date, and match the needs of the app was a time-consuming process. 2. **UI Consistency** Ensuring a consistent look and feel across the entire app required extra effort, especially when experimenting with different components and layouts. 3. **Smart Contract & Soulbound Token Concepts** Designing smart contracts for transparent charity and exploring the concept of Soulbound Tokens for certain use cases was challenging due to both technical and conceptual considerations. 4. **Code Consistency** Maintaining clean, consistent code was sometimes difficult, especially while rapidly prototyping different features. 5. **Language Consistency** I found myself switching between English and Indonesian in code comments, documentation, and UI text. This led to inconsistency that I had to consciously fix. 6. **Scope of Religious Knowledge** Islamic knowledge is vast. Choosing what to include and what to leave out in the MVP was a constant challenge, balancing between comprehensiveness and usability.