Antonio

@rflechtner yes, the idea of the creation would be to just initialise all the initial storage (i.e., marking the DID as existing), with no additional keys attached. The key is...

Document for the (upcoming) meeting to decide about the final details of what goes into a public credential (will have minimal impact on the chain side, as most logic is...

Just wanted to give a huge +1 to the proposed syntax for runtime construction that @kianenigma has suggested here. It was and is a big struggle for us as well...

Hello, yes I see that this solves the first of the two issues, thanks. But what about the latter one?

@Ad96el @ggera we caught a nice testing bug because of this PR. I will rebase on top of `develop` once https://github.com/KILTprotocol/kilt-node/pull/625 is merged.

This will break cross-chain DIP proofs since the storage keys (and the related proofs) have changed, hence we might want to change at least the DIP stuff to make it...

Technically ready for review, but I will wait until the node PR is merged before asking for review on this one.

Superseded by https://github.com/KILTprotocol/types-augment/pull/4.

Let me know if I can be of any support! I have a pretty decent router that monitors a lot of network and device info, so I could see almost...

Hey @halo, sorry if I get back to this only now. I am not sure I am that deep into the workings to make sense of everything you mentioned 😁...