> For the complete documentation index, see [llms.txt](https://docs.railgun.org/wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.railgun.org/wiki/learn/using-private-tokens/gasless-interactions.md).

# Gasless Interactions

Another major innovation deployed by the RAILGUN system is the ability to send interactions without needing to spend the underlying blockchain’s gas currency. Through the power of Broadcasters and complex ZK circuits, users can interact with RAILGUN entirely in their currency of choice. For example, a user would not need to hold a small balance of ETH to submit gas for interactions on the Ethereum network and could instead choose to only hold and spend a stablecoin like DAI, with all associated gas being submitted in DAI.

This is achieved through something called a “Meta Transaction”, a special form of Ethereum/blockchain transaction that is nested within another transaction. The gas fee can be paid in whatever asset the user specifies with the Broadcaster and nested transaction performing any conversion frictionlessly for the user. Like any other spend transactions, a Meta Transaction in RAILGUN calls the transact() function.


---

# 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.railgun.org/wiki/learn/using-private-tokens/gasless-interactions.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.