I want to build a service that requires sending many small bitcoin transactions to multiple wallets (like a faucet).
Since the transactions are small, the fees have to be kept small as well so it takes a while for them to be confirmed.
The system would need to send many transactions, which naturally creates long chains of unconfirmed transactions. If I understand it correctly, after 25 unconfirmed transactions the network starts rejecting new ones, and the system is basically stuck until the previous ones gets confirmed.
This limits the throughput of such a system to 25 transactions per confirmation time (which is at least a few hours given the low fees), making it completely unscalable.
Given the above, is there a way to build a (somewhat) scalable service that can send many small transactions? (without having to manage many wallets)