# Safety You do not know and trust everyone that posts a deal. So, we need to add some protections for investors. With protections in place, we can build trust and collaboration as the deal progresses. The protocol includes several layers of protection. ### Featured deals Featured deals are qualified by our arbitrators. They have reliable, reachable, and committed founders. They are designed to offer token holders good economics and governance. ### Smart contract security The [smart contracts](https://github.com/SurgeProtocol/core-contracts/tree/onetxconfig) are designed and [audited](https://github.com/SurgeProtocol/core-contracts/tree/main/audits) to give stakers a lot of ways to get money back. * Stakers can "unstake" any time before closing. * Stakers can "unstake" from any canceled deal. The protocol, the arbitrator, and the deal sponsor can cancel a deal at any time if they see problems. * Deals are canceled 7 days after closing. So, if a deal closes and something does not work correctly in the delivery, stakers can unstake. The only time that the smart contract will send assets to someone that is not the staker is in the seven days after a successful closing. In this case, the smart contract will run a delivery process to swap assets, and it will send the "claimed" or swapped stakes to an arbitrator address. ### Stake to your own wallet Tweet.fund stakers are staking into their own wallet. The protocol adds the staked assets to a "token bound account" that is attached to an NFT, and puts that NFT into the staker's wallet. The NFT holds a place line to buy the deal, before there is a transaction. It postpones accounting, legal, and compliance obligations until deal closing. ### Arbitrators On closing, assets go to a multisig treasury that is controlled by an arbitrator. This makes it difficult for an insincere sponsor to get money. The arbitrator can manually refund assets. The arbitrator will hand off the assets to the deal sponsor when the sponsor demonstrates reliability and governance that protects buyers. Learn more about this way of building [reliable ICOs](/reliable-icos.md). --- # Agent Instructions: 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.taiser.ai/safety.md?ask= ``` 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.