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

# mTransactions

mTransactions is an exploration of a bandwidth marketplace for transactions on the Solana blockchain

{% hint style="warning" %}
**Note:** mTransactions is currently paused and unavailable. The documentation below is kept for reference purposes only.
{% endhint %}

The feature was released earlier as an **open beta** to explore new transaction capabilities within the Marinade ecosystem. At this time, the service has been **temporarily paused and is not active**.

## **What are mTransactions**

mTransaction is an open-source RPC-like service that connects transaction senders and validators with stake on their nodes. It takes advantage of the [QUIC and QoS updates](https://medium.com/chorus-one/how-will-solana-improve-its-stability-6d4b0ba41866) that were added to Solana in 2022 and 2023.

Participating users are able to send transactions to the mTransaction service, which will redirect them to one of the participating validators. This validator will use his staked node to forward the transaction to the leader through a QUIC connection. 

### Github repository

{% embed url="<https://github.com/marinade-finance/mtransaction>" %}
mTransactions repository
{% endembed %}


---

# 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.marinade.finance/marinade-protocol/protocol-overview/mtransactions.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.