Technical Details
WebsiteDiscordOverviewSupport
  • Overview
  • Identity Protocol
    • Overview
    • Registry
    • Nodes & NFTs
      • Manufacturer
      • Vehicle ID
      • DeviceID
      • License
    • Auxiliary Contracts
      • Access Control
      • AdLicenseValidator
      • Eip712Checker
      • Mapper
    • Architecture
    • Pairing
  • Device Canonical Name
    • Overview
    • Contracts
      • DcnRegistry
      • DcnManager
      • PriceManager
      • Resolvers
  • Token & Governance
    • Token
    • Rewards
    • Governance
  • Data
    • Platform Components
    • DBC Decoding
    • Software-Only Connectivity
    • Data Storage
    • Validation
    • Data Dictionary
      • Sample Data
  • Hardware
    • Ecosystem
    • Open Hardware Spec
    • Manufacturing License
      • DIMO Memorandum of Understanding
      • Staking $DIMO for a Manufacturer License
    • Device License
      • Device Minting Certificate
      • Hardware and Security Audit
      • Testing and Quality Control
  • Abstraction
    • Sign In With Ethereum
    • Metatransactions
  • Security
    • Methods
    • Audits
    • User Privacy
Powered by GitBook
On this page
  1. Identity Protocol

Nodes & NFTs

PreviousRegistryNextManufacturer

Last updated 1 year ago

Address:

The contracts in this section constitute the main components of the DIMO identity, implementing both general and specialized functionalities as nodes of the . Each node works in conjunction with a respective NFT. When the final user sees the NFT in their wallets, the nodes are responsible for managing all transactions behind the scenes to ensure DIMO's structural integrity.

Since there are multiple types of nodes and they all share the same storage, each contract has an idProxyAddress variable to distinguish one from the other and also has its own set of whitelisted attributes.

Regardless of specific functionalities, all nodes have functions that share similar goals. It is worth reminding everyone that, although the functions below perform comparable tasks, they have different names in each contract:

  • setIdProxyAddress: set the Id proxy address (NFT) to distinguish one contract from the other.

  • addAttribute: whitelist a new attribute.

  • setInfo: adds information to a specific node.

  • mint: mint the NFT itself. This is the function that most differs in each contract.

0x83974355a82925fA0F84A9dD9C8fB022485cE2Ea
previously mentioned tree structure