Constellation Network
IntroductionFundamentalsFor DevelopersNode Validators
  • Index
  • Validator Node Guides
    • πŸ’°Delegated Staking
      • What is delegated staking?​
      • For Node Operators
      • Understanding Delegated Staking
      • Prerequisites
      • Create Delegated Staking Configuration
      • First Time Configuration
      • Modify Existing Configuration
      • Add/Update Delegating Staking Parameters
      • Update Delegated Staking
      • Duplicate Update
      • Status Command
    • 🚧Build Your Node
      • Create Discord Account
      • πŸ—’οΈNode Operator Notes
      • βš™οΈNode Specifications
      • 🚧Generic Build a VPS Guide
      • ☁️Cloud Provider Specific
        • 🚧Build AWS EC2 Instance
        • 🚧Build DigitalOcean Droplet
        • 🚧Build Hetzner Server
      • πŸš‰First Time Connection Guide
      • πŸ’½The nodectl utility
      • Download nodectl
      • πŸ—οΈTurn your VPS into a Node
        • 🚩Node Prerequisites
        • πŸ‡Quick Install Guide
        • 🎨Normal Install Guide
        • πŸ› οΈManual Installation
      • πŸ†Authorize to Join Hypergraph or metagaph
    • πŸ’°Collateralize Your Node
    • 1️⃣First Time Cluster Connection
    • πŸ’«Enable Auto Restart
    • πŸ“‚Operational Guides
      • ♻️Restart Validator Node Guide
      • 🐎Upgrade Tessellation Quick Start
      • 🏭Upgrade Tessellation Guide
      • πŸ—οΈReinstallation Guide
      • ♻️Backup/Restore a P12 KeyStore
      • πŸš‹Migrate V1 to V2 - P12 Keystore
  • πŸ‘‘MainNet
    • MainNet & IntegrationNet Quick Start Guide
    • 🚧Upgrade Tessellation to v3
  • πŸ₯…IntegrationNet
    • πŸ§ͺIntegrationNet Quick Start Guide
  • Metagraphs
    • πŸšͺDor metagraph
      • πŸšͺDor Validator Onboard Guide
      • πŸšͺUnderstanding Rewards
      • πŸšͺTechnical Procedures
        • πŸšͺBuild Dor Validator Node
  • πŸ“šReferences
    • πŸ“šnodectl Command Reference
    • Firewall Settings Table
    • πŸ”SSH Remote Access
      • πŸ”‘Create SSH Keys
      • πŸ“Upload SSH Public Key
      • πŸ”Securing SSH Access
      • ♻️How to SSH into VPS
    • 🍴Node Fork Types
    • πŸ—οΈP12 Keystore
    • 🏐Tarball
    • πŸ’»Virtual Private Server
  • GitHub nodectl utility
  • Run a Node Validator
  • Lattice Dashboard
Powered by GitBook

Main

  • Website
  • Get DAG
  • Explore Projects
  • Partners

Socials

  • Telegram
  • Discord
  • X (Twitter)

Tools

  • Wallet
  • DAG Explorer
  • Coingecko

Β© 2025 CONSTELLATION NETWORK

On this page
  • What Is a .p12 Keystore File?
  • πŸ” Usage in the Constellation Network
  • πŸ”’ Security Best Practices

Was this helpful?

Export as PDF
  1. References

P12 Keystore

Description of a p12 keystore.

What Is a .p12 Keystore File?

A .p12 keystore fileβ€”also known as a PKCS#12 file is a secure, encrypted container that stores multiple cryptographic keys and certificates within a single file. It is commonly used to bundle private keys, public keys, and certificates in a portable, protected format.


πŸ” Usage in the Constellation Network

Within the context of running a Validator Node on the Constellation Network, the .p12 keystore file plays several critical roles:

  • Network Authentication (Public Key) Contains a public key used to authenticate your Validator Node against the Constellation Network's seed list, allowing it to join the network cluster.

  • Transaction Signing (Private Key) Contains a private key used to sign and authorize transactions, making it your node’s hot wallet. This key can also be imported into a wallet like Stargazer to provide proof of staking, receive validator rewards and hold supported cryptocurrencies.

  • Consensus Participation (Private Key) Used to digitally sign consensus proofs, which is a core function of Validator Nodes participating in Hypergraph or metagraph consensus rounds.

  • DAG Wallet Address Derivation (Public Key) Contains the public key required to derive your wallet’s DAG address, used in transactions and rewards distribution.


πŸ”’ Security Best Practices

Because the .p12 file contains sensitive keys, it must be handled with extreme care:

  • Never share your .p12 file with untrusted individuals or systems.

  • Always protect it with a strong passphrase.

  • Maintain offline backups in secure, air-gapped locations (i.e., systems not connected to the internet).

  • Consider using hardware-based or encrypted storage for long-term archival.


Losing access to your .p12 file or having it fall into the wrong hands can result in loss of funds, node compromise, or inability to participate in network validation. Treat it as a critical asset.

PreviousNode Fork TypesNextTarball

Last updated 4 days ago

Was this helpful?

πŸ“š
πŸ—οΈ