Mapping that maps a party to a participant The PartyToParticipant mapping may also specify a list of signing keys for setting up an external party, in which case the keys and the threshold take precedence over any PartyToKeyMapping for the same party. Additionally, the list of signing keys may contain the public key of the party's namespace, which allows this mapping to authorize itself without the need of a NamespaceDelegation root certificate (called self-signed). authorization: the required authorization of the mapping is a union of the authorization for individual changes

• threshold change: party namespace
• adding a signing key: party namespace + all the new signing key
• removing a signing key: party namespace
• changing the signing key threshold: party namespace
• upgrading a participant permission or adding a new participant: namespaces from party and the participant namespace
• downgrading a participant permission or removing a participant: party namespace OR the participant namespace
• setting a participant's onboarding flag from false to true: party namespace
• setting a participant's onboarding flag from true to false: participant namespace
• the removal of a PTP must be authorized just by the party revocation: Revoking a self-signed PTP does not prevent later re-creation of a PTP with the same partyId. To prevent further usage of the key associated with the party's namespace, revoke a NamespaceDelegation root certificate for that namespace. UNIQUE(party)