CorDapp developers tend to use AbstractParty when they want to support concrete parties, as well as anonymous identities. Currently Cordaptor only supports concrete parties. We need to change serialization logic to support both anonymous and concrete parties.
Cordaptor is coupled with the underlying node, so it will follow the principle that if the node knowns about anonymous party identity, it will provide its X.500 name, otherwise only a hash of the owning key.
Hashing mechanism for the keys will obtain SHA256 hash of the key bytes, and then represent it as a string encoded as Base58, in line with Corda and general crypto community practice
CorDapp developers tend to use AbstractParty when they want to support concrete parties, as well as anonymous identities. Currently Cordaptor only supports concrete parties. We need to change serialization logic to support both anonymous and concrete parties.
Cordaptor is coupled with the underlying node, so it will follow the principle that if the node knowns about anonymous party identity, it will provide its X.500 name, otherwise only a hash of the owning key.
Hashing mechanism for the keys will obtain SHA256 hash of the key bytes, and then represent it as a string encoded as Base58, in line with Corda and general crypto community practice