> For the complete documentation index, see [llms.txt](https://praxxas.gitbook.io/killswitch/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://praxxas.gitbook.io/killswitch/f.a.q/gas-escrow.md).
# Gas Escrow
## How is gas handled?
It's a good question, one we pondered when conceptualizing KillSwitch. There were a few options but we settled on utilizing an escrow smart contract setup.
Essentially, the wallet owner loads that escrow contract with however much of the gas token of the chain is (ETH for Ethereum for example). It sits untouched and available at absolutely any time to them for withdrawal. When a trigger is executed on behalf of the wallet owner by KillSwitch, the gas is calculated to be used that quantity withdrawn from the wallet owners escrow quantity and routed to the KillSwitch Gas Wallet to replenish what was used. If a trigger is executed directly from the owners' wallet, the gas is being paid by the owner and not KillSwitch on their behalf, thus the gas in the escrow contract remains untouched.
This means if the escrow is not filled, KillSwitch performing triggers on the owners' behalf aren't possible. This can be mitigated a few ways of which we're integrating such as grace triggers, essentially performing it for free. These are likely to be earned per subscription tier or promotional events.
## Does my gas expire?
No. From the time you deposit, if we don't execute a remote trigger on your behalf, then the gas deposited remains untouched. The gas is in that contract for a single purpose: refunding KillSwitch for remote triggers on the owners' behalf.
## I transferred gas to the contract but don't see it as deposited?
Please request support for this. If we can verify the gas resides within the contract from your wallet, we can submit a ticket to those who have control of those wallets and they can recover the funds.
---
# 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, and the optional `goal` query parameter:
```
GET https://praxxas.gitbook.io/killswitch/f.a.q/gas-escrow.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.