@yfmao, the storage limits that have been imposed were designed to ensure high transaction throughput while providing flexible smart contract functionality.
With that, I can see several approaches that could be a good fit for you ( based on the information you’ve provided so far ) -
- Avoid storing the large common information in a global state. Instead, store the hash of that information, while storing the actual information on a third-party storage. There is a notary-like service that is using Algorand in a similar fashion to that.
- Deploy your own co-chain. On your own chain, you’ll have no issue re-configuring the above parameters to your needs. Having a private network is a bigger commitment, though.
- Find a creative way to avoid getting into a large common information. I don’t have enough data around your application to guide you here. ;-(
As for increasing the number of global states, I’m unaware of any plan around that. But from what you’ve said, a minor increase ( like 16 -> 24 ) would not really be meaningful for you anyway. You are looking for 16 -> 32K, which is something that would definitely lower the transaction throughput.
Btw - given that TEAL doesn’t have any loops, how were you planning to iterate over keys ?