Peer2Play WhitePaper
  • 📜Introduction
  • ⛔Problem Statement
  • đŸ› ī¸Solution
  • đŸŽ¯Mission and Vision
  • ⚡Key Features
    • Game Tokenization
    • Developer On-Boarding
    • Player-Driven Ecosystem
    • Transparent Revenue Sharing
    • On-chain Tournaments
    • Tokenized Economy
    • Cross-Chain Integration
    • Governance and Incentives
      • GameDAO
      • Incentives
    • Co-Ownership Model
      • Tokenized Games
      • Buybacks and Burns
  • 🤖AI Agents
  • Games
    • âœ‚ī¸Punk Paper(LIVE)
    • 🏏Decentralized Cricket League (DCL)(LIVE)
    • đŸ‹ī¸Chain Duel(Coming Soon)
    • đŸ•šī¸Upcoming Games
  • 🧩Use cases
  • đŸ’ĢGetting started
    • Game Developers
    • Influencers
    • Gamers
  • 👨‍đŸ’ģTechnical Architecture
    • MPC Wallet
    • Smart contract Architecture
      • Peer2PlayGenericStakingContract
        • Chess
        • Poker
        • Ludo
      • Peer2PlayGenericNonStakingContract
        • 1. Role-Playing Game (RPG)
        • 2. City-Building Game
        • 3. Farming Simulations
      • Tokenization & Revenue distribution
    • SDKs & APIs
  • 🔐Compliance & Security
  • ❓FAQ & Troubleshooting
  • 🤝Connect with Peer2Play
Powered by GitBook
On this page
  • Key Features:
  • Key Processes:
  • Security and Reliability:
  1. Technical Architecture

MPC Wallet

Overview of working of MPC Wallet

The Multi-Party Computation (MPC) wallet enhances security by decentralizing key management. Using Shamir's Secret Sharing (SSS) and AWS Key Management Service (KMS), the wallet ensures robust encryption, secure storage, and reliable key recovery.

Key Features:

  1. Secure Key Generation: Uses Web3py with Python to create public/private key pairs.

  2. Key Splitting with SSS: The private key is split into four shares, requiring all shares for reconstruction, enhancing security.

  3. Secure Storage:

    -Backend Share: Stored encrypted in PostgreSQL, backed up with AWS KMS.

    -User Share: Encrypted with a 12-word BIP-39 recovery phrase.

  4. Key Recovery: Combines user-provided recovery phrase and backend shares using Lagrange interpolation to reconstruct the private key.

Key Processes:

  1. Encryption: Backend shares are encrypted with a data key from AWS KMS.

  2. Decryption: Recovery involves decrypting the user key (via the recovery phrase) and backend key (via AWS KMS) to reconstruct the private key.

Security and Reliability:

  1. Four shares are required, preventing unauthorized access if a single share is compromised.

  2. Encrypted storage and AWS backups ensure data resilience and security.

PreviousTechnical ArchitectureNextSmart contract Architecture

Last updated 4 months ago

👨‍đŸ’ģ