Suppose I define a meta-message type, and its type is the hash %123...321=.sha256. Now I can create a message {type: "%123...321=.sha256", displayName: "vote"} to represent the message type vote. So far so good. But I also need to create the representation of the message type %123...321=.sha256 (the type of meta message descriptions). The type field of this message would need to refer to its own hash. Which is - as far as I understand the protocols - impossible, right?

It would be a shame if it was impossible for the message metamodel to describe itself, so let's hope that there can be a workaround via a stringly-typed message.