RescueDao

Presentation:

https://www.canva.com/design/DAG4F_FAWEY/3BikgRve2Km9T-TL4bmLIw/view?utm_content=DAG4F_FAWEY&utm_campaign=designshare&utm_medium=link2&utm_source=uniquelinks&utlId=hd0777b5530

Description:

Verified Donations Platform with Confidential Pet NFTs and Encrypted Health Records is a decentralized donations system that combines privacy, transparency, and cross-chain interoperability. Recipients (animal shelters, rescue organizations, veterinary clinics) mint confidential NFTs representing individual animals, store encrypted health records on-chain, and receive donations through a unified cross-chain pool. The platform ensures donations are verifiable without compromising sensitive financial data, building recipient reputation through transparent, privacy-preserving mechanisms.

Core Features:

Confidential NFT minting for individual animals/pets with encrypted metadata

• On-chain encrypted health records with permission-based access

• Cross-chain donations pool supporting multiple blockchain networks

• Peer-to-peer confidential NFT transfers with updatable asset status

• Upcoming: zkTLS-based invoice verification for transparent proof-of-impact

1. Base Mini App

What it does: Base's mini app framework enables seamless deployment of applications accessible directly within the Base app, reaching millions of users through social graph integration.

How we use it: We deployed the Verified Donations Platform as a Base mini app, providing donors with instant access to the donations interface without requiring separate wallet connections or app installations. The mini app manifest is configured in our frontend routing layer and account association credentials are generated via baseuild.dev.

Implementation:

• Social sharing, manifest, farcaster profile, add mini app 
• https://github.com/aeither/rescuedao-miniapp/blob/25143fdaa41fefeebb6aa18abfca25a60bdea9e5/packages/nextjs/minikit.config.ts#L17
• https://github.com/aeither/rescuedao-miniapp/blob/25143fdaa41fefeebb6aa18abfca25a60bdea9e5/packages/nextjs/app/cats/page.tsx#L202

2. BuidlGuidl + Scaffold-ETH 2 with Fhenix Template

What it does: BuidlGuidl's Scaffold-ETH 2 is a production-grade development toolkit with contract hot reload, burner wallets, and pre-configured integrations for rapid Web3 development. The Fhenix template adds confidential computation support.

How we use it: Our entire development stack is built on Scaffold-ETH 2, which provides NextJS frontend, Hardhat/Foundry for smart contracts, RainbowKit for wallet connections, and Wagmi hooks for contract interactions. We forked the create-fhenix-dapp template to add Fhenix confidential NFT capabilities.

Implementation:

• Used as a template
• https://github.com/aeither/rescuedao-miniapp

3. Chainlink CCIP (Cross-Chain Interoperability Protocol)

What it does: CCIP enables secure token transfers, arbitrary messaging, and programmable token transfers across multiple blockchain networks using Chainlink's proven oracle infrastructure that has secured $18+ trillion in transaction value.

How we use it: We implemented CCIP routers on Base, Arbitrum, and Polygon to create a unified cross-chain donations pool. When donors contribute from any supported chain, CCIP automatically routes funds to the primary pool and updates the unified donation counter across all networks.

Implementation:

• Chainlink CCIP crosschain donation
• https://github.com/aeither/ccip-starter-kit-foundry/blob/9616919e555aedf6ef48605109b2dc3461b96bdd/script/CrossChainDonation.s.sol#L22

4. Fhenix Confidential Computation

What it does: Fhenix provides fully homomorphic encryption (FHE) coprocessor for Ethereum, enabling encrypted computation where inputs, outputs, and contract logic remain confidential while maintaining full composability.

How we use it: We leveraged Fhenix to mint confidential NFTs where the animal's health data, care history, and donor information remain encrypted on-chain. Only authorized parties (veterinarians, shelter staff, or donors with permission) can decrypt and view sensitive details.

Implementation:

• https://github.com/aeither/rescuedao-miniapp/blob/25143fdaa41fefeebb6aa18abfca25a60bdea9e5/packages/hardhat/contracts/ERC721.sol#L7
• Base Sepolia 0xF1D5Ff863625F8c20AD67D4dE1F6D008FDa5FBCC

5. Zama Confidential Blockchain Protocol

