unfortunately we realized, that our registered vrf key is wrong. I hope you don’t mind that we have to wait now for 2 epochs until our renewed registration certificate with the correct vrf key is valid and your test-ada can stay delegated to our pool at least until our first approved block.
Block Leadership looks fine, leader log gives 19 block leaderships for this period - but as I said Block Generation runs on the error with wrong registered vrf key.
Do you know how you mixed up your VRF key? I made this mistake once but I had the other set so I was able to just swap them and restart. My leader log was incorrect at that point but I still produced blocks.
we are quite familiar with linux but unfortunately we realized that the problem was bigger, because we had the wrong version of vrf at our air gapped machine.
After re-registering 3 epochs ago, I checked today the ledger state and now we have definitely the correct vrf key.
But with 1.4 mio test-ada we were chosen for 0 blocks for this epoch (ideal 2.04), so we have to wait for the next epoch until our first block. But now we are quite optimistic!
we were adopted now for our first 3 blocks and are looking forward now to lead more blocks on testnet and to set up our productive tools (coming soon).
Thanks to all supporters, who delegated additional test ada!
if you run daedalus wallet for testnet on your pc/mac you can see the rank of your node and delegate some testada.
Nodes, who are expected to generate no rewards are ranked at the bottom (all the same rank).