How dimo-network/dimo-identity works
Main Components
a) Core Registry Layer:
b) NFT Module Layer:
• NFT-related contracts (AftermarketDeviceId, IntegrationId, ManufacturerId, VehicleId, SyntheticDeviceId)
• Inheritance from Base/MultiPrivilege
c) Implementation Modules Layer:
• By implementation types:
• Charging implementations
• Node implementations
• Streamr implementations
• Tableland implementations
• AdLicenseValidator
d) Access Control Layer:
• DimoAccessControl components
• Relationship with other components
e) External Integrations:
• Streamr integration
• Tableland integration
Specific Elements
a) Smart Contract Infrastructure:
• Upgrade proxy pattern implementation
• Libraries and utilities as supporting components
• EIP-712 implementation for structured data signing
b) Development Tools:
• Testing framework integration
• Deployment scripts relationship
• ABI generation flow
Technical Details to Emphasize
• Relationship between different node types
• Access control flows
• External integration points
Additional Elements
• Version information
• Network deployment options (Polygon, Mumbai testnet)
• Important configuration flows
Metadata Section
• Important environment variables
• Dependencies
Key Considerations:
• Proxy-based upgrade pattern
• How the NFT system integrates with the core functionality
• Role of external services (Streamr, Tableland)
• Demonstrate the access control flow through the system