# Fluid Economy In terms of users and applications, the crypto ecosystem is expanding at breakneck speed, and this trend is expected to continue. Despite the growing usage of DeFi and Metaverse applications, due to the pseudo-anonymous nature of addresses, protocols lack a basic understanding of the users they are interacting with. The web 3.0 user experience now is very similar to the early era of the internet. In contrast, today, web 2.0 applications are robust; loyal users get rewards and personalized offerings. Borrower-specific interest rates were first introduced in the 4th century, and today, in 2021, DeFi treats all borrowers and users as equal risks. Because of the lack of user profiling in DeFi, all risk is reflected in collateral rather than interest rates, resulting in a poor user experience. There is no incentive for users to exhibit repetitive good on-chain behaviour. ‌This white paper describes the solution to these problems and aims to provide the missing piece for DeFi and web 3.0 mainstream adoption, introducing Unomi scores. ‌Unomi is a first of its kind decentralized identity scoring protocol that will serve as a backbone solution for the entire crypto ecosystem—creating a DeFi ecosystem that rewards its users for doing good and being trustworthy. Identity scores like Credit, Airdrop, Hodler, NFT hodler and Power user scores will provide applications with necessary info on their users and prospects. For E.G.TGE teams can prioritize airdrops and token sales to hodlers exhibiting long term behaviour. Unomi integrated DeFi protocols will provide granular services and dynamic terms to their users based on their on-chain score; this will help DeFi protocols become **fluid.** ‌DeFi lending ecosystem is still in its infancy with many opportunities untapped due to overcollateralized loans, as there is no way for protocols to profile and assess their users. Unomi credit scores provide a solution where addresses issued higher credit scores gain access to low-collateral loans. This fluidity helps improve capital efficiency. --- # 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://kudomoney.gitbook.io/kudo-docs/protocol/fluid-protocols.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.