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
  2. Auxiliary Contracts

Mapper

PreviousEip712CheckerNextArchitecture

Last updated 2 years ago

Address:

Due to the DIMO system architecture, we constantly strive to avoid cross-module calls and minimize codependency, typically simply accessing each other's storage. But a third module, , is used to create the connection between the Vehicle and the AftermarketDevice. Its sole responsibility is to keep track of any connections between modules that might exist and that wouldn't make sense if they were to reside in a particular module.

0x8083F96cF51727BE905057a837DAafBE0B91920f
Mapper