> For the complete documentation index, see [llms.txt](https://docs.jetbit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetbit.com/security-and-self-custody.md).

# Security and Self-Custody

Jetbit is built so that you hold your own funds and can verify the platform's numbers yourself. This page covers how custody works and how to check things on-chain.

## Your keys, your funds

When you trade through the vault, you connect your own wallet and your USDT moves through an on-chain vault contract. There is no custodial deposit address and no third party holding your keys. You authenticate by connecting a wallet, not by handing over an email and password.

## How deposits and withdrawals are protected

Deposits are verified on-chain before they count. The engine reads the confirmed deposit receipt from the blockchain before crediting your balance, so a deposit is never taken on trust and can never be counted twice.

Withdrawals are backed by real funds. The amount you can withdraw is the lesser of your free margin and the balance backed by USDT in the vault. Small withdrawals pay out right away. Larger withdrawals above a set size go into a short review queue and are released by a multisig, which is a deliberate check on unusually large outflows.

## Verify it yourself

Every headline figure on Jetbit, from pool TVL to vault balances, is a live contract balance you can open on BscScan. The status bar at the bottom of every screen shows network status, gas, the current block, and oracle health, so you can always see that prices are live and the chain is current.

Only a few of Jetbit's contracts ever hold USDT. The vault holds trader funds, the pool holds liquidity, the reserve holds the insurance slice, and the fee collector holds fees on their way to the treasury. The rest handle bookkeeping and never custody funds.

## Contract addresses

You can verify Jetbit's contracts on BscScan at the addresses below.

| Contract        | Address                                    |
| --------------- | ------------------------------------------ |
| Vault           | 0x991e3e0A16D729a0872CA7A3B58EF31A19A64C7E |
| Pool            | 0x075A553CC4E1F3EE70B21E1472E1c85c73d53B2C |
| Reserve         | 0x0bE292625D6d3b073BeBC40bd6F234095a2bb548 |
| FeeCollector    | 0x04b6E0C452aCdceE8b7641E3E61332B138DA9878 |
| LPStaking       | 0x3b3105b0A3e8b8De1f6E0C904413df21629918F4 |
| TraderVault     | 0x2Ee5Cd1CB60528636d119FFEeE0780B18629e638 |
| LPPositionNFT   | 0xAC5E47374cf48D930411f1BFd582361226eBE5E0 |
| AccessManager   | 0xE402514141DbC5295001d5Bb18f3ad644e9dDb9B |
| AddressRegistry | 0x763Dc364425b2b0b7ad11b8ebcb8A86d56B1eB17 |


---

# 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://docs.jetbit.com/security-and-self-custody.md?ask=<question>&goal=<endgoal>
```

`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.