Congratulations!!
How many time had it costed?
I’m waiting for that 
Thank you! BEEHI pool been on mainnet for 16 days and hoping to stay on for at least 16 centuries
2 Likes
ehh… you know… the protocol will return 5-6% per year… I think u already achieved this target :)) (kidding)
1 Like
aaaaaaaaaaand that’s it haha
How come Daedalus and cntools show no rewards yet?
The rewards will be paid next epoch
Thanks Alex,
yeah, I did a refresh on stake pool school on that topic
Hi Guys
I’m having the same issue with my pool.
Got it updated to 1.27.1, got the KES updated, ran topololoyUpdater.sh but still no Processed TX.
Can I get you to take a look Alex?
Ticker is CBOX
Do u have IN peers on relay?
I see no errors on pool.vet
Perhaps u have set TraceMempool=false inside configuration file?
I’m out now.
I’ll have a look in an hour or two.
I must be close to minting that first block now.
I got just under 100k pledge and staked.
Roughly how many blocks a day/week should I expect to be minting when it’s all working properly.
I know there is luck involved, but a rough idea would be good
Ok, I’m back and relay #1 has processed 6000 TX in a few hours, great.
I must’ve messed up the KES on Relay #2 but I’ve fixed that now, it should be at full steam in a short while when I can run TopologyUpdate.sh
I’m chuffed to bits
Hi Alex,
I don’t know what Ive done but its messedup again.
On the BP and Relay boxes, they all seem to be working fine but pool.vet shows errors with topology file but I cant see why.
Could you help me out again?
Ticker is CBOX
Error mentions that your relays seem unreachable. Did you change your topology file somehow or downloaded a fresh one that need editing?
To confirm I got this right.
CORE box mainnet-topology.json only contains address’s and port of my RELAYS
there is no topology.json on CORE box.
RELAY box’s mainnet-topology.json only contain address and port of my CORE
RELAY topology.json contains adress’s of my RELAYS, NOT CORE BP
topologyUpdaer.sh on RELAY boxes contains the line
CUSTOM_PEERS=“cbox-relay-1-1.uksouth.cloudapp.azure.com,3001|cbox-relay-2-1.uksouth.cloudapp.azure.com,3001”
Both there port are open as is the Core BP port on 6000
Cant understand why pool.vet says this
Relay node http://cbox-relay-1-1.uksouth.cloudapp.azure.com:3001
Can’t reach relay node http://cbox-relay-1-1.uksouth.cloudapp.azure.com:3001
Check manually that the topology for relay node http://cbox-relay-1-1.uksouth.cloudapp.azure.com:3001 is configured
Relay node http://cbox-relay-1-1.uksouth.cloudapp.azure.com:3001 is missing in topology.json
Relay node http://cbox-relay-2-1.uksouth.cloudapp.azure.com:3001
Can’t reach relay node http://cbox-relay-2-1.uksouth.cloudapp.azure.com:3001
Check manually that the topology for relay node http://cbox-relay-2-1.uksouth.cloudapp.azure.com:3001 is configured
Relay node http://cbox-relay-2-1.uksouth.cloudapp.azure.com:3001 is missing in topology.json
yes, I got some wierd EOF error when I edited the files.
I had to download and use nano instead of sublinetxt which seemed to do the weird EOF issue
Why do you have 2 seperate topology files on your relay nodes?
I have to admit, I wondered why myself.
When I stat the node, I use this command on RELAY
.cardano-node run --topology /opt/cardano/cnode/files/mainnet-topology.json --database-path /opt/cardano/cnode/db --socket-path /opt/cardano/cnode/sockets/node0.socket --host-addr 0.0.0.0 --port 3001 --config /opt/cardano/cnode/files/mainnet-config.json
On CORE its the same with
–shelley-kes-key=/opt/cardano/cnode/priv/pool/CardanoBox/kes.skey --shelley-vrf-key=/opt/cardano/cnode/priv/pool/CardanoBox/vrf.skey --shelley-operational-certificate=/opt/cardano/cnode/priv/pool/CardanoBox/node.cert
I take it I don’t need all the json files.
Which ones do I need?
Do I still reference shelley files?
Its very unclear and different urls’ say differentt things
Another weird thing that may be connected is this.
Running cntools.sh on CORE node
Polls->LIST shows this
CardanoBox
ID (hex) : 4c8dc69f54bb2088f2155d26d66a579621XXXXXXXXXXXXXX
ID (bech32) : pool1fjxud865hvsg3us4t5ndv6jhjcssXXXXXXXXXXXXXX
Registered : NO
KES expiration date : 2021-10-09 21:44:51 UTC
But Pools->SHOW says this
Pool Name : CardanoBox
ID (hex) : 4c8dc69f54bb2088f2155d26d66a57962109CXXXXXXX
ID (bech32) : pool1fjxud865hvsg3us4t5ndv6jhjcssj5rg2eq78XXXXXX
Registered : YES
Metadata etc, etc
When you run the node you reference the mainnet-topology.json so that’s the json file that will provide the address information