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

# Security

Silo's smart contract architecture separates fund-touching contracts from business logic contracts. Vault contracts that interact with user funds are designed to be immutable once deployed. Business logic contracts (routing, fee calculation, tier enforcement) are upgradeable via proxy patterns, allowing the platform to evolve without compromising the security of fund-holding infrastructure.

Silo's privacy layer uses zero-knowledge proofs to create on-chain unlinkability between deposits and withdrawals. The ZK commitment and proof system ensures that withdrawals can only be executed by the designated wallet, and that no on-chain observer can link a specific withdrawal to a specific deposit.

Encrypted transaction records (Payment Instructions) are stored using SEAL encryption on Walrus, Sui's decentralized storage layer. This ensures that records are encrypted at rest, durable across decentralized infrastructure, and not dependent on a single server or database.

Cross-chain transfers are routed through CCTP (Circle's Cross-Chain Transfer Protocol), the most widely audited bridge protocol for USDC transfers. Silo does not use third-party bridges with unaudited or experimental security models.

KYC verification is handled through Sumsub. Transaction screening (KYT) is handled through TRM Labs. Silo does not build or maintain its own identity verification or transaction monitoring infrastructure — these functions are delegated to established, purpose-built providers.

***

#### **Audits**

Silo's smart contracts are undergoing security review. Audit reports will be published on this page when complete. Silo is committed to transparency around its security posture and will make all audit findings publicly available.

***

#### **Responsible Disclosure**

Information on Silo's responsible disclosure and bug bounty program will be published here when the program is live.

<br>


---

# 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.silopay.io/resources/security.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.
