LogoLogo
  • Entangle
    • Overview
    • Security Audits
  • Universal Interoperability Protocol
    • Overview
    • Architecture
      • Scalability and Network Stability
        • L2 Utility Blockchains
        • Transmitter Groups
      • Security and Consensus Mechanism
      • Finality
      • Execution Latency
      • Compatibility and Interoperability
    • Developer Guides
      • Getting Started
      • Solidity
        • Simple Abstract Messenger Example
        • Deploying Your Custom EVM Protocol
        • Bridging Tokens with UIP
        • Become an EVM Transmitter
      • Solana
        • Simple Abstract Messenger Example
        • Deploying Your Custom Solana Protocol
        • Become a Solana Transmitter
      • Calculate Cross-Chain Transaction Cost
      • Customizable Message Transmission Options
      • How to Debug Sent Messages
      • SDK Setup
      • Revenue Sharing for Transmitters
      • How to Become a Super Transmitter
    • Endpoints
  • Universal Data Feeds
    • Overview
    • Architecture
      • Data Delivery Methods
        • Pull Model
        • Push Model
      • Oracle Contract & User Interaction
    • Developer Guides
      • Custom Data Feeds
      • Fetch Data via Pull Model (PAYG)
        • EVM Smart Contracts
        • Solana Smart Contracts
      • Fetch Data via Pull Model (Subscriptions)
        • EVM Smart Contracts
        • Solana Smart Contracts
      • Fetch Data via Push Model
        • EVM Smart Contracts
        • Solana Smart Contracts
    • User Guides
      • Accessing Feeds
      • Subscribe to a Data Feed
      • Check Subscription
      • Manage Subscription
      • Renew Subscription
    • Data Endpoints
  • Universal Token Standard
    • Overview
    • Architecture
      • Fee Components
    • Developer Guides
      • Manual Deploy
        • Token Deployment Types
        • Create a Custom Token
        • Factory Blueprint Deployment
        • Examples
          • Initial Setup
          • UTS Connector
            • Mint & Burn Connector Scheme
            • Lock & Unlock Connector Scheme
            • Connector Over Native Currency
          • UTS Token
            • Simple Token
            • Token with Messages
      • Bridge SDK
      • Token Verification
      • Fees Calculation & Gas Estimation Logic
      • Estimations
    • User Guides
      • Launch Universal Token
      • Create a Liquidity Pool
      • Expand Existing Token
      • Transfer Liquidity to Connector
      • Bridging
    • Contract Addresses
  • Entangle Interoperable Blockchain
    • Overview
    • Architecture
    • Developer Guides
      • Set up a Validator Node
      • Delegating to Validators
      • Undelegating from Validators
      • Supported Accounts
  • More
    • Media Kit
    • FAQ
    • Report an Issue
    • Become a Partner
Powered by GitBook
On this page
  • Penalty System for Agent Downtime
  • Smart Contract Immutability

Was this helpful?

Export as PDF
  1. Universal Interoperability Protocol
  2. Architecture

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.

PreviousTransmitter GroupsNextFinality

Last updated 1 month ago

Was this helpful?