# Security and Consensus Mechanism

UIP introduces a two-tier consensus model:

* **Agent Signatures**: Regular agents execute and transmit messages across networks, ensuring that all operations are verified collectively to reduce risks of manipulation.
* **Super-Agent Signatures**: Super-agents validate transactions to add trust and mitigate risks, particularly in the protocol's early stages.

This consensus structure enhances network security by requiring signatures from both agents and at least one super-agent. When executing cross-chain messages, the process includes:

* **Transmitters Consensus**: Ensures reliable message delivery with sufficient gas for execution.
* **Executors Consensus:** Validates message legitimacy and appropriate pricing on the destination chain.

## Penalty System for Agent Downtime

To maintain network stability, UIP enforces a penalty system for agents experiencing extended downtime (over one hour). The penalties incentivize agents to maintain uptime, adopt proactive maintenance, and minimize service disruptions, enhancing the network's resilience and reliability.

## Smart Contract Immutability

The Master Smart Contract, UIP's immutable core, ensures tamper-resistance, transparency, and trust for seamless omnichain operations.

1. **Resistance to Tampering**: Once deployed on the blockchain, smart contracts cannot be altered or deleted. This immutability ensures that the terms of the contract remain intact and cannot be manipulated by any party, reducing the risk of fraud and unauthorized changes.
2. **Transparency**: The code of the smart contract is publicly accessible on the blockchain. This transparency allows all participants to view and verify the contract's terms, fostering trust among parties and minimizing disputes regarding contract interpretation.
3. **Reduced Risk of Manipulation**: Since smart contracts are self-executing and governed by code, there is little room for manipulation by external parties. This characteristic is particularly beneficial in scenarios where trust is a concern, as it ensures that outcomes are determined solely by the coded logic of the contract.


---

# 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.entangle.fi/universal-interoperability-protocol/architecture/security-and-consensus-mechanism.md?ask=<question>
```

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.