> For the complete documentation index, see [llms.txt](https://docs.dimo.org/protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dimo.org/protocol/device-canonical-name/contracts/pricemanager.md). # PriceManager *Address:* [*0xB012e1c73073E87aD268844769170B4eE2d5bfb3*](https://polygonscan.com/address/0xB012e1c73073E87aD268844769170B4eE2d5bfb3) The `PriceManager` contract plays a crucial role within the DCN (Device Canonical Name) system by managing the pricing mechanism for minting DCN names. While currently focused on time-based pricing, the `PriceManager` holds the potential to support a variety of charging strategies in the future, adapting to evolving needs and market dynamics. ### Time-Based Pricing The primary purpose of the `PriceManager` is to determine the cost of minting a DCN name based on the duration of ownership. The pricing structure follows a per-second rate, allowing users to precisely tailor the duration of name ownership to their preferences. This approach offers flexibility and fairness, as users are charged proportionally to the actual duration they wish to possess the name. ### How it Works 1. **Base Price**: The `PriceManager` sets the base price per second. This price serves as the foundation for calculating the total cost of minting a DCN name. It reflects the intrinsic value of owning a name within the DCN system. 2. **Total Price Calculation**: When a user initiates the minting process for a DCN name, the `PriceManager` calculates the total cost by multiplying the base price by the desired duration of ownership in seconds. This straightforward calculation ensures transparent and predictable pricing. ### Future Expansion While the `PriceManager` currently focuses on time-based pricing, its design anticipates the implementation of diverse charging strategies in the future. This built-in flexibility allows for the integration of alternative pricing models that may better align with changing user preferences and market trends. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.dimo.org/protocol/device-canonical-name/contracts/pricemanager.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.