> For the complete documentation index, see [llms.txt](https://docs.stacks.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stacks.co/learn/sbtc/auxiliary-features/transaction-fee-sponsorship.md).

# Transaction Fee Sponsorship

Transaction Fee Sponsorship is a feature in sBTC that allows users to pay for Stacks transaction fees using sBTC instead of STX.

## Overview

* sBTC transactions on Stacks can be sponsored in return for some sBTC.
* This feature improves user experience by allowing sBTC holders to use their tokens for gas fees.

## Implementation

The fee sponsorship system is implemented using the approach suggested in [stacks-network/stacks-core#4235](https://github.com/stacks-network/stacks-core/issues/4235).

{% stepper %}
{% step %}
**Sponsor support for fees**

sBTC users can get support from existing STX holders for transaction fees.
{% endstep %}

{% step %}
**Sponsor receives sBTC**

The sponsor pays the STX fee and receives sBTC in return.
{% endstep %}
{% endstepper %}

## User Experience

From a user's perspective:

{% stepper %}
{% step %}
**Opt into fee sponsorship**

When initiating an sBTC transaction, they can opt for fee sponsorship.
{% endstep %}

{% step %}
**Agree to sponsorship terms**

The user agrees to pay a small amount of sBTC for the sponsorship.
{% endstep %}

{% step %}
**Transaction processed**

The transaction is then processed with the fees paid in STX by the sponsor.
{% endstep %}
{% endstepper %}

## Benefits

* Improved UX: Users don't need to hold STX to use sBTC.
* Lower Barrier to Entry: New users can start using sBTC without first acquiring STX.
* Flexibility: Provides an additional option for handling transaction fees.


---

# 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.stacks.co/learn/sbtc/auxiliary-features/transaction-fee-sponsorship.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.