> For the complete documentation index, see [llms.txt](https://docs.sivax.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sivax.io/overview/why-xrpfi.md).

# Why XRPFi

XRP has long been associated with payments, settlement efficiency, and fast asset movement. For the ecosystem to mature, it needs an income layer that users can stay in and understand.

> *SIVAX bridges that gap by contributing to a broader vision of XRPFi: building financial products that make holding XRP more useful, more productive, and more sustainable over time.*

Users face a tradeoff between centralized earn products and generic DeFi strategies, each with clear limitations.

| Centralized earn products | Generic DeFi yield strategies | SIVAX approach                              |
| ------------------------- | ----------------------------- | ------------------------------------------- |
| Feel simple               | More open, but complex        | Easier to access                            |
| Depend on custody         | Opaque and hard to verify     | Easier to follow                            |
| Limited transparency      | Inconsistent or unstable      | Better aligned with an always-on experience |
| Hard to inspect           | Difficult to evaluate         | Designed for clarity                        |

### The SIVAX Approach

XRPFi lacks a usable income layer that allows users to stay invested and benefit over time.&#x20;

The SIVAX approach is centered on a fund-type product rather than a sequence of isolated product decisions. Users enter a single product and remain in a strategy that operates over time, enabling continuous participation in a managed income strategy.

### Why XRPL

XRPL is a strong foundation for this model. A continuously managed income strategy depends on efficient settlement, transparent asset movement, and infrastructure that supports ongoing portfolio activity.&#x20;

It enables frequent asset movement, clear asset handling, and a more transparent operating environment than traditional structured product workflows.

For SIVAX, XRPFi is about giving users a product they can actually use:

* A simpler point of entry,
* Ongoing participation instead of repeated rebuilding,
* Visible portfolio status,
* And a structure that is designed to keep working as market conditions change.

### The Fund Product&#x20;

Structured income is a core part of XRPFi.

It shapes exposure through defined strategy logic, active allocation, and risk management across changing market conditions. SIVAX applies this within a managed product without exposing users to the full complexity of product construction.

The main XRPFi experience in SIVAX is the fund product, designed for users who want a managed and continuously operating income strategy.

{% hint style="info" %}
Custom-built structures may also be supported for qualified use cases that require more specific payoff design or product-level control. This remains a separate capability rather than the default experience.
{% endhint %}

A credible XRPFi layer connects asset ownership to a real financial experience, giving users a reason to remain active in the network through products designed for ongoing participation.


---

# 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:

```
GET https://docs.sivax.io/overview/why-xrpfi.md?ask=<question>
```

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.
