> For the complete documentation index, see [llms.txt](https://docs.playscript.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.playscript.xyz/stakes-and-results/vault.md). # The vault One shared vault holds Amazon shares for payouts and PLAY from stakes. There is one vault for every market. Match contracts do not hold the funds. When you lock, your PLAY moves into the vault, and the vault reserves Amazon shares for that script. The vault accepts a call from a match only when that contract is the one the factory would deploy for the match id. There is no separate allowlist. When a script is settled, the vault approves the exact share amount that payout needs. The match cannot pull more than the reserve booked at lock. ## Two balances The vault tracks Amazon shares and PLAY separately. Amazon shares pay winners. Liquidity providers deposit them. Each open script reserves its maximum payout, which is the perfect-script share count. The vault also keeps a 2% floor. Free float is what providers can withdraw: `free float = share balance − open reserves − 2% floor` PLAY is the stake. It sits in the vault, but it is not free float and it is not the prize. After a script settles, PLAY is credited to liquidity providers by the shares they hold. A provider who deposits later does not receive PLAY that was credited before they joined. ## What a lock does to the pool A new stake increases the PLAY balance and increases the share reserve by the perfect-script count at the same time. While the script is open, that reserve is not free float. Providers cannot withdraw shares that might still be owed. When the script loses, the reserve is released and the PLAY stake remains. Those shares become withdrawable again, apart from the floor. When the script wins, the holder is paid from the reserve and any unused reserve is released. Open [Liquidity providers](/stakes-and-results/lps.md) for a full deposit and withdrawal walkthrough. --- # 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.playscript.xyz/stakes-and-results/vault.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.