Steve Todd

Just to add the datapoint, the issue persists in the newly released macOS 12.3.

FWIW, and I'm not an expert on this, but as far as the procedure goes, I'm not sure whether the vote that was held in the meeting when the WG...

> And in contrast to what Juan Said the vote is not 75% but a majority of those who have attended in at least 50% of the last four meetings...

IIRC, the group approved this, so I think this issue could be closed. It appears to have already been done in keripy (https://github.com/decentralized-identity/keripy/pull/158).

Ok, so the blast radius is limited to the group. From my reading of the code, keripy currently [wraps all the attachments in a single group](https://github.com/decentralized-identity/keripy/blob/master/src/keri/db/dbing.py#L1201-L1248), which means that at...

Sorry, I could have phrased the original description of the issue better. The issue I'm raising here is about the future time when additional signature and digest algorithms are standardized...

I should add that security isn't my main concern, but more from a standpoint of things shouldn't break when an expected future enhancement arrives. a.k.a. [forward compatibility](https://en.wikipedia.org/wiki/Forward_compatibility).

Yep, that works for controller signatures and witness receipts since they will never use an algorithm beyond the version number in the event. VRCs, however, can and that has now...

We can close this as resolved for now, since the `-F` code takes care of the most proximate needs. I don't know if it is worthwhile to consider at this...

I read Sam's description wrong in #130. Repeated here: > The new attachment group is a counter with code -F## where ## is replaced by the two character Base64 count....