Mind Network Docs
  • 🧠 What is Mind Network
  • Background
    • 🔐 HTTPZ
  • 🚀 Challenges and Solutions
  • Research
    • 📚 FHE Research
      • FHE 101
      • FHE Validation
      • FHE Consensus
      • FHE Chain
      • FHE Transaction
      • FHE Scheme
      • FHE Data
  • Product
    • 🛠️ Product Overview
    • 🌐 AgenticWorld 🔥
      • AgenticWorld User Guide
        • DeepSeek Hub
        • Agent Launch @ Mainnet
        • Agent Launch @ Testnet
      • Rewards Rule
      • Revenue and Payment
      • Bridge
    • ⛓️ MindChain
      • MindChain Developer Guide
    • 🌉 FHEBridge
      • FHEBridge Guide - Transfer
      • FHEBridge Guide - Bridge
      • FHEBridge Guide - Manage
    • MINDV (Ended)
      • MindV User Guide (Ended)
      • vFHE Explanation (Ended)
  • Usecase
    • DeepSeek Integrates FHE Rust SDK
    • MindX - Encrypted LLM
    • AI Agents Framework: ElizaOS and Virtuals
    • Multi-Agents: Swarms Shield Hub
    • World AI Health Hub
    • Fair Randomness in Decentralized Systems
    • FHE+TEE: Security in Decentralized AI Governance
    • Decentralized GPU Computation
    • MindLake - FHE Encrypted DataLake
  • Data Encryption
  • Crosschain Infra
  • Storage Secruity
  • Governance
    • $FHE
    • Tokenomics
    • Get $FHE
  • Community
    • 🪪 CitizenZ
    • 🎙️ FHECon
    • 🎤 X On My Mind
  • Deverloper Guide
    • Developer Overview
    • Hub Tutorial
      • SDK For Hub Framework
      • Validator Tutorial - Randgen Hub Voter as the example
  • Consensus Tutorial
  • Security and Privacy
    • Audit - FHEBridge
    • Audit - Restake
    • Multi-Sig & Timelock
    • Terms of Service
    • Privacy Policy
    • Mind Network Airdrop Terms of Service
    • Mind Network Airdrop Privacy Policy
  • Other
    • Airdrop User Guide
    • Early-bird Rewards
    • FAQ
    • Official Links
    • Brandkit
Powered by GitBook
On this page
  • Ethereum
  • Scroll

Was this helpful?

  1. Security and Privacy

Multi-Sig & Timelock

Mind Network has implemented a proxy-based approach for the contracts to minimize the impact of any unforeseen issues.

To further enhance security, all permissions related to contract upgrades and administrative functions are managed by a 48-hour timelock controlled by a 2/3 multi-signature mechanism.

When there is a need for a contract upgrade or administrative configuration, the team initiates the request, and the designated multi-signature signer proposes the desired changes with a 48-hour timelock. During this 48-hour period, users have the option to decide whether they want to continue using the contract or opt out. Once the 48 hours have elapsed, the proposed upgrade or configuration change takes effect on-chain.

Ethereum

Contract

Address

Multi-Sig

0xE00b18EfedFE68Aa3e835880cDEC49f06DF6C758

Timelock

0x7bc0591102901979259986343FF64351E9757901

Scroll

Contract

Address

Multi-Sig

0x2Ed0587Be9c4502E6799Cf92552AdA0B75E343B8

Timelock

0x69F2F54B681Ac23700E6082743F496d8fd78BeA0

PreviousAudit - RestakeNextTerms of Service

Last updated 2 months ago

Was this helpful?