Samuel Smith

@Joachim16 ## Call to Action I very much appreciate you detailing your concerns. I will start with your call to action. You are essentially proposing changing the rules for governance...

I admit I asked Charles what level of contribution Jolocom was making and he was not aware of any recent significant contributions I also looked at pull requests and meeting...

The kind parameter allows different serialization/deseriazation types. This can be implemented by created a _dumps method that is used instead of explicitly calling json.jumps self._dumps = json.dumps or the like

the datify function in keri.help.helping converts a dict back into a dataclass instance ```python def datify(cls, d): """ Returns instance of dataclass cls converted from dict d Parameters: cls is...

The work item is to flesh out the .get and .del methods and to support JSON and MGPK, and maybe CBOR, and Pickle

I just pushed the skeleton code above to the keripy. There were some subtleties in the python code that I fixed that might have misled you. https://github.com/decentralized-identity/keripy/pull/148 Anyway the incomplete...

So Sophy does a couple of other things like support slicing which could be added to the Komer object. It also supports backup of the database which should be added...

The json serializer could be made more compact to get rid of white space and use utf-8 instead of escaping when non-ascii. ```python >>> d = dict(a=1, b=2, c=3) >>>...

See the discussion here on the WebOfTrust repo which is where actvity for the did:keri is being conducted. https://github.com/WebOfTrust/did-keri/issues/3

I agree that There may be some rare use cases where one might want to have a TEL for the backer information or use a KEL for the backer keys...