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

# wallet sessions

The current Sui integration uses explicit wallet signatures. There is no production session-key system that gives a browser continuous authority to trade on behalf of a user.

“One-click Buy/Sell” describes a simple trading action. It does not mean that wallet approval is bypassed, that gas is free, or that a transaction executes instantly.

## The current approval boundary

A user reviews and signs the Sui transaction that opens, closes, claims, or withdraws.

The application must bind the following to the transaction actually signed:

* Network
* Package
* Vault
* Sender
* Margin source
* Amount
* Price constraints

A transaction assembled for one network or deployment must not be reused against another.

Cross-chain deposits also require source-chain approvals or burn authorization, followed by destination receipt. An EVM approval must specify the correct USDC contract and permitted spender; it is not a GetRekt trading session.

## Requirements for a future session feature

A scoped trading session would need:

* Explicit opt-in
* Expiry
* Revocation
* Action and amount limits
* Market and deployment binding
* Replay protection
* Clear key custody

Withdrawal and administrator authority must not be implied by permission to trade.

{% hint style="warning" %}
Those controls require Sui-specific contracts and wallet integration. Papertrade's EVM session-key design is not automatically available on Sui.
{% endhint %}

Until a verified implementation is released, the documentation and interface must continue to require normal wallet approval. [Integration](broken://pages/f2e97be1c7dbb94457b8693d9a73abcdc212583d).


---

# 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.getrekt.trade/wallet-sessions.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.