Pool registration on testnet

Hi all ,
i’m presently building my first pool on testnet , following Create Stakepool on Testnet - Love2Stake Docs and Guide: How to build a Cardano Stake Pool - CoinCashew as base and actually managed to register a pool and got to
cardano-cli query stake-snapshot --stake-pool-id $(cat …/cardano-my-node/stakepoolid.txt) --testnet-magic 1097911063
“poolStakeGo”: 0,
“activeStakeGo”: 14195111186333735,
“poolStakeMark”: 10001497223728,
“activeStakeMark”: 14393109639017331,
“poolStakeSet”: 0,
“activeStakeSet”: 14292624486035479
now the funny thing i dont explain is gLview puts me at epoch 139 , and when i look at pooltool testnet side it displays epoch 135 , obviously i’m not finding my pool , but what really puzzle me is the epoch difference , any input would be greatly appreciated

1 Like

Hi Eric, I just got my pool on testnet as well and was wondering the same thing. my Epoch just hit 140 but https://pooltool.io says 135.

I am going to press on, just not sure if this is an indication of an issue with my network.

well if we’re both at 140 , and you say you just passed at 140 just as i did , i’d say the problem is pooltool side , dunno quiet very much a newb in all that


here is the official explorer for testnet:

Tkx! running off a bunch of hacks here , some official sounds good

i’m managing to trace my trasactions for the pledge and registration , but still not being listed ,last possibility is my metadata on git or the fact i use ip-v4-relay with a dhcp address , i need to set some ddns , not giving up , wish me luck


What is the pool id?


get the info from ledger:
cardano-cli query ledger-state --testnet-magic 1097911063 > testnet-ledger-state.json
grep -A30 6d2416945f8d75813a25989bc33814f7fbd8cbbae3f54d128ce2ed32 testnet-ledger-state.json

6d2416945f8d75813a25989bc33814f7fbd8cbbae3f54d128ce2ed32": {
                        "publicKey": "6d2416945f8d75813a25989bc33814f7fbd8cbbae3f54d128ce2ed32",
                        "cost": 340000000,
                        "metadata": {
                            "hash": "646eb5fab7e3dc787850ea7dcab2c17bc7df64b3458aa9f1af71cc4ae139b5fc",
                            "url": ""
                        "owners": [
                        "vrf": "cf2d44e57d97f379ce452cccad7895a724e326817da783028d8c42b332514251",
                        "pledge": 100000000000,
                        "margin": 1.0e-2,
                        "rewardAccount": {
                            "network": "Testnet",
                            "credential": {
                                "key hash": "1ca4d53ae93d83b0c6457fb492dc530488f199cdc0e0cb9386a4ed99"
                        "relays": [
                                "single host address": {
                                    "IPv6": null,
                                    "port": 9001,
                                    "IPv4": ""

So the metadata url should a valid address

i hadn’t got has much up to now , looking at duplicating my side but ;)))))))

i just prcessed 2 blocks !! i’m seriously amazed !! , tkx for being there man

processed 2 transactions but yes, that is a good sign that the node is in sync.
next is to fix the metadata info

like all the obvious retries on the registration ?

yes, the node is ready once it is listed on pooltool.io correctly.

any specific reason why pooltool is 5 epoch late ?

i’m actually thinking of retirering this pool and redoing a clean registration with a newly generated meta and metahash

yeah good question - but, pooltool is just a convenient way to verify the registration. but if you know what the registration should look like in ledger then that is ok as well - a harder way

from left to right relay1 relay2 and block producer , i saw up to 300 TX on relays last night but 0 on block producer , but this morning got 1 , i’m also starting to see foreign inbounds on my relays

the foreign inbounds is the block producer, I guess

no , i had my block prodcer coming in as that dmz fw public address , but i also had public ip from germany and states (i’m in Canada) as incomming , when i usually see them as outbound