Submissions
Notice - Decentralized Notification System on the Internet Computer A powerful decentralized notification management system built on the Internet Computer platform using Azle. This system enables seamless communication and notification delivery between users, organizations, and services while maintaining complete data sovereignty and transparency. Key Features Real-time notification delivery Customizable notification templates Priority-based notification queuing User preference management Multi-channel delivery (in-app, email integration capabilities) Notification history tracking Read/unread status management Technical Stack Internet Computer (IC) for decentralized infrastructure Azle 0.24.1 for smart contract development TypeScript for type-safe development DFX 0.24.2 for deployment and management Node.js 20.x for development environment Development Setup The project leverages modern TypeScript features with proper decorator support and strict type checking, ensuring robust code quality and developer experience. This decentralized solution revolutionizes how notifications are handled, providing a censorship-resistant, always-available notification infrastructure for the next generation of decentralized applications
Platform designed to raise awareness about eczema by providing users with access to valuable resources. It allows people to share information on various aspects of eczema, such as treatment options, preventive measures, research updates, diet advice, and personal testimonials. Users can easily search for specific topics, view verified resources, and contribute their insights. The platform ensures that all information is organised and accessible, with the added benefit of trust through resource verification. Built on the Internet Computer blockchain, it guarantees secure and transparent management of information, promoting better understanding and support for individuals affected by eczema.
FEEDBACK
An Agricultural marketplace
Sarah, your implementation focuses on buyer management in a Motoko-based backend for an Agritech supply chain. The goal was to create, update, delete, and retrieve buyers while managing their transaction history. However, the challenge requires TypeScript, while your code is in Motoko. Despite this, I refined your Motoko code instead of rewriting it entirely.
1️⃣ Storage Initialization Issue
buyers
HashMap was incorrectly initialized inside init()
, causing storage to be undefined.var buyers
outside init()
to ensure persistent storage.2️⃣ Principal ID Validation Error
createBuyer()
, an invalid Principal ID error (aaaaa-aa
) occurred.3️⃣ Error Handling & Data Validation
null
instead of structured errors, making debugging harder.Option
handling. However, error messages still need improvement.4️⃣ Performance Enhancements
5️⃣ Challenge Misalignment (TypeScript vs. Motoko)
🔹 Decide: Stick with Motoko or migrate to TypeScript?
🔹 Improve Validation: Add phone, email, and ID validation to prevent invalid entries.
🔹 Refine Error Handling: Use structured errors instead of returning null
.
🔹 Testing Needed: There are no test cases, which makes debugging harder.
Sarah, you’re making progress, but this still needs work. Let me know if we’re switching to TypeScript or refining Motoko!
Dacade is an open-sourced platform and is created in collaboration with multiple contributors. Go to the repository to start contributing.