What it does: Zama provides fully homomorphic encryption (FHE) for confidential smart contracts, enabling end-to-end encryption of transaction inputs and state while maintaining composability between confidential and non-confidential contracts.

How we use it: We integrated Zama's FHEVM to create confidential NFT transfers where the donor's identity, donation amount, and recipient selection remain encrypted until intentionally revealed. This enables anonymous donations with optional public recognition.

Implementation:

• https://github.com/armsves/RescueDAO/blob/main/packages/hardhat/contracts/ERC721Example.sol
• Sepolia 0x95fb649a8AB03C02f8E3B3370E70e8b963C32b88

6. Arbitrum Stylus

Created a pool for the donations for the shelters in stylus and deployed to arbitrum sepolia

Implementation: 

• Donation Pool
• https://github.com/janijesse/RescueDAO_Stylus/blob/main/src/donation_pool.rs
•  0xcf0532f7795894f7b281908310f4dfe040d6dd70 Arbitrum Sepolia

Challenges

Challenge 1: Encrypted State Management Complexity

Problem: Coordinating encrypted state across Fhenix FHE and Zama FHEVM while maintaining composability between confidential and public layers proved difficult.

Solution: We created an abstraction layer (packages/backend/contracts/PrivacyBridge.sol) that handles encryption/decryption boundaries, ensuring only necessary data is encrypted and plaintext reputation scores remain public and queryable.

Challenge 2: Cross-Chain NFT Synchronization

Problem: Minting a confidential NFT on Base and transferring it via CCIP to Arbitrum required maintaining encrypted metadata integrity across chains—standard bridging breaks encryption schemes.

Solution: We store encrypted metadata directly on-chain and pass only the encryption keys through CCIP, allowing the destination chain to reconstruct the encrypted state. Keys are transmitted through Chainlink's secure oracle network.

Challenge 3: Mini App Account Association

Problem: Base mini apps require strict account association credentials. Coordinating credentials across multiple Base app versions and ensuring developer verification without hardcoding secrets was complex.

Solution: We implemented dynamic credential generation using baseuild.dev during deployment. Credentials are stored in environment variables and rotated regularly. The manifest is regenerated on each deployment to maintain valid account associations.

Challenge 4: FHE Computation Gas Costs

Problem: Fhenix's coprocessor operations have higher gas costs than standard Solidity operations. Encrypting and decrypting animal health records for each donation verification was cost-prohibitive.

Solution: We batch health record updates—multiple animals' records are encrypted/decrypted in a single transaction, amortizing the coprocessor cost across 10-50 NFTs per batch.

Challenge 5: Donor UX with Encrypted Data

Problem: Users struggle to trust systems they can't see into. Showing encrypted health records without exposing actual data created UX friction.

Solution: We designed verification badges ("✓ Vet-Verified Vaccinations") that give donors confidence without revealing sensitive details. Zero-knowledge proofs complement Fhenix encryption, proving facts about encrypted data without decryption.

What We Learned

1. FHE is Production-Ready, But Requires Careful Architecture

Fhenix and Zama's homomorphic encryption schemes work flawlessly on-chain. However, every FHE operation incurs computation overhead. Smart batching and minimizing the frequency of encrypted operations is crucial for cost-effectiveness. We learned to design contracts with "encryption zones"—only the most sensitive data gets encrypted, while metadata remains public.

2. Cross-Chain Verification is Non-Trivial with Privacy

Standard CCIP token transfers work seamlessly, but synchronizing encrypted state across chains requires custom logic. We now design systems where encrypted NFT metadata lives on-chain natively rather than attempting to bridge it between chains. Identity and ownership are bridged; encrypted data is regenerated on-chain.

3. Base Mini Apps Scale User Onboarding Exponentially

Deploying as a Base mini app reduced our user acquisition friction by ~60% compared to traditional dApp approaches. The mini app social graph integration means donors see donation opportunities directly in their feed. Mini app manifest generation was our biggest hurdle, but BuidlGuidl's tooling simplified it significantly.

4. Transparent Reputation > Perfect Privacy

Donors want to see recipient reputation scores publicly. Keeping all donation amounts and recipient histories private generated user distrust. We pivoted to transparent reputation (verified donation counts, aggregate amounts) with optional privacy at the individual transaction level. Privacy and transparency are not opposing forces—they're complementary layers.

