Download Wallet

Security Center

Protect wallets, keys, server access, and Service Node identity.

Service Node operation is not only about staking and starting a server. Operators also need to protect wallet recovery information, private keys, access files, node records, and backup materials so that funds, infrastructure, and node identity remain recoverable and safe.

Seed phraseoffline backup
Private keysnever share
Server accessprotect .pem files
Backupsseparate safe locations

Critical Security Materials

Protect the materials that can recover wallets, identify Service Nodes, or access servers.

01

Wallet seed phrase backup

The wallet seed phrase is one of the most important recovery tools.

  • Do not share the seed phrase with anyone
  • Do not send the seed phrase through chat apps or email
  • Do not store the seed phrase in plain text on an online computer
  • Do not take screenshots of the seed phrase
  • Do not upload the seed phrase to cloud storage
  • Do not paste the seed phrase into unknown websites or tools
  • Keep at least one offline backup in a safe location

If the wallet seed phrase is lost, the wallet may not be recoverable. If the wallet seed phrase is leaked, the wallet funds may be at risk.

02

Wallet password backup

The wallet password is also important.

  • Use a strong password
  • Do not use simple passwords
  • Do not store the wallet password together with the seed phrase
  • Do not send the wallet password to anyone
  • Keep a secure offline backup if necessary

A good practice is to store the wallet seed phrase and wallet password separately.

03

Service Node private key backup

The Service Node private key is used to identify the Service Node. The key file is usually located at /home/ubuntu/.bitjudecoin/key_ed25519.

  • Do not share the Service Node private key
  • Do not send it through chat apps or email
  • Do not post it in public groups
  • Do not upload it to public cloud storage
  • Keep at least two offline backups
  • Store backups in separate safe locations

If the server is lost, damaged, reinstalled, or migrated, the Service Node private key may be needed to restore the original Service Node identity.

04

.pem server access file backup

A .pem file is used to access the server. If the .pem file is lost, normal SSH access to the server may be lost.

  • Do not share the .pem file with anyone
  • Do not upload it to public storage
  • Do not store it only on one computer
  • Keep an encrypted offline backup
  • Use clear file names to avoid confusion
  • Store different server keys carefully if managing multiple nodes

The .pem file should be treated as a sensitive access file.

Backup and Recovery Structure

Use separated backups and private records so wallet and Service Node recovery does not depend on a single device.

05

Server information backup

A Service Node operator should keep a basic private record of server information.

  • Server region
  • Server provider
  • Instance name
  • Public IP address
  • CLI version
  • Service Node public key
  • Wallet used for registration
  • Registration date
  • Current node status
  • Notes about upgrades or restarts

Do not publish this full record publicly. It is useful for private management and recovery.

07

Hardware encrypted USB drive

A hardware encrypted USB drive can be useful for storing sensitive files.

  • Service Node private key backup
  • .pem file backup
  • Node record file
  • Wallet recovery notes
  • Important operation documents
  • Use at least two encrypted USB drives
  • Keep them in different safe locations
  • Do not keep both backups in the same bag or same computer
  • Test the USB drive before relying on it
  • Keep the password safe and separate from the USB drive

Encrypted backups are only useful if the backup device and password are both protected.

Never Share These Materials

Recovery materials, private keys, access files, and sensitive screenshots should not be sent through public or private channels.

08

What should never be shared

Never share sensitive wallet, server, or Service Node access information.

  • Wallet seed phrase
  • Wallet private key
  • Wallet password
  • View key
  • Spend key
  • Wallet files
  • Service Node private key
  • .pem file
  • Server login credentials
  • Verification codes
  • Backend screenshots containing sensitive information

If anyone asks for these, treat it as a serious security risk.

Communication and Community Safety

Reduce avoidable exposure in public channels, emails, screenshots, and contribution workflows.

09

Email and phishing safety

Be careful with emails or messages claiming to represent the project, community, or technical team.

  • Check whether the sender is using a trusted domain
  • Check whether the message is asking for private keys or seed phrases
  • Check whether there is a suspicious link
  • Check whether the message is trying to create urgency
  • Confirm the identity through trusted project channels before responding

Never provide private keys, seed phrases, wallet files, or server access files through email.

10

GitHub and community safety

When contributing to GitHub Discussions or documentation, avoid exposing private operational information.

  • Do not post wallet seed phrases
  • Do not post Service Node private keys
  • Do not post .pem files
  • Do not post server login information
  • Do not post full backend screenshots
  • Remove personal information from screenshots before sharing
  • Avoid exposing large holdings or node ownership details publicly

Community contribution should be helpful, but it should not expose private operational information.

Migration and Recovery Readiness

Confirm recovery materials before changing servers, moving funds, or restoring a Service Node identity.

11

Before server migration or recovery

Before migrating or restoring a node, confirm that the required access and identity materials are available.

  • Service Node private key backup
  • .pem file or new server access
  • CLI version information
  • Service Node public key
  • Node records
  • Wallet access
  • Safe working environment

Do not start recovery work if you are unsure whether the Service Node private key is correct.

Basic Backup Checklist

Use this final checklist before running or maintaining a Service Node.

12

Basic backup checklist

Before running or maintaining a Service Node, make sure the essential recovery materials are backed up.

  • Wallet seed phrase
  • Wallet password
  • Wallet files if needed
  • Service Node private key
  • .pem file
  • Server region and instance notes
  • Service Node public key
  • CLI version information
  • Node operation notes
  • One main encrypted backup
  • One offline encrypted backup
  • One separate paper backup for critical recovery information

Service Node security is as important as Service Node operation.

Conclusion

A node operator should not only know how to start, restart, or restore a node, but also know how to protect the keys and files behind the node. Safer backup habits reduce avoidable risks and help protect the long-term operation of the Service Node.