Retain previous CHURP shareholder to prevent query failures
Closed this issue · 0 comments
peternose commented
The key manager enclave only keeps the most recent CHURP shareholder in memory. If clients are lagging behind during handoff transition, they may request key shares from the previous handoff, causing their queries to fail.
To solve this problem, the enclave should retain the second-to-last shareholder for at least a few blocks, giving clients sufficient time to catch up if they are behind.