Yes, temporal sharding would theoretically become unnecessary with this system. The current implementation should be capable of handling the entire historical C

Yes, temporal sharding would theoretically become unnecessary with this system. The current implementation should be capable of handling the entire historical CT dataset without requiring time-based partitioning. On storage efficiency, CompactLog requires about 200-400GB per 100 million certificates and can be run even on slow hard drives (there's support for local caching, which usually would be NVMEs drives).