Faucet Drops
Your Plug-and-Play token distribution Faucet
Created on 8th August 2025
•
Faucet Drops
Your Plug-and-Play token distribution Faucet
The problem Faucet Drops solves
Problem
Manual token distribution during events, onboarding processes, and community programs is slow, inefficient, and error-prone. Organizers often have to verify wallets, send tokens one by one, and manage claim requests manually, this thereby creates bottlenecks, stressful distribution, and poor user experiences.
Solution
Faucet Drops automates the entire token distribution process through a smart contract-based faucet system. Organizers can preload tokens, set custom claim criteria and limits, whitelist addresses, and allow participants to self-claim tokens in a secure, seamless way. This removes the friction in Web3 onboarding, engagement, and testing.
Challenges we ran into
The biggest hurdle we encountered was dealing with factory contract validation in my faucet creation wizard. Initially, the app was incorrectly blocking users from creating custom faucets on Base, even though we had already deployed all the necessary factory contracts (dropcode, droplist, and custom factories) to the network.
The issue was in the factory availability checking logic - it wasn't properly reading the deployed contract addresses from my network configuration. This caused the UI to show "custom faucets not available" warnings and prevent users from proceeding, leading to a frustrating user experience.
We had to debug the network context and factory address resolution to ensure the app correctly recognized that all three factory types (open drop, whitelist drop, and custom drop) were actually available on Base. The fix involved properly mapping the factory types to their deployed addresses and ensuring the validation logic correctly checked against the Base network configuration.
Another challenge was ensuring the name validation worked correctly with the deployed Base factories, making sure it checked for existing faucet names against the right factory contracts without throwing unnecessary errors.
This taught us the importance of thorough testing of network-specific configurations and validation logic, especially when dealing with contract deployments across different environments.
Smart Contract Address(es)
0x945431302922b69D500671201CEE62900624C6d5
0xda191fb5Ca50fC95226f7FC91C792927FC968CA9
0x587b840140321DD8002111282748acAdaa8fA206
Other Onchain Proof
Tracks Applied (1)
Top 5 New Consumer Apps
Technologies used
