Samuel Smith

This is handled in the latest python code in The msg processor logic in Kevery.msgProcessor(). Note this uses new tritet sniff defined in KID 001 to determine if subsequent data...

It think it would be problematic to split the baby as it were between DIF and ToIP. I don’t see any concrete issues wrt divergence. Divergence only happens if someone...

To clarify the relevant version number is not the version number of the event but the version number in the message itself. When the message is an event message they...

As far as I can tell all @stevetodd concerns were addressed separately above. - backward compatibility (version string in event) for unknown attachment types - blast radius allows restart without...

I don't think there has ever been any contention that by default option 1 is how things should be. In any security protocol allowing mixed versions is always problematic. Using...

In general we are quite loose in our use of terminology but the normative definition in the KERI white paper is not loose. > Section 7.11 defines a message thusly:...

This issue IMHO is looking at the the version future compatibility issue from the wrong perspective. A more helpful perspective is to think of versioning happening at the connection level....

Yes, The corner case of a new receipt on an old event means the new receipt may use a different version number and new signatures from the version. In general...

I will keep the issue open until we move the Normative language about versioning for message body and message foot (attachments) into the spec. As well as the query version...

The best place to start is the /demo folder. There is no KERI server per se. At least not yet. We are still building the KERI core library. The demos...