> For the complete documentation index, see [llms.txt](https://docs.layerk.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.layerk.com/layer-6-distribution-layers/liquidity.md). # Liquidity ## Liquidity-Backed Capacity \ Every NodeK needs LYK locked to access network jobs. Liquidity-Backed Capacity (LBC) lets the community help machines reach that lock threshold so they can start contributing sooner. Contributors place LYK into a purpose-built pool, and those tokens are assigned in on-chain escrow to specific devices—no trading, no leverage, just community-backed capacity that brings more machines online, in more places. \ When an node operator requests additional lock for a device, the pool allocates LYK directly to that machine’s escrow. The device runs jobs as normal. A small, pre-set share of the machine’s daily emissions automatically routes back to the pool until the backing is cleared, after which the full emission route returns to the operator. Everything is transparent in-app: who is backed, how much is allocated, and the settlement progress—without moving tokens through user wallets or creating transferable claims. **Why it’s good for the network**\ LBC lowers activation friction and accelerates global coverage. More active devices mean lower latency, higher reliability, and capacity for more powerful workloads—strengthening LayerK's utility while aligning everyone around real work performed by real machines. It’s people-powered liquidity for network growth: simple, transparent, and purpose-built for putting hardware to work. --- # 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.layerk.com/layer-6-distribution-layers/liquidity.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.