Logware has no limit to the amount of cryptographic hash data it can store. A blockchain is like a ledger book with an unlimited number of blank pages. Sure, it might get heavy after a while, but hard drive space is cheap and gets cheaper every year. The issue comes down to speed. The Logware API is capable of queueing a backlog, so a burst of requests can be received and stored, but it might take a few seconds to complete the task. This nice thing about the API is this work is all handled automatically for the customer. The API can even provide a Logware Identification Number that identifies the transaction before the hash is even stored. It’s unlikely a record will be needed within seconds of submitting it so it works well for almost all use cases.