# Introduction ### What is HODLer Market? The DeFiner HODLer market is a configurable lending market with a lock-up function. It includes a Smart Contract Factory which produces a lending market on demand. With 3 clicks, anyone can launch their own lending market. The HODLer market is 100% permissionless. Just like anyone can go to UniSwap to create a token pair, anyone can come to DeFiner to be a DeFi lending market. The HODLer market is very customizable. Users can create a market by controlling aspects such as asset supported, maturity date, oracle, and more. The following documentation describes the fundamentals of the protocol and how to interact with it. Please join the [#development](https://discord.com/invite/rUCBdTp) room in the DeFiner community Discord server; our team and members of the community look forward to helping you build on top of DeFiner. ### Basic Overview The DeFiner protocol codebase is hosted on [Github](https://github.com/DeFinerOrg/Savings), the HODLer market code is still private. The protocol is implemented as a set of **smart contracts** on top of the Ethereum and other EVM-compatible blockchains. Smart contracts guarantee safety and do not require a middleman. Users and applications can interact directly with the smart contracts, the blockchain data, or via their favorite web3 providers. DeFiner Protocol is developed with security as a priority, having been audited by multiple auditors. For a deeper dive into the protocol, economics, and how it works, refer to the [White Paper](https://github.com/DeFinerOrg/DeFiner-2.0-whitepaper/wiki/DeFiner-2.0-Whitepaper). ## --- # 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.definer.org/introduction.md?ask= ``` 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.