Decryption keys are only released at block timestamps causing up to a 5s delay #56
Description
Problem
The Shutter API releases decryption keys only at block times. If users provide a decryption timestamp that does not align with a block time, the keys are only made available at the next block timestamp, which can cause a delay of up to 5 seconds for the keys to be available, while the API throws an error indicating that the decryption keys are not available. This behavior can cause confusion for app developers who expect keys to be available exactly at the specified decryption time, and can also lead to failure to get decryption keys if they are only requested at that time.
Proposed Solution
[API] Add a response message when a request for decryption keys is made with a trigger time before the corresponding block timestamp:
- Explain that keys will only be available at the block timestamp.
- Include the actual block timestamp in the response.
[Docs] Update documentation to:
- Clarify that decryption keys are released at block timestamps only which can cause up to 5s delays.
[Optional] Add a helper endpoint that returns:
- An estimated block timestamp corresponding to the time trigger defined by the user.
Notes
- This affects any apps built on top of the Shutter API, such as Shutter Predict and Shutter Hongbao.
- Block timestamps are not deterministic — they vary slightly, so exact timing cannot be guaranteed.