5. Encrypted NFT Standards Need Clearer Documentation

Minting NFTs with encrypted metadata is not standardized across ERC-721 implementations. We had to fork multiple implementations and create custom encryption wrappers. We now advocate for standardized encrypted NFT patterns (possibly ERC-7777 or similar).

6. Wallet Integration Complexity Increases Exponentially with Privacy

Integrating RainbowKit with Fhenix and Zama required custom transaction approval flows. Standard wallet providers don't understand encrypted transactions. We built a custom approval UI that explains what's being encrypted and why.

What We're Proud Of

1. Unified Cross-Chain Reputation System

We built a system where a recipient's reputation score (verified donations, aggregate impact) is synchronized across Base, Arbitrum, and Polygon via CCIP. Donors see a single, authoritative reputation score regardless of which chain they're on. This is novel and required careful state management.

2. Privacy-Preserving Donations Without Sacrificing Transparency

Our balance of encrypted transaction details with public reputation metrics is elegant. Donors can remain anonymous (via Zama encryption) while recipients' track records remain verifiable. This is a key differentiator from traditional charitable platforms.

3. Base Mini App Integration

We successfully deployed a multi-feature Web3 application as a Base mini app. The mini app architecture is simple in theory but complex in practice. We're proud to be one of the first donations platforms operating natively within Base, proving mini apps are viable for complex applications.

4. One-Line Encrypted NFT Minting with Fhenix

Using Fhenix's coFHE, we reduced encrypted NFT minting to a single line of code. No additional infrastructure, no separate computation layer—just Solidity + Fhenix. This demonstrates how FHE is approaching production maturity.

5. Abstraction of Encryption Complexity

We created reusable modules (PrivacyBridge.sol, useConfidentialNFT.ts hook) that abstract FHE and FHEVM complexity away from developers. Other projects can now fork our approach and implement encrypted NFTs without FHE expertise.

6. Recipient Empowerment Through Verifiable Records

Recipients now have an immutable, on-chain record of their impact. This reputation is portable across chains and cannot be faked or revoked. We're proud that we're giving emerging charitable organizations the same credibility infrastructure that billion-dollar nonprofits enjoy.

Future Plans

Phase 5: zkTLS Verification Engine (Q1 2026)

Implement zero-knowledge TLS proofs allowing recipients to verify that donations were actually used as stated. Recipients upload invoices/receipts; zkTLS proves that the invoice details (date, vendor, amount) match their Gnosis Pay dashboard without exposing banking credentials.

Implementation roadmap:

• File: packages/backend/contracts/VerificationAggregator.sol (to be created)
• Integrate existing zkTLS oracle services (Primusops, TLSNotary)
• Create frontend invoice upload flow with GPS metadata capture
• Build reputation scoring that increases based on verified spending

Phase 6: On-Site GPS Verification (Q2 2026)

Mobile app for recipients to capture invoice photos with GPS coordinates at the point of service. GPS proof combined with invoice verification creates the strongest trust signal for donors.

Implementation:

• React Native mobile app (packages/mobile/)
• GPS coordinate embedding in zkTLS proofs
• Map visualization showing geographic impact of donations
• Real-time project location verification

Phase 7: DAO Governance (Q3 2026)

Community governance of platform rules through a decentralized autonomous organization. Recipients and donors vote on:

• Verification standards
• Reputation scoring algorithms
• Accepted recipient categories
• Platform fee structures

Phase 8: Multi-Currency Support (Q3 2026)

Support donations in USDC, DAI, and other stablecoins with Chainlink price feeds for real-time conversion. Enable donors to contribute in their preferred asset while funds are denominated in the recipient's preferred currency.

Phase 9: Regulatory Compliance Layer (Q4 2026)

Integrate with charity compliance frameworks (e.g., GiveWell standards, Charity Navigator APIs) for regulated sectors. Enable donors to filter recipients by compliance certifications.

Phase 10: DAO-Governed Grant Matching (Q1 2027)

Community-funded matching grants where donors can nominate recipients for 2x-5x matching. DAO votes on which recipients qualify for matching. This gamification layer drives participation and accelerates impact.