We need advice on a model using Woolett for an automated document authentication system.

Hello everyone,

I'm building an automated document verification system and want to use Woleet to generate timestamps and digital signatures directly from the Poly Track backend. During the testing phase, I encountered a few unclear points and would greatly appreciate feedback from those with practical experience.

Some points I'd like to discuss:

When generating timestamps for large documents (around 20–80MB), will the processing time increase significantly?

Is there a way to optimize the hash → anchor → verify process to reduce the number of API calls while maintaining reliability?

I've seen documentation mentioning a "signature anchoring workflow," but I'm not sure in which cases it should be used instead of just timestamps.

When verifying a large number of signatures simultaneously (100–300 files), will the API have speed limitations?

I want to design a stable system from the start, so I'd really appreciate hearing about how others are implementing it in practice. I'd be very grateful if anyone had best practices or architectural examples.

Thank you for taking the time to read this. I'll update you on the progress once I've tested a few scenarios.