DIMCredits Whitepaper
  • DIMCredits Whitepaper
  • Introduction
    • History
    • What is DIMCredits?
  • Core Concepts of DMAS and Holochain
    • Decentralized Multi-Agent Systems (DMAS)
      • What are DMASs?
      • Associated DePIN Network
      • Information storage mechanism
      • Validations
      • Identity management
      • Mutual currencies
      • Use cases
      • Community
      • Conclusion
  • Security in mutual credits
    • Security in mutual currencies
    • Governance mechanisms
  • Existing insurance solutions
    • Centralized credit insurance
    • Sharing economy
    • Blockchain-based parametric insurance
  • DIMCredits design
    • Overview
    • Governance
    • Workflows
    • Agents definition
      • Insurer agent
      • Debtor
      • Creditor
      • Reserve accounts
      • Broker
      • Validator
    • Transactions
      • DICs exchange
      • Agreement request
  • Legal
  • Bibliography and references
Powered by GitBook
On this page

Was this helpful?

  1. Core Concepts of DMAS and Holochain
  2. Decentralized Multi-Agent Systems (DMAS)

Identity management

PreviousValidationsNextMutual currencies

Last updated 1 year ago

Was this helpful?

An agent operates with their own devices within the ecosystem, installs applications in those devices, and generates her own profile and event history. For advanced identity features, agents can install an hApp which allows them to have DPKI services like:

  • Register keys.

  • Replace keys with new ones.

  • Revoke keys.

  • Associate multiple devices under unified keyset management.

  • Check the validity of a key.

  • Store private instructions to rebuild app keys from a master seed to reestablish authority after data loss.

  • Do social management of keys through m of n signatures (the initial default is a 1 of 1 signature using a revocation key).

These kinds of services are provided in Holochain by independent hApps as one called.

Identity and Interactions in Decentralized Multi-Agent Systems

HApps manage authorization through a functional layer called Membrane which grants and revokes access to agents. HApps also manages the rules to apply for agents’ interactions within the application. All those interactions are publicly stored by hApps and can be checked by randomly selected validators which can perform attestations and flag invalid events. This way, good or bad behaviors of agents are registered in hApps history.

Deepkey
Decentralized identity and security