Approved. I was just trying to figure out the correct order of events though. I assume in a simple contest a client would trigger the thaw, the server sends the thaw state event, followed by all the judgements from during the freeze, then the end of contest.
I assume instead of "end of contest" you mean end_of_updates (also below)?
If a resolver is directly connected to the CCS, we can't trigger the thaw first b/c then other clients would see all judgements, so I guess it would trigger thaw at the end?
Yes, I guess so, and the resolver would have to be connected with jury/admin privileges.
If a resolver is connected via the CDS, it could likely send a thaw event, let the judgements out slowly (on clicks) to all clients, then end of contest at the end. If other systems want to do this we could spec a separate 'expose judgement' capability.
Sounds reasonable to me. There's nothing that forces the CDS to expose all judgements immediately. I'm not sure I'd immediately add a separate capability for this in the spec, but of course feel free to add it to the CDS.
deboer-tim
commented
1 year ago
I assume instead of "end of contest" you mean
end_of_updates(also below)?Yes, I guess so, and the resolver would have to be connected with jury/admin privileges.
Sounds reasonable to me. There's nothing that forces the CDS to expose all judgements immediately. I'm not sure I'd immediately add a separate capability for this in the spec, but of course feel free to add it to the CDS.