Registered pool but not shown in Daedalus

Staking & Delegation Pool Introductions
1

Hi everybody, thank you in advance for every help you can give me!

I have 1 relay on the same machine as the block producer, both working fine, gLiveView shows everything is in sync.

I followed the coincashew guide for setting up a pool. I’m registered and on the pool tool.io site, my id is shown on the list:
Pool id: 3a33e0dc0c8e154b4203285da69a2adf2d5586d74c992d7b441f697b.

Something is not right though. My ticker name is not correct (should be ROT), and i’m not listed on Daedalus Wallet. I followed other guides because it could be the metadata hash changed, not registered correctly, but when i tried to do the process from the start, it keeps asking me for 500 ada (which i’ve already paid). If i try to build only the transaction (since i’ve already all the .certs) it tells me i’m already registered (StakeKeyAlreadyRegisteredDELEG).

I’ve registered the pool with the 1.25 version of the node, could be that i’m not updated?

I don’t know what else i can do, any help is really appreciated.

Have a nice day

2

Hi!

Could you please change the category of this topic from English|Community Techincal Support to staking-delegation|setup-a-stake-pool?

1 Like
3

There is an online tool which checks your pool setup
https://pool.vet/#3a33e0dc0c8e154b4203285da69a2adf2d5586d74c992d7b441f697b
Error reading [metadata](https://git.io/JYoYG): Unexpected token < in JSON at position 6

which transaction you are building?

1 Like
4

In your registration, you want to have this URL (i.e. the raw content)

https://raw.githubusercontent.com/alesIpa/rotapoolCardano/main/poolMetaData.json

1 Like
5

cardano-cli stake-pool registration-certificate
–cold-verification-key-file node.vkey
–vrf-verification-key-file vrf.vkey
–pool-pledge 200000000
–pool-cost 340000000
–pool-margin 0.015
–pool-reward-account-verification-key-file stake.vkey
–pool-owner-stake-verification-key-file stake.vkey
–mainnet
–pool-relay-port 6000
–pool-relay-ipv4 192.168.1.175
–metadata-url https://git.io/JYS1e
–metadata-hash $(cat poolMetaDataHash.txt)
–out-file pool.cert

6

Following the guide (coincashew) I put the shrinked url in the registration…do you mean in the homepage JSON field?

7

It seems that you have https://git.io/JYoYG in your certificate and not https://git.io/JYS1e

8

there is a subcategory under Staking & Delegation - called Setup a Stake Pool - instead of using tags - could try to modify the category again?

9

Also, I don’t think that 192.168.1.175 is a public IP. Instead, it might be the internal IP on your home network.

10

I cannot find that subcategory. I see only stake delegation, and pool introductions (other than the Staking&Delegation main). Sorry

11

Yes that’s internal but it should work since i do port forwarding…I’m trying to make another registration…fixing the metadata json.

12

ok - maybe you can not create posts yet there… no worries…
So in the ledger this is the registered informations about your pool:

"3a33e0dc0c8e154b4203285da69a2adf2d5586d74c992d7b441f697b": {
                            "owners": [
                                "cc06e3efa83027975ab11f585d642b5c571dbcf6d488b724f160f6f7"
                            ],
                            "cost": 340000000,
                            "margin": 1.5e-2,
                            "publicKey": "3a33e0dc0c8e154b4203285da69a2adf2d5586d74c992d7b441f697b",
                            "pledge": 200000000,
                            "vrf": "f809b8a8d87cc5497f90aa6e9f8bcaf8128eac4bd6cbcb20123726b038a5ce60",
                            "metadata": {
                                "hash": "1208ef629fd45c2c8dfe59129b0f42c1abb8a66a181f0b67c60a20348b7aa17a",
                                "url": "https://git.io/JYoYG"
                            },
                            "relays": [
                                {
                                    "single host address": {
                                        "IPv6": null,
                                        "IPv4": "192.168.1.175",
                                        "port": 6000
                                    }
                                }
                            ],

So now the question is why you can not re-register your pool… how are you signing the transactions?

13

I think i’ve overlapped the registration with different tx.signed.

The registered info are correct but now i’m updating the metadata. I’m trying to build another transaction to update those info.

cardano-cli transaction build-raw
{tx_in} \ --tx-out (cat payment.addr)+(( {total_balance} - {poolDeposit})) \ --invalid-hereafter (( ${currentSlot} + 10000))
–fee 0
–certificate-file pool.cert
–certificate-file deleg.cert
–mary-era
–out-file tx.tmp

I don’t know how i should set the amount to update without paying another registration. I’ve read it is just a fee of 1 ADA more or less. Am I doing the right procedure?

14

are you following the re-registration guide?
https://www.coincashew.com/coins/overview-ada/guide-how-to-build-a-haskell-stakepool-node#18-4-changing-the-pledge-fee-margin-etc

15

yes, but without deleting the db folder. I’m doing it right now, let see how it goes :slight_smile: Thank you for your time

16

Signed tx submitted without problem. The pool.vet now is ok regarding the metadata. There are some warning about the topology…

Relay node 192.168.1.175:6000

Can’t reach relay node 192.168.1.175:6000

Check manually that the topology for relay node 192.168.1.175:6000 is configured

Relay node 192.168.1.175:6000 is missing in [topology.json]

This is my BlockProducer:

{
“Producers”: [
{
“addr”: “192.168.1.175”,
“port”: 6000,
“valency”: 1
}
]
}

And here’s the relay:

{
“Producers”: [
{
“addr”:“0.0.0.0”,
“port”:6001,
“valency”:1
},
{
“addr”: “relays-new.cardano-mainnet.iohk.io”,
“port”: 3001,
“valency”: 2
}
]
}

17

You cannot use local IP addresses for the relays. Local IPs (i.e. 192.168.xxx.yyy) are not public and cannot reached from the outside world. You need public IPs or your realys will never be seen from the outside.

Also, you pledge is not fuflilled, you need to deposit more ADA in the pool address.

1 Like
18

Thank you very much guys!

19

Pledge fulfilled. The pool is online on pool tool but not on daedalus wallet yet. I’m putting a public ip on the relay topology file and restart it, and see how it goes. Thanks again

20

Still could not find the issue about the public IP…i use topologyUpdater with this env:

CNODE_PORT=6000 # must match your relay node port as set in the startup command
CNODE_HOSTNAME=“192.168.1.175” # optional. must resolve to the IP you are requesting from
CNODE_BIN="/usr/local/bin"
CNODE_HOME=/home/cardano-my-node
CNODE_LOG_DIR="${CNODE_HOME}/logs"

Maybe i need to wait?