Decipher Transaction submit error 1.27.0 - OutsideValidityIntervalUTxO

Staking & Delegation Setup a Stake Pool
1 
cardano-cli transaction submit --tx-file tx.signed --testnet-magic 1097911063

This command is returning the following error:
Command failed: transaction submit Error: Error while submitting tx: ShelleyTxValidationError ShelleyBasedEraMary (ApplyTxError [UtxowFailure (UtxoFailure (OutsideValidityIntervalUTxO (ValidityInterval {invalidBefore = SNothing, invalidHereafter = SJust (SlotNo 900)}) (SlotNo 28183487)))])

Not sure what this error is trying to tell me. Any ideas?

2

Hi!

Is your node fully synced?

have you add --invalidHereafter flag to the transaction?

3

Hi, laplasz

db is sync’ed. Not seeing a --invalidHereafter option to the transaction submit syntax.

4

Hi!

this flag is available for

cardano-cli transaction build-raw
Usage: cardano-cli transaction build-raw [--byron-era | --shelley-era | 
                                           --allegra-era | --mary-era]
                                         (--tx-in TX-IN) [--tx-out TX-OUT] 
                                         [--mint VALUE] [--invalid-before SLOT] 
                                         [--invalid-hereafter SLOT] 
                                         [--fee LOVELACE] 
                                         [--certificate-file FILE] 
                                         [--withdrawal WITHDRAWAL] 
                                         [--json-metadata-no-schema | 
                                           --json-metadata-detailed-schema] 
                                         [--script-file FILE] 
                                         [--metadata-json-file FILE | 
                                           --metadata-cbor-file FILE] 
                                         [--update-proposal-file FILE] 
                                         --out-file FILE
  Build a transaction (low-level, inconvenient)
5

–invalid-hereafter should more then (SlotNo 28183487

6

Thanks. I’ll give that a try.

7

The issue was the difference in the JSON being returned in 1.25.1 vrs 1.27.0.

I was referencing slotno attribute which has changed to slot in 1.27.0

Once the code referenced the value from slot attribute in the JSON, the transaction submitted successfully.

Thanks for getting pointed in the right direction.

output 1.25.1

  ``` output 1.25.1
  {
     "blockNo": 2570754,
     "headerHash": "a07bb8990fb9f3ea740163bc6e44e6174dc8735693b60c81e84677f67bd300fb",
     "slotNo": 26316179
  }
  ```

output 1.27.0

  ``` output 1.27.0
  epoch : 135
  hash  : ec8bb2ab2b11edd298edc7aa8f91548089669f52103914c2e55fc2e73e82550f
  slot  : 28173138
  block : 2633340
  era   : Mary
  ```
1 Like
8

btw what type of transaction have you submitted?

9

Just a simple transaction. Following the documentation in the Stake Pool course.