Skip to main content
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), Circle’s canonical burn-and-mint 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 two independent providers, TRM Labs and CipherOwl, so screening remains available even if one provider is down. 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.