Payment.addr Question

Staking & Delegation Setup a Stake Pool
1

I have a producer and a relay setup, from what I can tell the next step for me in the process of setting up a stake pool is getting my keys registered.

I thought I was supposed to send money to the payment.addr address that I created so that I can use that to as ada for the transactions. However when I use my Daedalus Wallet to send the ada to the payment.addr and then run

cardano-cli query utxo --address $(cat payment.addr) --mainnet

This is my output

                       TxHash                                 TxIx        Amount

But if a check the address on the cardano explorer it shows the transaction was complete for the ada I send. Hopefully I didnt send this ada into oblivion any help on next steps would be much appreciated. Seems like all I need to do next is get my stake address registered and stake pool registered. Just want to make sure im doing this correct and I donā€™t mess something up.

Thanks!

1 Like
2

Are your nodes fully synced?

3

Yes as far as I can tell they are fully synced.

cardano-cli query tip --mainnet
Warning: Sync progress unavailable: System start unavailable
{
ā€œepochā€: 277,
ā€œhashā€: ā€œb6190616c74a67b387577f8f9ed165d0df28bc5bdadbdf96dd8a7c05048e9d8dā€,
ā€œslotā€: 34332038,
ā€œblockā€: 5960367,
ā€œeraā€: ā€œMaryā€
}

4

Make sure your passive node is running,
$ cardano-node run
ā€“topology /path/to/mainnet-topology.json
ā€“database-path /path/to/db
ā€“socket-path /path/to/db/node.socket
ā€“host-addr x.x.x.x
ā€“port 3001
ā€“config /path/to/mainnet-config.json

It will take about 24 hours for your passive node to be in sync to the current block height. And if you had created the payment.addr recently(which is more than likely), you need to wait till it completely syncs up.

When you run,
$ cardano-cli query tip --mainnet
you are not supposed to see this error ā€˜Warning: Sync progress unavailable: System start unavailableā€™

5

Okay this helps so it looks like I may have jumped the gun on my config and got it ready for block producing to soon.

I was using this.

cardano-node run \
        --topology block-producing/mainnet-topology.json \
        --database-path block-producing/db \
        --socket-path block-producing/db/node.socket \
        --host-addr x.x.x.x \
        --port 3001 \
        --config block-producing/mainnet-config.json \
        --shelley-kes-key pool-keys/kes.skey \
        --shelley-vrf-key pool-keys/vrf.skey \
        --shelley-operational-certificate pool-keys/node.cert

Here is what I get when I remove those 3 lines then run the command on my producer and relay

CARDANO-PRODUCER:~/cardano/node# cardano-cli query tip --mainnet
Warning: Sync progress unavailable: System start unavailable
{
    "epoch": 278,
    "hash": "719c6bb407fe5242874995457a647f037a62f51e2e4e5ac9cd2bd02975300354",
    "slot": 34738554,
    "block": 5980472,
    "era": "Mary"
}

CARDANO-RELAY1:~/cardano/node# cardano-cli query tip --mainnet
Warning: Sync progress unavailable: System start unavailable
{
    "epoch": 278,
    "hash": "8d3a694a1b6e3de47da8dc4762359981f1ea21316a6e5a954cb06d3d726f5d6a",
    "slot": 34738662,
    "block": 5980481,
    "era": "Mary"
}

Seems like I need to take out the last 3 lines and try again?

6

I hope you were able to see your payment. Clarification on your question,

Relay node

  • must not have kes.skey, vrf.skey, node.cert

Block Producer

  • should have kes.skey, vrf.skey, node.cert

As long as you see these messages on block producer and relay node, you are ok,

Chain extended, new tipā€¦

Block node should play catch up to relay node. You would know they are in sync when slot matches each other. Seems like you are pretty close.

Iā€™m also seeing ā€œWarning: Sync progress unavailable: System start unavailableā€ on my nodes. Maybe another expert could chime in if thatā€™s ok. ------UPDATE: This is because i upgraded to 1.28 which is still not available on --mainnet. Switched back to 1.27 and itā€™s all good.