# Resolvers

* ResolverRegistry [0x60627326F55054Ea448e0a7BC750785bD65EF757](https://polygonscan.com/address/0x60627326F55054Ea448e0a7BC750785bD65EF757)
* Shared [0x97Fd55d91D42ea01C73fc88DAbBa89944a97FddA](https://polygonscan.com/address/0x97Fd55d91D42ea01C73fc88DAbBa89944a97FddA)
* NameResolver [0x4f6cDA539a63e52ee5a5e4F3D7dfC97C7C48842e](https://polygonscan.com/address/0x4f6cDA539a63e52ee5a5e4F3D7dfC97C7C48842e)
* VehicleIdResolver [0xeBd57Eb7821EfDdC9280bB87228888D0BDD5DbcA](https://polygonscan.com/address/0xeBd57Eb7821EfDdC9280bB87228888D0BDD5DbcA)

The `ResolverRegistry` acts as a centralized hub for interacting with various resolver contracts. It facilitates the resolution of DCN names into associated data, such as Vehicle IDs. The following resolvers are integrated:

* **NameResolver**: Maps DCN nodes to name strings.
* **VehicleIdResolver**: Resolves DCN names to Vehicle IDs, offering seamless retrieval of associated Vehicle IDs based on minted names.


---

# 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/device-canonical-name/contracts/resolvers.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.