> For the complete documentation index, see [llms.txt](https://docs.helix.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helix.org/whitepaper/abstract.md).

# Abstract

<h2 align="center">Helix White Paper</h2>

<p align="center"><strong>Abstract</strong>: <br>Helix is a permissionless, non-custodial lending protocol designed for deployment on the Base blockchain, leveraging Ethereum Virtual Machine (EVM) compatibility. It introduces a novel trustless primitive that prioritizes capital efficiency and architectural flexibility. Unlike conventional lending platforms, Helix enables open market participation and decentralized risk management without reliance on centralized oracle infrastructure by leveraging Chainlink Oracles.The protocols architecture is derived from Aave, but is restructured to emphasize minimalism, immutability, and composability. It functions as a governance-light, static base layer intended to support the development of auxiliary financial primitives and layered protocols. This design enables improved collateral efficiency, dynamic interest rate behavior, reduced gas consumption, and lower latency. Furthermore, Helix expands asset compatibility to include Coinbase-wrapped tokens such as XRP and DOGE, thereby increasing accessibility across diverse asset types.</p>

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><i class="fa-leaf">:leaf:</i></h4></td><td><strong>Introduction</strong></td><td>Intro to Helix Protocol</td><td><a href="/whitepaper/introduction.md">Introduction</a></td></tr><tr><td><h4><i class="fa-plug">:plug:</i></h4></td><td><strong>Motivation</strong></td><td>Why Helix?</td><td><a href="/whitepaper/motivation.md">Motivation</a></td></tr><tr><td><h4><i class="fa-money-bill-wave">:money-bill-wave:</i></h4></td><td><strong>Helix Token</strong></td><td>The native ecosystem token</td><td><a href="/whitepaper/helix-token.md">Helix Token</a></td></tr><tr><td><h4><i class="fa-book">:book:</i></h4></td><td><strong>Smart Contracts</strong></td><td>Helix based smart contracts</td><td><a href="/whitepaper/smart-contracts.md">Smart Contracts</a></td></tr><tr><td><h4><i class="fa-computer-mouse">:computer-mouse:</i></h4></td><td><strong>Supplying &#x26; Borrowing</strong></td><td>Protocol usage</td><td><a href="/whitepaper/smart-contracts/supplying-and-borrowing.md">Supplying and Borrowing</a></td></tr><tr><td><h4><i class="fa-bullhorn">:bullhorn:</i></h4></td><td><strong>Oracles</strong></td><td>Pricing Mechanism</td><td><a href="/whitepaper/oracles.md">Oracles</a></td></tr></tbody></table>

<sup><sub>**Disclaimer**<sub></sup><sup><sub>: Helix is an open-source software project developed on the Base blockchain powered by HLX. HLX tokens are exclusively distributed through mining mechanisms, decentralized autonomous organization (“DAO”) programs, and were allocated during the protocol’s initial launch for immediate functional use within the Helix ecosystem. HLX tokens are intended strictly as governance and utility tokens and are designed solely for use in connection with the Helix protocol. They do not constitute securities, investment contracts, or any other form of securitybased financial instrument under the laws of any jurisdiction. This document does not constitute a prospectus, offering memorandum, or solicitation for investment. It is not intended to be an offer to sell or a solicitation of an offer to purchase any securities, financial products, or regulated instruments in any jurisdiction. There should be no expectation of profit derived from the acquisition or use of HLX tokens. HLX tokens do not represent ownership in any common enterprise, nor do they entitle holders to any ownership interest, dividends, or governance rights outside of the protocol’s intended use cases.<sub></sup>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.helix.org/whitepaper/abstract.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.