The problem SpendSentry solves

Revolutionizing Fundraising, Payment Transparency with SpendSentry

Organizations, such as NGOs, schools, colleges, fundraisers, etc., collect funds from end-users/stakeholders to achieve specific goals.

Organizations often face challenges in providing clear insights into fund allocation and project progress.

User Uncertainty

Users contributing funds/fees are unaware of where their money is spent and lack real-time updates on project milestones.

SpendSentry's Solutions

• Smart Contracts: Utilizes smart contracts for secure and transparent financial transactions.
• Real-time Tracking: Enables organizations to allocate funds efficiently and allows users to monitor progress in real time.
• Notification System: Users receive instant notifications upon the achievement of project milestones, ensuring transparency.

Use Cases and Examples

• Preventing Scams: SpendSentry identifies and prevents fraudulent activities, ensuring funds reach legitimate organizations.
• Enhanced Trust: Users gain confidence with real-time updates and notifications, promoting trust in the fundraising process.
• Efficient Allocation: Organizations use SpendSentry to streamline fund allocation, reducing inefficiencies and optimizing project budgets.

Use Cases

• NGO Fundraising: SpendSentry facilitates transparent fundraising for NGOs, allowing users to track contributions and fostering trust in the donation process.
• College Fee Payments: Colleges can leverage SpendSentry for fee transactions, empowering users to hold institutions accountable by providing a transparent record of financial transactions.
• Blockchain Trading Transparency: SpendSentry can be adopted by blockchain trading agencies to attract investors.

Challenges we ran into

Network Integration and Development Process

Changing networks frequently posed integration challenges, prompting us to adopt a more streamlined approach by working with a single network. Specifically, we selected Sepolia ETH exclusively for the push protocol integration, leading us to settle on a singular network for simplicity.

Development Environment Transition

Initially, our development efforts were centered around GitHub Codespaces. However, complications emerged during user wallet authentication as there was no wallet available in the Codespaces browser. To effectively address these challenges, we made the decision to transition to local development.

Documentation Challenges

During the development process, we encountered issues in the documentation of the push protocol code. This included the identification of spelling mistakes that required correction.