georgepisaltu
9185195185
Fixes #179 # Description This PR makes the structure containing identity information used in `pallet-identity` generic through the pallet `Config`. Additionally, the old structure is now available in a separate module called `simple` (pending rename) and is compatible with the new interface. Another change in this PR is that while the `additional` field in `IdentityInfo` stays for backwards compatibility reasons, the associated costs are stil present in the pallet through the `additional` function in the `IdentityInformationProvider` interface. This function is marked as deprecated as it is only a temporary solution to the backwards compatibility problem we had. In short, we could have removed the additional fields in the struct and done a migration, but we chose to wait and do it off-chain through the genesis of the system parachain. After we move the identity pallet to the parachain, additional fields will be migrated into the existing fields and the `additional` key-value store will be removed. Until that happens, this interface will provide the necessary information to properly account for the associated costs. Additionally, this PR fixes an unrelated issue; the `IdentityField` enum used to represent the fields as bitflags couldn't store more than 8 fields, even though it was marked as `#[repr(u64)]`. This was because of the `derive` implementation of `TypeInfo`, which assumed `u8` semantics. The custom implementation of this trait in https://github.com/paritytech/polkadot-sdk/commit/0105cc0396b7a53d0b290f48b1225847f6d17321 fixes the issue. --------- Signed-off-by: georgepisaltu <george.pisaltu@parity.io> Co-authored-by: Sam Johnson <sam@durosoft.com> Co-authored-by: joe petrowski <25483142+joepetrowski@users.noreply.github.com>
Identity Module
Overview
A federated naming system, allowing for multiple registrars to be added from a specified origin.
Registrars can set a fee to provide identity-verification service. Anyone can put forth a
proposed identity for a fixed deposit and ask for review by any number of registrars (paying
each of their fees). Registrar judgements are given as an enum, allowing for sophisticated,
multi-tier opinions.
Some judgements are identified as sticky, which means they cannot be removed except by complete removal of the identity, or by the registrar. Judgements are allowed to represent a portion of funds that have been reserved for the registrar.
A super-user can remove accounts and in doing so, slash the deposit.
All accounts may also have a limited number of sub-accounts which may be specified by the owner; by definition, these have equivalent ownership and each has an individual name.
The number of registrars should be limited, and the deposit made sufficiently large, to ensure no state-bloat attack is viable.
Interface
Dispatchable Functions
For general users
set_identity- Set the associated identity of an account; a small deposit is reserved if not already taken.clear_identity- Remove an account's associated identity; the deposit is returned.request_judgement- Request a judgement from a registrar, paying a fee.cancel_request- Cancel the previous request for a judgement.
For general users with sub-identities
set_subs- Set the sub-accounts of an identity.add_sub- Add a sub-identity to an identity.remove_sub- Remove a sub-identity of an identity.rename_sub- Rename a sub-identity of an identity.quit_sub- Remove a sub-identity of an identity (called by the sub-identity).
For registrars
set_fee- Set the fee required to be paid for a judgement to be given by the registrar.set_fields- Set the fields that a registrar cares about in their judgements.provide_judgement- Provide a judgement to an identity.
For super-users
add_registrar- Add a new registrar to the system.kill_identity- Forcibly remove the associated identity; the deposit is lost.
License: Apache-2.0