subkey generate
Secret phrase: twist buffalo mixture excess device drastic vague mammal fitness punch match hammer
Network ID: substrate
Secret seed: 0x5faa9e5defe42b201388d5c2b8202d6625a344abc9aa52943a71f12cb90b88a9
Public key (hex): 0x28cc2fdb6e28835e2bbac9a16feb65c23d448c9314ef12fe083b61bab8fc2755
Account ID: 0x28cc2fdb6e28835e2bbac9a16feb65c23d448c9314ef12fe083b61bab8fc2755
Public key (SS58): 5CzCRpXzHYhuo6G3gYFR3cgV6X3qCNwVt51m8q14ZcChsSXQ
SS58 Address: 5CzCRpXzHYhuo6G3gYFR3cgV6X3qCNwVt51m8q14ZcChsSXQ
To properly store these keys, create a file in your keystore directory with a specific naming convention. The filename must consist of the hex string `61757261` (which represents "aura" in hex) followed by the public key without its `0x` prefix.
Using the example above, you would create a file named:
```
./keystores/6175726128cc2fdb6e28835e2bbac9a16feb65c23d448c9314ef12fe083b61bab8fc2755
```
And store only the secret phrase in the file:
```
"twist buffalo mixture excess device drastic vague mammal fitness punch match hammer"
```
When submitting `setKeys`, use `0x00` as the proof parameter.
!!! warning "Save your session key output immediately"
You must save these session keys as you'll need them for on-chain registration.
Calling `author_rotateKeys` or `author_rotateKeysWithOwner` generates **new keys every time** — it does not return previously generated keys. If you lose the output, there is no way to retrieve it. You will need to call the RPC again, which generates a fresh set of keys, and then re-submit `setKeys` with the new result.
## Register Collator for Selection
System parachains use different mechanisms for selecting collators. A quick breakdown of each mechanism is as follows:
| Method | How it Works | Requirements |
|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------|
| **Invulnerables list** | Fixed list defined through governance. Most common for system parachains. | Permissioned via governance |
| **On-chain selection** | Runtime automatically selects eligible collators. Some parachains use [pallet-collator-selection](https://paritytech.github.io/polkadot-sdk/master/pallet_collator_selection/index.html). | Semi-permissionless (criteria-based; may require bonding tokens) |
| **Fellowship decisions** | Technical fellowship may manage some system parachain collators. | Permissioned via Fellowship |
### Registration Process
Collator registration authorizes your node to produce blocks on the network. The parachain's collator selection mechanism uses this on-chain registration to determine which nodes are eligible to author blocks.
The registration process varies by system parachain. General steps include the following:
1. Check the existing collators for your target parachain:
1. Navigate to Polkadot.js Apps and connect to your system parachain.
2. Locate **Developer > Chain State**.
3. Query **`collatorSelection.invulnerables()`**.
2. Prepare a governance proposal for invulnerables-based selection, including the following information:
- **Draft proposal**: Explain why you should be added as a collator.
- **Technical details**: Provide your session keys and account ID.
- **Infrastructure**: Describe your hardware and monitoring setup.
- **Experience**: Detail your relevant experience.
Submit the proposal to the relevant governance channels.
3. Once approved (or if using on-chain selection), follow these steps to register session keys using Polkadot.js Apps:
1. Locate **Developer > Extrinsics**.
2. Select your account.
3. Choose the **`session.setKeys`** extrinsic.
4. Enter the values returned by [Generate Session Keys](#generate-session-keys):
- **`keys`**
- **`proof`**
5. Click **Submit Transaction** and sign the transaction.
!!! note
The first `session.setKeys` call holds a deposit equal to `session.keyDeposit`. The call fails if your free balance is below the ED plus this deposit. Rotating keys that are already registered is not charged again. Calling `session.purgeKeys` releases the deposit. Keys registered before the deposit was introduced stay deposit-free.
Query the current deposit in Polkadot.js Apps under **Developer > Chain State > Constants > `session.keyDeposit`**, since runtime upgrades can change it. If the constant is zero or isn't listed, no deposit applies.
4. (Optional - primarily for non-system parachains) If the parachain uses on-chain bonding for collator selection, register as a candidate using Polkadot.js Apps:
!!! note
Most system parachains use invulnerables lists exclusively and do not require this step. Skip to step 5 if you're running a collator for a system parachain.
1. Locate **Developer > Extrinsics**.
2. Select your account.
3. Select `collatorSelection.registerAsCandidate`.
4. Click **Submit Transaction** and sign the transaction. The required bond amount will be automatically reserved from your account based on the pallet's configured `CandidacyBond`.
5. For system parachains using invulnerables lists, await governance approval for your proposal. Once approved, your collator is added to the invulnerables list and will begin producing blocks in the next session or era.
6. Verify your collator is active by monitoring logs for block production messages like "Prepared block for proposing" and "Imported #123". See the [Log Management](#commands-for-log-management) section for commands for log viewing.
## Commands for Node Management
Use the following commands to manage your node:
=== "Docker"
- **Stop container**:
```bash
docker stop polkadot-collator
```
- **Start container**:
```bash
docker start polkadot-collator
```
- **Remove container**:
```bash
docker rm polkadot-collator
```
=== "systemd"
- **Check status**:
```bash
sudo systemctl status polkadot-collator
```
- **Stop service**:
```bash
sudo systemctl stop polkadot-collator
```
- **Enable service**:
```bash
sudo systemctl enable polkadot-collator
```
- **Start service**:
```bash
sudo systemctl start polkadot-collator
```
## Commands for Log Management
Efficient log management is essential to ensure collator performance and uptime. Use the following commands to help you manage logs to monitor and maintain your collator:
=== "Docker"
- **View logs**:
```bash
docker logs -f polkadot-collator
```
- **View recent logs (last 100 lines)**:
```bash
docker logs --tail 100 polkadot-collator
```
- **Filter for errors**:
```bash
docker logs polkadot-collator 2>&1 | grep -i error
```
- **Filter for block production**:
```bash
docker logs polkadot-collator 2>&1 | grep -i "imported"
```
=== "systemd"
- **View recent logs**:
```bash
sudo journalctl -u polkadot-collator -n 100
```
- **Follow logs in real-time**:
```bash
sudo journalctl -u polkadot-collator -f
```
- **Filter for errors**:
```bash
sudo journalctl -u polkadot-collator | grep -i error
```
- **Filter for block production**:
```bash
sudo journalctl -u polkadot-collator | grep -i "imported"
```
## Database Maintenance
Check database size periodically using the commands for your selected setup:
=== "Docker"
```bash
# Replace with your mounted data directory path
du -sh ./collator-data
```
=== "systemd"
```bash
du -sh /var/lib/polkadot-collator
```
The collator node automatically prunes based on configuration.
## Updates and Upgrades
Updates or upgrades can happen on either the runtime or client. Runtime upgrades are automatically applied via on-chain governance and do not require any manual action on your part. Client upgrades do require a manual binary update process performed via terminal commands as follows:
=== "Docker"
1. Stop the service:
```bash
sudo systemctl stop polkadot-collator
```
2. Backup data (recommended):
```bash
sudo cp -r /var/lib/polkadot-collator /var/lib/polkadot-collator.backup
```
3. Pull the new Docker image:
```bash
docker pull parity/polkadot-parachain: