# Registry

> *Address:* [*0xFA8beC73cebB9D88FF88a2f75E7D7312f2Fd39EC*](https://polygonscan.com/address/0xFA8beC73cebB9D88FF88a2f75E7D7312f2Fd39EC)

The primary contract and system entry point is `DIMORegistry`. This contract has all of the storage and is in charge of adding, deleting, and updating modules. It also directs calls and transactions to the appropriate module, which houses the implementation logic, using delegate calls. Nevertheless, no module has`constructor`, and the only contract that does so is `DIMORegistry`.

The only contract that cannot be upgraded is DIMORegistry, which helps to increase security and fend against harmful attempts. Only addresses with the admin role can access the functions that alter modules.

```solidity
struct Storage {
    // Maps function selectors to the implementations that execute the functions
    mapping(bytes4 => address) implementations;

    // Maps the implementation to the hash of all its selectors
    // implementation => keccak256(abi.encode(selectors))
    mapping(address => bytes32) selectorsHash; 
}
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.dimo.org/protocol/identity-protocol/registry.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.