Looking for Shelley public testnet genesis-block-hash value

Staking & Delegation Operate a Stake Pool
1

Hi,
i’ve already a staking pool running on itn STPZ1,
now i’m looking for the jormungandr configuration values for the new shelley public testnet,
i couldn’t find them googling around.
I need something like:
https://hydra.iohk.io/build/1579767/download/1/index.html
Can some one help me.
Thanks.
Stefano.

2

The new Shelley public testnet doesn’t use Jormungandr, it uses the Haskell codebase.
The files for the new testnet can be found here under the ff cluster. There’s also a guide for setting up a pool here and a great guide by PoA pool on setting up nodes and a fancy dashboard here.

2 Likes
3

Thanks a lot for the information,
but as far as I can see cardano-node software has the producing-block instance and the relay one,
can you give me some more info on how to configure the producing-block one with my stake-ID.
Thanks.
Stefano.

4

Check here for tutorials

5

thanks a lot

6

Oh man… you made my day! Thank you so much, I couldn’t find anything on how to get the three files in the official doc.

7

hi, are you sure that is the new shelley testnet?
in cardano-node log say that is epoch 385 !

[localhos:cardano.node.ChainDB:Info:5] [2020-06-14 09:49:20.33 UTC] Opened imm db with immutable tip at (Point 416505, HashHeader {unHashHeader = 0342aacfee13fc199b580dac75840ce658b6149ed63b1b2ee7200a2a6f36445d}) and epoch 385

If the shelley-testnet just began how we already reached epoch 385?
Pleease let me know.
Thanks.
Stefano.

8

385 is definitely not right. We’re on epoch 37 currently.
Maybe you loaded configs for the wrong network?
You need to use the ones labeled ‘ff’ under ‘Cluster’ here.

9

Just for info I use the cardano-node release 1.13.0 .

I checked the config files again and I used them,
in ff-topology.json
{
“addr”: “relays-new.ff.dev.cardano.org”,
“port”: 3001,
“valency”: 2
}
and in ff-genesis.json
“networkId”: “Testnet”,
…
“networkMagic”: 42,

The host is resolved with theese IP:
nslookup relays-new.ff.dev.cardano.org
Server: 192.168.1.1
Address: 192.168.1.1#53

Non-authoritative answer:
Name: relays-new.ff.dev.cardano.org
Address: 3.22.202.206
Name: relays-new.ff.dev.cardano.org
Address: 54.177.253.76
Name: relays-new.ff.dev.cardano.org
Address: 54.176.199.50
Name: relays-new.ff.dev.cardano.org
Address: 18.139.122.21
Name: relays-new.ff.dev.cardano.org
Address: 18.229.253.139
Name: relays-new.ff.dev.cardano.org
Address: 52.76.171.181
Name: relays-new.ff.dev.cardano.org
Address: 54.233.252.241
Name: relays-new.ff.dev.cardano.org
Address: 54.94.137.119

Is there another way to enquiry the cardano-node (like jcli with jormungandr)
or the db files to see the node state ?
Maybe in the log is just a not correct write.

Thanks.

10

That all looks correct.
I’m not familiar with the logging. You could use cardano-cli to get the current slot and then divide by number of slots per epoch to find the current epoch. Not sure if there’s an easier way to do that but the command is:

cardano-cli shelley query tip --testnet-magic 42

Tip (SlotNo {unSlotNo = 820415}) (ShelleyHash {unShelleyHash = HashHeader {unHashHeader = 8a42d12dff42ccb10113640ebf35c14155728e8720481e8d209675fe23160d58}}) (BlockNo {unBlockNo = 34553})

Then divide unSlotNo by 21600 = 37th epoch