> For the complete documentation index, see [llms.txt](https://docs.sweep.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sweep.finance/system-architecture/transparency-and-verifiability.md). # Transparency & Verifiability Sweep implements a **verifiability and transparency mechanism** designed to ensure that all critical system operations are observable, traceable, and independently auditable at the protocol level. The platform is built on **blockchain-based infrastructure**, where all relevant transactions and system-level actions are recorded on-chain. This ensures that once executed, data cannot be altered, removed, or retroactively modified. As a result, system behavior is not dependent on internal claims, but on **publicly verifiable execution**. All interactions within Sweep—ranging from gameplay activity to value distribution—are processed through a combination of **on-chain transactions and predefined logic**. This structure enables users and external observers to verify system activity without relying on centralized trust. *** ### **Blockchain-Based Verifiability** Sweep operates on the **BNB Smart Chain (BSC)** network. Every relevant action generates a verifiable blockchain record, creating a transparent and immutable audit trail. This ensures that: * Transactions are **publicly accessible and traceable** * Recorded data **cannot be modified after execution** * System activity can be **independently verified at any time** This approach establishes a clear distinction between Sweep and traditional closed systems, where internal operations are not externally observable. *** ### **Rule-Based Execution & Smart Contracts** Core platform mechanisms are governed by **predefined rules and smart contract logic**. This eliminates discretionary control over outcomes and ensures consistent execution across all system operations. Under this model: * Outcomes are generated through **deterministic, rule-based processes** * Execution is **automated and not subject to manual intervention** * System behavior remains **consistent and predictable** By removing arbitrary human control, Sweep reduces the possibility of hidden manipulation and reinforces structural integrity. *** ### **Non-Custodial Architecture** Sweep is designed as a **non-custodial system**, meaning user assets are never held or controlled by the platform. Users interact directly through their own wallets, and all transactions are executed on-chain. This ensures: * Full **user ownership and control of assets** * Elimination of **counterparty custody risk** * Direct interaction with the protocol without intermediary control *** ### **Provable Fairness Framework** Sweep’s architecture is built to support a **provably fair interaction model**, where outcomes are determined by transparent logic rather than hidden processes. In this context, provable fairness means that: * System behavior follows **predefined and observable rules** * Outcomes are not influenced by **manual decisions or operator intervention** * Critical actions are supported by **verifiable on-chain activity** Unlike traditional platforms, where users must rely on trust, Sweep provides a structure where outcomes can be **supported by observable data and system logic**. It is important to note that fairness refers to the **consistency of execution**, not the guarantee of favorable outcomes. Users may still experience varying results depending on the mechanics of the system they engage with, but those results are generated within a transparent and rule-based framework. *** ### **System-Level Transparency** Transparency within Sweep is not presented as a claim, but as a **structural property of the system**. All core processes—including transaction flow, distribution mechanisms, and outcome generation—are tied to observable execution. This ensures that: * System operations are **not hidden behind centralized control** * Users can rely on **verifiable data rather than assumptions** * Platform behavior is constrained by **protocol-level rules** --- # 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.sweep.finance/system-architecture/transparency-and-verifiability.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.