Qtum Documentation
  • Qtum Features and Advances
    • Qtum Ordinals
      • Chapter 1: Introduction to ordinals
      • Chapter 2: Understanding Inscriptions in Depth
      • Chapter 3: The Intricacies of Ordinals on the Blockchain
      • Chapter 4: Engineering Ordinals within Qtum's Architecture
      • Chapter 5: Prerequisites for Engaging with Ordinals on Qtum
      • Chapter 6: The Procedure for Inscribing a Satoshi with Ordinals
      • Inscribing Messages on Qtum Testnet
    • Qtum-BIP38
  • Qtum Wallet
    • Qtum-Core Wallet Documentation
      • Qtum Documentation
      • Using Qtum Wallet
      • Linux Repositories
      • Qtum on Raspberry Pi
      • How to Update Qtum
      • Qtum Wallet Best Practices
      • Qtum Wallet Commands
      • Adding Nodes To Qtum Wallet
      • Encrypt & Unlock Qtum Wallet
      • Recovery wallet data with salvagewallet
      • Testnet User Guide
      • Bech32 Addresses support
      • How to Add Options (Config)
      • How to use Bootstrap
  • Staking and Nodes
    • Secure Staking With Qtum Star Network
    • Staking Documentation
      • Qtum Staking
      • Offline Staking
      • Offline Staking Address Delegation - Undelegation Transaction Details
      • Qtum on AWS ec2
      • Staking with a VPS
      • Staking with a Raspberry Pi
  • Other Wallets
    • Wallets Supporting Qtum
      • Electrum
      • Qtum Web Wallet
      • Qtum Lightning Network
  • RPC CALLS AND API
    • QTUM RPC CALLS
    • QTUM RPC API
  • Qtum Deployment
    • Guidance on Qtum Deployment
    • Building Qtum on Linux
    • Guidance for Exchange Deployment
  • Smart Contracts and QRC20 Tokens
    • QRC20 Token integration
    • QRC20 Integration Technical Guide
    • Raw QRC20 Transaction implementation guide
  • WEB3
    • Web3 Compatibility Layer
    • Janus Docker Container
    • Truffle
    • Differences between EVM chains
  • QNEKT
    • QNEKT
    • Why Fork Metamask ?
    • Sideloading Qnekt
    • Setting up QNEKT
    • Working with Testnet Coins on QNEKT
    • Connecting QNEKT to regtest
    • QNEKT Regtest with react-box
  • Research
    • Confidential Assets
    • Data Analytics
Powered by GitBook
On this page
  • EC-multiply modes.
  • How it works
  • Why it's important
  1. Qtum Features and Advances

Qtum-BIP38

https://github.com/qtumproject/qtum-bip38 A Python library for implementation of BIP38 for Qtum. It supports both No EC-multiply and

EC-multiply modes.

BIP38 (Bitcoin Improvement Proposal 38) is a cryptographic standard that defines a method for encrypting and securing private keys associated with Qtum addresses. It provides a way to create encrypted versions of private keys, which can then be decrypted using a passphrase. This adds an additional layer of security to the process of storing and transmitting private keys.

By encrypting a private key with BIP38, users can protect their funds even if the encrypted private key is exposed. This is because an attacker would need to know the passphrase in order to decrypt the private key and gain access to the associated funds. BIP38 encryption is often used to create "paper wallets" or physical copies of Bitcoin private keys that can be stored offline for enhanced security.

How it works

1. Password-Protected Encryption (No EC-multiply): BIP38 allows users to encrypt their private keys with a user-defined passphrase. This passphrase is used as the basis for generating an encrypted private key.

2. Derivation Process (EC-multiply): BIP38 employs a key derivation function to create an intermediate code that represents the private key and can be encoded in a QR code or printed on paper. This intermediate code is protected by the passphrase.

3. Decryption: To access the private key and spend funds, users need both the encrypted intermediate code and the original passphrase. Decrypting the private key requires inputting the passphrase to regenerate the private key.

Why it's important

1. Enhanced Security: BIP38 significantly improves the security of private keys. Even if someone gains access to the encrypted private key, they cannot use it without knowing the passphrase. This adds an extra layer of protection against theft and unauthorized access.

2. Secure Cold Storage: Users can print the encrypted private key and store it offline, reducing the risk of online attacks.

3. Resilience Against Physical Threats: In cases where the encrypted key is stored on paper, it is immune to digital threats like hacking and malware. It becomes a physical asset that can be stored securely.

4. User-Friendly: BIP38 provides a user-friendly way to encrypt and protect private keys. It's especially useful for those who are not well-versed in cryptography but still want to enhance their security.

5. Recovery Option: In the event of a lost passphrase, BIP38 offers a way to recover the funds. Users can create a new encrypted private key with a new passphrase, transferring the funds to this new key.

In summary, BIP38 is a crucial standard for enhancing the security and usability of private keys in the Qtum blockchain. It empowers users to protect their assets against a wide range of threats, both digital and physical, while still allowing for recovery in case of passphrase loss.

PreviousInscribing Messages on Qtum TestnetNextQtum-Core Wallet Documentation

Last updated 1 year ago