Also, the data can be downloaded. So the community can back it up in case the calendars ever fail.
while we are at it. Have you ever done napkin math on what the reasonable maximum proof size is one could expect? Technically proofs can be extended ad infinitum, which im not sure is ever a sensible idea....
Need to have some ballpark number since my proposal is to add it to the json, so parsers need some reasonable datasize range as to not be DOS'd by gigabyte blobs.
There are other potential usecases that can leverage this technique of just attaching it to the JSON, but i suspect OTS-proofs to be one of the larger(in terms of bytes), if not the largest phenomena in that realm (other use cases would be like counts etc. which would be fairly small)
Need to have some ballpark number since my proposal is to add it to the json, so parsers need some reasonable datasize range as to not be DOS'd by gigabyte blobs.
There are other potential usecases that can leverage this technique of just attaching it to the JSON, but i suspect OTS-proofs to be one of the larger(in terms of bytes), if not the largest phenomena in that realm (other use cases would be like counts etc. which would be fairly small)