Ruby One V2
  • Ruby One V2 - Your Complete Ruby One Wallet Guide
  • General Introduction
    • Vision of Ruby One
    • What is Ruby One V2?
    • What is MPC technology?
    • Is MPC technology secure?
    • What are the benefits of MPC technology?
  • Why Use Ruby One
    • High-Security Wallet Access Through MPC
    • Contract Accounts for Secure and User-Friendly Blockchain Interaction
    • Third-Party DApp Integration with the Ruby DApp Bridge
    • Bridging the Web2-Web3 Gap
  • Tech Introduction
    • MPC-Secret Sharing
    • MPC-Threshold Signature Scheme
    • Social Recovery - DKIM
    • Contract Account Dynamic Upgrade
    • DApp Bridge
    • Ruby One V2 Upgrade Log
  • How to Use Ruby One V2
    • Launch App
    • Sign Up
    • Login Via Google
    • Login Via Email
    • Set Local Password
    • Backup Key Fragments
    • Three Test Networks
    • Send & Receive Crypto
    • Social Recovery Your Account
    • Sign Out & Clear Data
  • Term of Use
    • Welcome to Ruby Protocol
    • About the Website
    • Intellectual Property
    • Acceptable Use of the Website
    • Wallet Address, Private Key, and Backup Capabilities
    • Accuracy of Information Provided by User
    • Your Use of Ruby’s Services
    • Privacy Policies
    • Disclosure of Information
    • Changes and Availability
    • Contacting us via the Website
    • Age Restriction and Eligibility
    • Disclaimer of Warranty
    • Limitation of Liability
    • Changes to the Terms
    • Contact Us
  • Ruby One - MPC Wallet
Powered by GitBook
On this page
  1. Why Use Ruby One

Contract Accounts for Secure and User-Friendly Blockchain Interaction

Building upon our MPC-based private key management system, we've designed an advanced account system that employs contract accounts instead of Externally Owned Accounts (EOAs). This approach carries several significant advantages for institutions and retail users too:

  • High-Level Security through MPC: Contract accounts in our system are controlled by the private key managed via MPC. This architecture means the account's security is as robust as our MPC-based private key system, which requires at least two out of three key shares to access the account.

  • Social Recovery of Lost Private Key: By designing the system to allow for social recovery, we've introduced a solution for the potential loss of the private key. If users lose their private key, they can recover access to their account through social media mechanisms, such as DKIM email verification. This feature enhances both security and usability.

  • Flexible Gas Payment Options: Our system allows gas payments through the Ruby server, which provides users with various payment options. Users can pay gas fees using ERC20 tokens or other methods without buying ETH, thereby simplifying transaction costs.

  • Transaction Privacy through Unified Relay: We've implemented a unified relay system to send transactions, allowing users to conceal their addresses and IPs. This system enhances privacy and provides an additional layer of security.

By adopting contract accounts controlled by an MPC-managed private key system, we offer users more secure, user-friendly, and versatile experiences when interacting with blockchains. This solution combines the strengths of our MPC-based private key system with the flexibility and user-centric benefits of contract accounts, delivering an unmatched blockchain experience for our users.

PreviousHigh-Security Wallet Access Through MPCNextThird-Party DApp Integration with the Ruby DApp Bridge

Last updated 1 year ago