yeah i agree it makes sense for relays (or clients) to carry the proofs. I came up with that kind1041 event for that reason, that everyone can keep an eye on those, and go the calendar server themselv...
Similar thing, my 31045s allow "not_yet_available" in the block height tag, and then later the 31045 can get replaced with one that carries a complete proof.
But if I remember correctly your 1041 automatically expire after a week or so, which makes sense.
My client basically has settings in which users specify a list of pubkeys for which they want to be stewards of OTS info, and then the client automatically tries to do the work of keeping the OTS info updated for events from those pubkeys. The default setting is simply that users are stewards for OTS info for their *own* pubkey.
But if I remember correctly your 1041 automatically expire after a week or so, which makes sense.
My client basically has settings in which users specify a list of pubkeys for which they want to be stewards of OTS info, and then the client automatically tries to do the work of keeping the OTS info updated for events from those pubkeys. The default setting is simply that users are stewards for OTS info for their *own* pubkey.
1