BUG protocol.json shelley testnet

Hello, I’m trying to deregister my stake pool so I can add another delegator, but it turns out that in protocol.json the “poolRetireMaxEpoch” is 18, and the current epoch is 57 already… So there is no way to retire my stake pool… I’m always getting this error message after trying to submit the tx.signed file for the retirement process.

cardano-cli transaction submit --tx-file tx.signed --testnet-magic 1097911063
Command failed: transaction submit Error: Error while submitting tx: ShelleyTxValidationError ShelleyBasedEraMary (ApplyTxError [LedgerFailure (UtxowFailure (UtxoFailure (OutsideValidityIntervalUTxO (ValidityInterval {invalidBefore = SNothing, invalidHereafter = SJust (SlotNo 24713026)}) (SlotNo 24714884)))),LedgerFailure (UtxowFailure (UtxoFailure (BadInputsUTxO (fromList [TxInCompact (TxId {_unTxId = SafeHash “94dbaeb26efb2de465ddae8e3213e83b0dbf2f4818b4d6befba03f2e16863475”}) 0])))),LedgerFailure (UtxowFailure (UtxoFailure (ValueNotConservedUTxO (Value 0 (fromList )) (Value 2055055585 (fromList )))))])

-Do I have to use the same addr. that I used to register my pool, in my case paymentwithstake.addr? or… can I use the payment.addr which is associated with paymentwithstake.addr for retiring the pool?

-My last question is… once my pool is running on Mainet, how can i make others to put their funds into my pool without forcing them to make a delegation certificate. I guess it must be an easy way for them to put their funds into my pool…
Thank you very much.

Hi There!

on testnet the current epoch is 127 https://explorer.cardano-testnet.iohkdev.io/en
so that means that at max the pool can be retired at 127+poolRetireMaxEpoch
13. Retiring a Stake Pool — cardano-node Documentation 1.0.0 documentation

What was the transaction build command you executed?

Delegation is a built-in feature in all wallets, i.e. Daedalus, Yoroi


I just followed the official school guide, where the protocol.json I got said MaxEpoch is 18. But after doing the maths of ( SlotNo / epochlength ) gives me a larger number than the MaxEpoch from the protocol.json that I queried by submitting this command

cardano-cli query protocol-parameters
–testnet-magic 1097911063
–out-file protocol.json

This is the transaction build command that I used.

cardano-cli transaction build-raw
–tx-in 9db6cf…#0
–tx-out $(cat payment.addr)+999999096457
–ttl 860000
–fee 171309
–out-file tx.raw
–certificate-file pool.retirement

to detect the current epoch not needed the math any more. version 1.26.2 tells you went querying the tip

$ cardano-cli query tip --testnet-magic 1097911063
    "epoch": 127,
    "hash": "693f6407ff05253293e531aa3960633fb19dfa68d08d1741a920ba98c5def221",
    "slot": 27645317,
    "block": 5629274

eMax is an offset - so the max epoch number = current epoch + eMax
so the tx-in contains how much lovelace?