> ## Documentation Index > Fetch the complete documentation index at: https://docs.safefoundation.org/llms.txt > Use this file to discover all available pages before exploring further. # Safenet results > Understand the results Safenet can return and what each means for transaction execution. Safenet derives a result from Sentinel checks of the same proposed transaction. The result determines whether Validators attest the transaction so it can execute through Safenet, whether it enters arbitration, or whether it cannot be treated as secure. ## Result states ```mermaid theme={null} flowchart LR A["Sentinels check transaction"] --> B{"Safenet result"} B -->|"All return secure"| C["Validators attest transaction"] C --> D["Can execute through Safenet"] B -->|"All return insecure"| E["No Validator attestation"] E --> H["Cannot execute through Safenet"] B -->|"Sentinels disagree"| F["Arbitration / no Validator attestation"] F --> H B -->|"Check cannot complete reliably"| G["Not treated as secure"] G --> H ``` *The four Safenet result states and their execution outcomes.* The four high-level outcomes are: * **Secure:** all participating Sentinels return secure. * **Insecure:** all participating Sentinels return insecure. * **Split:** Sentinels disagree and the transaction enters arbitration. * **No reliable result:** Safenet cannot complete the check reliably. Only a secure result can be attested by Validators and execute through Safenet. ## Secure results A transaction receives a secure result when all participating Sentinels determine that it satisfies every applicable [Charter](https://github.com/safe-research/safenet-charter) rule. Validators can then attest the secure result using FROST threshold signing. The resulting attestation is bound to the exact Safe, network, and transaction. If the Safenet Guard is enabled, a valid Validator attestation allows the transaction to execute through Safenet. ## Insecure results A transaction receives an insecure result when all participating Sentinels determine that it violates at least one applicable Charter rule. An insecure result: * Receives no Validator attestation. * References at least one violated Charter rule. Without a Validator attestation, the transaction cannot execute through Safenet. The delayed execution and exit path is unaffected, so owners remain in full control of their Safe. Sentinels agree on whether the transaction is secure or insecure. Each Sentinel should explain its verdict, but explanations do not need to be identical across Sentinels. See [Safenet checks](/safenet-aegis/use-safenet/transaction-checks) for the risks Safenet evaluates. ## Split results and arbitration A result is split when Sentinels disagree on whether the transaction is secure. Split results enter Safenet's arbitration process and receive no Validator attestation, regardless of the arbitration outcome. The transaction therefore cannot execute through Safenet. The delayed execution and exit path is unaffected, so owners remain in full control of their Safe. The arbitration process can resolve the dispute, but it does not turn the original split result into a Validator-attested secure result. ## No reliable result Safenet does not treat an incomplete or unsuccessful check as secure. This includes cases where a transaction is: * Unsupported or outside Safenet's current scope. * Malformed. * Incomplete. * Timed out. * Affected by a technical failure. These states are distinct from an insecure result: Safenet has not concluded that the transaction violates the Charter. It has been unable to produce a reliable security result. Without a valid secure attestation, the transaction cannot execute through Safenet. The delayed execution and exit path is unaffected, so owners remain in full control of their Safe. Understand how Safenet results are enforced onchain. Learn about the participants that perform Safenet checks.