☁️
Zus Docs
  • About Züs
  • System
    • Providers and Services
      • Miner
      • Sharder
      • Blobber
      • Validator
      • Authorizer
      • Node Locator (0DNS)
    • Storage
      • Architecture and Data Management
      • Protocol
        • Allocations
        • Reference Objects
        • Challenges
        • Write Markers
          • Chain Hashing
          • Two Commit
        • Blobber Repair Protocol
      • ZS3 Server
        • Backup, Recovery and Replication
        • Encryption and Compression
        • S3FS Setup and Usage
        • Backup & Recovery with Restic on Blimp + ZS3 Server
        • Backup & Recovery with Veeam on Blimp + ZS3 Server
      • File Operations
        • Upload
        • Download
        • File Sharing
        • Partial Error Recovery
        • Streaming
        • Rent a Blobber
    • Smart Contracts
      • Storage S.C.
      • Miner S.C.
      • ZCN S.C.
      • ERC-20 S.C.s
      • Bridge Protocol
    • Blockchain & Consensus
      • Entities
    • User Authentication and Wallet Management System
      • OKTA Integration
      • Key Management System (KMS)
  • APIs
    • 0DNS API
    • JS API
    • Mobile API
  • CLIs
    • Storage CLI
      • Quickstart
      • Configuring the tool
    • Wallet CLI
      • Wallet Configuration
      • Quickstart
      • Configuring the tool
  • SDKs
    • Go SDK
      • GO SDK Microservices
    • JS SDK
  • Tokenomics
    • Staking
    • Reward & Penalty
  • ✨Züs Apps
    • 🗝️Vult
      • Getting Started
        • Web
        • Mobile
      • Vult AI
        • Batch Processing
        • Memory Retention
        • Technical Implementation
        • Architecture Overview
      • Login / Register
      • File Management Pages
      • File Sharing
      • Storage Management Dashboard
      • Storage Maintenance and Troubleshooting
      • Züs Subscription
      • Wallet Management
      • Refer a friend
      • Settings
    • 🏗️Blimp
      • Getting Started
      • Login / Register
      • Configure Storage
        • Create Standard Storage Allocation
        • Create Enterprise Allocation
        • Create S3 Server Allocation
        • Create Cloud Migration Allocation
        • Allocation Maintenance and Troubleshooting
      • File Management Pages
      • File Sharing
      • Manage Allocations
      • Upgrade Storage
      • Blimp Vault
      • Refer a friend
      • Settings
      • Launching ZS3 Server
      • Using CLI to backup files into Blimp + ZS3 Server
    • 🏠Chimney
      • Getting Started
      • Login / Register
      • Create New Deployment
      • Manage Your Deployments
      • Homepage
      • Staking Dashboard
      • Rank Dashboard
      • Monitor Dashboard
      • Stats Dashboard
      • Logs Dashboard
      • Wallet Dashboard
      • Operations on your Deployments
      • Restricted Blobbers
      • Settings
        • Manage Profile
        • Wallet Settings
        • Update Blobber Settings
        • Update Blobber Version
        • Refer a friend
        • Help
    • 🌐Atlus
      • Getting Started
      • Home page
      • Service Providers Page
      • Charts Page
        • Market Charts
        • Network Charts
        • Storage Charts
      • Blockchain Page
      • Server Map Page
      • Storage Explainer Page
      • Details Pages
        • Block Details Page
        • Transaction Details Page
        • Wallet Details Page
        • Miner Details Page
        • Sharder Details Page
        • Blobber Details Page
        • Validator Details Page
        • Authorizer Details Page
        • Allocation Details Page
      • Appendix: Common Components
    • ⚡Bolt
      • Getting Started
        • Web
        • Mobile
      • Login / Register
      • Sign In with external wallet
      • Staking Dashboard
      • Staking/Unstaking a provider
      • Claiming Rewards
      • Send/Receive ZCN tokens
      • Buy ZCN
      • Deposit/Withdraw ZCN tokens
      • Activity Dashboard
      • Refer a friend
      • Settings
  • Releases
    • Hardfork
Powered by GitBook
On this page
  • Signing Burn and Mint Tickets:
  • Validation Process:
  • Asymmetric Key Encryption:
  • Integration with Smart Contracts:
  • Rewards and Penalties:
  1. System
  2. Providers and Services

Authorizer

This page provides a high-level overview of the authorizer node's structure and functionality, ensuring clarity on its role within the Züs network.

PreviousValidatorNextNode Locator (0DNS)

Last updated 8 months ago

The authorizer node plays a crucial role in the token bridge protocol by validating and signing burn and mint tickets. It ensures the integrity of transactions by verifying burn transactions on the Ethereum blockchain (ERC-20 tokens) and issuing proof-of-burn tickets to clients. These tickets are then used to mint new tokens on the Züs blockchain (ZCN tokens). The authorizer node's validation is essential for maintaining the trust and security of the bridge protocol, enabling seamless token conversions between the Ethereum network and the Züs blockchain.

Fig1: The chart illustrates the authorizer node's role in converting WZCN (ERC-20 tokens) to ZCN (native Züs tokens) in the token bridge protocol.

Below is a detailed description of its functionality:

Signing Burn and Mint Tickets:

  • Burn Tickets: When a user wants to convert WZCN tokens (ERC-20) to ZCN tokens (native to the Züs blockchain), they first burn the WZCN tokens. This generates a burn ticket, which the authorizer node must sign.

  • Mint Tickets: Conversely, when a user wants to convert ZCN tokens to WZCN tokens, they burn the ZCN tokens to generate a mint ticket, which also requires the authorizer node's signature.

Validation Process:

  • Verification: The authorizer node verifies the validity of burn and mint tickets by checking the corresponding smart contracts on the Ethereum network or the Züs blockchain.

    • For burn tickets, the authorizer node ensures that the tokens have indeed been burned and that the transaction is recorded in the smart contracts.

    • For mint tickets, the node verifies that the ZCN tokens have been burned in the native network's smart contracts.

Asymmetric Key Encryption:

  • Signing Tickets: The authorizer node uses asymmetric key encryption for signing tickets. It signs the tickets using its private key.

  • Verification by Smart Contracts: The validity of these tickets is then confirmed by smart contracts using the authorizer node's public key.

Integration with Smart Contracts:

  • The authorizer node interacts with smart contracts deployed on both the Ethereum network and the Züs blockchain.

  • It ensures that the burn and mint tickets are properly recorded and validated, maintaining the integrity of the bridge protocol.

Rewards and Penalties:

  • Reward Mechanism: Authorizer nodes are rewarded based on the tickets they sign. The rewards are distributed as transaction fees, paid in ZCN for ZCN mint transactions and in ether for WZCN mint transactions.

  • Penalties: If the authorizer fails to validate and sign tickets correctly, they may face penalties as outlined in the governance protocol.