Skip to content

Commit

Permalink
Remove Legacy key from Creating keys and addresses (#521)
Browse files Browse the repository at this point in the history
* Remove Legacy key from Creating keys and addresses

Remove Legacy key from Creating keys and addresses page

* Removed Legacy key from Create Stake Pool Keys

Removed Legacy key from Create Stake Pool Keys page

* Removed hex line

Removed hex line

* Removed hex line

Removed hex line
  • Loading branch information
os11k authored Feb 15, 2022
1 parent 1ad9eec commit de4729b
Show file tree
Hide file tree
Showing 2 changed files with 0 additions and 32 deletions.
16 changes: 0 additions & 16 deletions docs/stake-pool-course/handbook/create-stake-pool-keys.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,22 +23,6 @@ cardano-cli address key-gen \

This creates two files `payment.vkey` (the _public verification key_) and `payment.skey` (the _private signing key_).

## Legacy key

To generate Byron-era _payment key_:

Payment key files use the following format:

```json
{
"type": "PaymentSigningKeyByron_ed25519_bip32",
"description": "Payment Signing Key",
"cborHex": "hex-here"
}
```

Where the `hex-here` is generated as `0x5880 | xprv | pub | chaincode`

## Stake key pair
To generate a _stake key pair_ :

Expand Down
16 changes: 0 additions & 16 deletions docs/stake-pool-course/handbook/keys-addresses.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,22 +26,6 @@ cardano-cli address key-gen \
```
This creates two files `payment.vkey` (the _public verification key_) and `payment.skey` (the _private signing key_).

## Legacy key

To generate Byron-era _payment key_:

Payment key files use the following format:

```json
{
"type": "PaymentSigningKeyByron_ed25519_bip32",
"description": "Payment Signing Key",
"cborHex": "hex-here"
}
```

Where the `hex-here` is generated as `0x5880 | xprv | pub | chaincode`

## Stake key pair
To generate a _stake key pair_ :

Expand Down

0 comments on commit de4729b

Please sign in to comment.