Tenancy Pallet

[ndkazu]

Use of Identity pallet with few additions

• Storage_0 : (Tenant_id: User_infos) => user info generated by identity pallet.
• No need for additional field in the tenant struct

Dispatchable Functions in Identity pallet (Only the ones we might use)

• For general users = Tenant
  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 registrars = Representative
  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 = Virtual account
  add_registrar - Add a new registrar to the system.
  kill_identity - Forcibly remove the associated identity; the deposit is lost

[ndkazu]

A suggestion on how we could use the identity pallet (After M5, because of the complex re-factoring involved)

1. In pallet_roles, during tenant role creation, incorporate set_identity from the identity pallet
2. In pallet tenancy, the tenant requests the desired asset ('request_asset'). This extrinsic will use request_judgment from pallet Identity.
3. this is a 2 steps process:

• Inside tenant_session of the Asset_management pallet, the representative first provide_judgment to assess the tenant ID and his/her ability to pay the rent for the required asset (according to identity pallets, possible judgments are: Reasonable, KnownGood, OutOfDate, LowQuality, Erroneous, etc..).
• The judgment result together with the tenant information is transferred to the investors, and a referendum is started by the Representative through the democracy pallet.

For M5, All new function can just be included in the Tenancy pallet