📓
Stake Pool Scripts by APEX Stake Pool
  • Stake pool registration
    • Directory structure
    • Wallet
    • Metadata
    • Configuration file
    • Stake pool scripts
      • Cold key
      • VRF key
      • KES key
      • Operational certificate
      • Registration certificate
      • Stake key registration
      • Stake key delegation
    • Transaction
      • Using a remote node
      • Transaction scripts
    • Retiring the stake pool
  • Hardware wallet for Pledge
    • Stake key
    • Registration certificate
    • Stake key registration
    • Stake key delegation
    • Transactions
      • Registration certificate
      • Delegation certificate
  • Running a cardano node
    • Starting a relay node
    • Starting a block producing node
Powered by GitBook
On this page
  1. Stake pool registration

Configuration file

Create the following configuration file with the name env and save it into the pool-scripts folder:

#!/bin/bash


NODE_HOME=~/stake-pool-files
CARDANO_NODE_SOCKET_PATH=/run/cardano-node.socket

KES_PERIOD=1

PLEDGE=1000000000  # 1000 ADA
COST=340000000     #  340 ADA
MARGIN=0.01        #    1 %

NET="--testnet-magic 2"  # the preview network has the magic 2
RELAY1_HOST=relay1.stakepool.url
RELAY1_PORT=port1
RELAY2_HOST=relay2.stakepool.url
RELAY2_PORT=port2
METADATA_URL=https://stakepool.url/metadata.json
METADATA_HASH=$(cat ${NODE_HOME}/metadata/poolmetadata.hash)

Edit all the values to match your data. The usual values for port are 3001 or 6000, but any valid port can be used.

It is also possible to use IP Addresses instead of hostnames, but in this case the stake pool registration certificate command will be slightly different. It is recommended to use hostnames, because if the IP Address changes, it can be changed in DNS, without being required to submit a new stake pool registration certificate with the new IP Address (as it would be required when using IP Addresses for the registered relays).

PreviousMetadataNextStake pool scripts

Last updated 1 year ago