- Get Started
- Stellar Attachment Convention
- Compliance Protocol
- Add Stellar To Your Exchange
- Hardware Requirements
- Issuing Assets
- Known Validators
- Build Stellar Apps
- Contribution Guide
Stellar has two public networks: the Public Network (pubnet), which is the main network used by applications in production, and the Test Network (testnet), which is a network maintained by the Stellar Development Foundation that developers can use to test their applications.
Each Stellar network has its own unique passphrase, which is used when validating signatures on a
given transaction. If you sign a transaction for one network but submit it to another, it won’t be
considered valid. By convention, the format of a passphrase is
'[Network Name] ; [Month of Creation] [Year of Creation]'.
The current passphrases for the Stellar pubnet and testnet are:
'Public Global Stellar Network ; September 2015'
'Test SDF Network ; September 2015'
The passphrase serves two main purposes:
Most SDKs have the passphrases hardcoded for the Stellar pubnet and testnet, but if you’re running a private network, you’ll need to manually pass in a passphrase to be used whenever transaction hashes are generated. All of Stellar’s official SDKs give you the ability to use a network with a custom passphrase.
When creating your application on top of the Stellar network, we recommend starting on the testnet, and migrate to pubnet after rigorous testing has proved it to be production ready (we are talking about money here).
For applications that don’t rely on the state of a network (such as specific accounts needing to exist), moving to production is as simple as changing the network passphrase and ensuring your Horizon instance is connected to pubnet.
If you’ve been running a stellar-core or Horizon instance against the test network, and want to switch to production, changing the passphrase will require both respective databases to be completely reinitialized. You certainly wouldn’t want transactions from another network to end up in your ledger!