I’m building a functionality that involves having multiple addresses that transfers ASA.
The tricky issue I’m encountering involves (1) Minimum balance on account (2) ASA opt-in
- Having multiple addresses means that as the number of addresses grow, I would need an increasing amount of ALGO which doesn’t seem practical. This does not seem scalable imo which might mean it is a wrong design.
- Multiple address would also mean that ASA opt-in would be required for all addresses as it scale.
Instead of having multiple address, I’m skewing towards having just 2 addresses: (1) for storing ALGO to use as gas & (2) for handling ASA transfer.
This way i would only require 1 opt-in and min. balance would not incrementally increase. To differentiate transaction, I would use memo as the differentiator.
Each transaction would be an atomic transfer that uses ALGO from (1) and ASA transfer would be made from (2)
Wanted to get some opinions on what you guys think about this?