Stake Pool node not showing up in ledger after registration

Somehow it now shows up without any change! (i did not check before my previous message)
Still don’t know what the accurate syntax is to check registration using cardano-cli

FWIW, I think you should be able to locate your pool in the ledger as follows:

cardano-cli shelley query ledger-state --mainnet | grep <metadata_hash>

I was not able to locate my testnet pool using the method from the docs either.

Doesn’t work either…

Instead I found the correct Pool ID on Adapools. Using this ID i now get multiple results from the cli:
cardano-cli shelley query ledger-state --mainnet | grep 4308d4056a9af42c5d8bd2498a5e2ea215598c6ea5570b6dfbb63570
“4308d4056a9af42c5d8bd2498a5e2ea215598c6ea5570b6dfbb63570”: {
“publicKey”: “4308d4056a9af42c5d8bd2498a5e2ea215598c6ea5570b6dfbb63570”,
“4308d4056a9af42c5d8bd2498a5e2ea215598c6ea5570b6dfbb63570”
“4308d4056a9af42c5d8bd2498a5e2ea215598c6ea5570b6dfbb63570”
“4308d4056a9af42c5d8bd2498a5e2ea215598c6ea5570b6dfbb63570”: {
“publicKey”: “4308d4056a9af42c5d8bd2498a5e2ea215598c6ea5570b6dfbb63570”,
“4308d4056a9af42c5d8bd2498a5e2ea215598c6ea5570b6dfbb63570”: {
“publicKey”: “4308d4056a9af42c5d8bd2498a5e2ea215598c6ea5570b6dfbb63570”,

Is multiple results as expected?
Although my pool now shows up on adapools.org it still doesn’t (correctly) show up on Pooltool and Daeadlus. On pooltooi.io I can find it using the pool ID but the Ticker is not showing.
Very strange. Could it be of multiple registrations?

Doesn’t work either…

Instead I found the correct Pool ID on Adapools. Using this ID i now get multiple results from the cli:
cardano-cli shelley query ledger-state --mainnet | grep 4308d4056a9af42c5d8bd2498a5e2ea215598c6ea5570b6dfbb63570
“4308d4056a9af42c5d8bd2498a5e2ea215598c6ea5570b6dfbb63570”: {
“publicKey”: “4308d4056a9af42c5d8bd2498a5e2ea215598c6ea5570b6dfbb63570”,
“4308d4056a9af42c5d8bd2498a5e2ea215598c6ea5570b6dfbb63570”
“4308d4056a9af42c5d8bd2498a5e2ea215598c6ea5570b6dfbb63570”
“4308d4056a9af42c5d8bd2498a5e2ea215598c6ea5570b6dfbb63570”: {
“publicKey”: “4308d4056a9af42c5d8bd2498a5e2ea215598c6ea5570b6dfbb63570”,
“4308d4056a9af42c5d8bd2498a5e2ea215598c6ea5570b6dfbb63570”: {
“publicKey”: “4308d4056a9af42c5d8bd2498a5e2ea215598c6ea5570b6dfbb63570”,

Is multiple results as expected?
Although my pool now shows up on Adapools it still doesn’t (correctly) show up on Pooltool and Daeadlus. On pooltooi.io I can find it using the pool ID but the Ticker is not showing.
Very stange. Could it be of multiple registrations?

I came across this same thing. I discovered that cardano-cli shelley stake-pool id has a flag --output-format which can either be "hex" or "bech32". By default it’s bech32 which starts with pool.... As far as I can see, using the hex version is the most common approach. So try the following:

cardano-cli shelley stake-pool id \
--verification-key-file /path/to/cold.vkey \
--output-format hex
4 Likes

Yeah I think this is new to 1.19.0

1 Like

Yes, this solves this issue with the pool ID. Thx!

I’m having the same problem with my pool now. I registered the pool today some time ago.
Pool ticker and website details are not showing up in pooltool.io and adapool.org.

How did you solve this problem?

I appreciate your help with this.

Pool ID: a1b6398200511816277ec4ac4a94160b6cb0fbf6a8bc002c506e41ad

I had some issues with the pool metadata file. I fixed and submitted the transaction again with an updated pool hash. Adapools.org is picked up the update immediately and showing up all the ticker and website details. My Ticker STASH is not showing up in Daedalus wallet and pooltool

Any help in this regard is much appreciated.

I think you solved the issue meanwhile? (I see your ticker in adapools)

It is only showing on Adapools.org, but not on the Daedalus wallet after I re-submitted the transaction. Not sure why Daedalus and pooltool have not picked up the updated details.

Mine starts with pool…, but that’s on the testnet version.

lungaretta is right. I recall reading somewhere that stakepools need
–output-format hex flag now, starting with 1.19.0

I see it in Daedalus

1 Like

Thanks for checking. I updated the JSON file metadata hash, increased the pledge (Maybe not required, but I did update to make sure Daedalus picks up my change), and re-registered the pool. It works like a charm after that.