Module pallet_identity::pallet

source ·
Expand description

The pallet module in each FRAME pallet hosts the most important items needed to construct this pallet.

The main components of this pallet are:

  • Pallet, which implements all of the dispatchable extrinsics of the pallet, among other public functions.
    • The subset of the functions that are dispatchable can be identified either in the dispatchables module or in the Call enum.
  • storage_types, which contains the list of all types that are representing a storage item. Otherwise, all storage items are listed among Type Definitions.
  • Config, which contains the configuration trait of this pallet.
  • Event and Error, which are listed among the Enums.

Re-exports§

  • pub use __tt_error_token_1 as tt_error_token;
  • pub use __tt_default_parts_7 as tt_default_parts;
  • pub use __tt_extra_parts_7 as tt_extra_parts;
  • pub use __tt_default_parts_v2_7 as tt_default_parts_v2;

Modules§

  • Auto-generated docs-only module listing all defined dispatchables for this pallet.
  • Auto-generated docs-only module listing all (public and private) defined storage types for this pallet.

Structs§

  • The Pallet struct, the main type that implements traits and standalone functions within the pallet.

Enums§

  • Identity pallet declaration.
  • The Error enum of this pallet.
  • The Event enum of this pallet

Traits§

  • Configuration trait of this pallet.

Type Aliases§

  • Reverse lookup from username to the AccountId that has registered it. The value should be a key in the IdentityOf map, but it may not if the user has cleared their identity.
  • Information that is pertinent to identify the entity behind an account. First item is the registration, second is the account’s primary username.
  • ModuleDeprecated
    Type alias to Pallet, to be used by construct_runtime.
  • Usernames that an authority has granted, but that the account controller has not confirmed that they want it. Used primarily in cases where the AccountId cannot provide a signature because they are a pure proxy, multisig, etc. In order to confirm it, they should call Call::accept_username.
  • The set of registrars. Not expected to get very big as can only be added through a special origin (likely a council motion).
  • Alternative “sub” identities of this account.
  • The super-identity of an alternative “sub” identity together with its name, within that context. If the account is not some other account’s sub-identity, then just None.
  • A map of the accounts who are authorized to grant usernames.