Cardano CLI Preprod Query UTXO Error

[Ralph_L_Aurage]

I am running the following command cardano-cli query utxo --testnet-magic 1 --address addr_test1vprrnztnlegw4wht4z95ktp6gj9yzz9jllwm76kjxdga5ncg229l7 and I get no UTXOs but when I check the address here I can see that there ae UTXOs at that address. What am I doing wrong?

[Alexd1985]

@Ralph_L_Aurage

–testnet-magic 1

--testnet-magic 1097911063

[Ralph_L_Aurage]

I’m on the preprod network so I am using --testnet-magic 1

When I use --testnet-magic 1097911063 I get this error:

cardano-cli: HandshakeError (Refused NodeToClientV_13 "version data mismatch: NodeToClientVersionData {networkMagic = NetworkMagic {unNetworkMagic = 1}} /= NodeToClientVersionData {networkMagic = NetworkMagic {unNetworkMagic = 1097911063}}")

[Ralph_L_Aurage]

And I’m also using Demeter for my node and it says the sync progress of the node is 98.80%. Is that the reason for the error perhaps and if so, is there any way to speed up the syncing?

[HeptaSean]

@Ralph_L_Aurage

I’m on the preprod network so I am using --testnet-magic 1

When I use --testnet-magic 1097911063 I get this error:

You are totally right. The magic 1097911063 was for the old testnet and shouldn’t be used since last summer.

@Ralph_L_Aurage

sync progress of the node is 98.80%. Is that the reason

Since all transactions to the address were only six hours ago (3 hours at the time of your message), that is totally possible.

@Ralph_L_Aurage

is there any way to speed up the syncing?

As far as I understood Demeter, it is not you who is running the node, but they are running it for you and just give access to these different playground instances. No idea why that should go out of sync.

[georgem1976]

Are you running cardano-node 1.35.4 or 1.35.5? If you are running an older version, upgrade. The older versions are not supported anymore after the last hard fork (which took place about 36 hours ago).

[Ralph_L_Aurage]

@HeptaSean

As far as I understood Demeter, it is not you who is running the node, but they are running it for you and just give access to these different playground instances. No idea why that should go out of sync.

When you say playground instances, do you mean it can’t be used in a production environment? Like if I was to use their services to help facilitate with the mint of an NFT collection, do you think they would be able to handle something like that? If not, can you recommend a service out there where I can essentially “rent” a node for the likes of an NFT collection mint? Thank you

[Ralph_L_Aurage]

This is the version I’m using cardano-cli 1.35.4 - linux-x86_64 - ghc-8.10

[georgem1976]

cardano-node not cardano-cli. But you probably have the same version.

[HeptaSean]

@Ralph_L_Aurage

When you say playground instances, do you mean it can’t be used in a production environment?

I just called it “playground”, because that’s what they call the thing I get without paying.

I really don’t know if their paid offers are meant to be used for production. I had the impression that it is more an exploration and development tool.

@Ralph_L_Aurage

mint of an NFT collection, do you think they would be able to handle something like that?

On the other hand: If it is not a huge hype, it probably does not use that much resources.

But still: all keys would be in their system, which is strange.

You say that you are not able to run a node yourself, but you do have a web server, where the website for that mint will be hosted?

@Ralph_L_Aurage

If not, can you recommend a service out there where I can essentially “rent” a node for the likes of an NFT collection mint? Thank you

Don’t know. You still seem to use cardano-cli. Since that only works locally over a Unix socket file, they would have to give you shell access. Not aware of any service that does that.

As said previously:

@HeptaSean

Hmm, yes, then writing it as a nodejs application might be closer to what you are comfortable with:

• cardano-serialization-lib can be used to construct transactions: cardano-serialization-lib/generating-transactions.md at master · Emurgo/cardano-serialization-lib · GitHub
• If you want to be as independent as possible, you can use something like https://ogmios.dev/ and https://cardanosolutions.github.io/kupo/ to monitor and submit transactions on your own node.
• Or you use an API like https://docs.blockfrost.io/ for that, but then you are dependent on that.

All of that would be more elegant than calling out to the shell to cardano-cli in my opinion.

Write your application in JS without any callouts to cardano-cli. Use Blockfrost to query the blockchain and submit transactions. I’d run it on a server, but if you want you can also run it at home.

[HeptaSean]

@georgem1976

But you probably have the same version.

I wouldn’t count on it. Demeter can very well have a different node version running and provide it to the workspaces than the cli version that is installed inside the workspaces. …

[Ralph_L_Aurage]

cardano-node 1.35.4 - linux-x86_64 - ghc-8.10 But it’s working now, I can see the utxos, thank you

[Ralph_L_Aurage]

Thank you for the comprehensive answer, I will get in contact with them to see if they can indeed facilitate such a task and if not then I might have to do what you suggested and go the blockfrost route but I’m sure they too have their own limitations. You’re saying I can just use my own hosting server if I just build a Node JS application? Doing it this way wouldn’t require the use of a node?

[Ralph_L_Aurage]

Sorry do you know what this error means? I am trying to mint an NFT and I’m getting this error

Command failed: transaction submit Error: Error while submitting tx: ShelleyTxValidationError ShelleyBasedEraBabbage (ApplyTxError [UtxowFailure (FromAlonzoUtxowFail (WrappedShelleyEraFailure (ScriptWitnessNotValidatingUTXOW (fromList [ScriptHash "a9b5b9d4e78b26fecdb4fc49acc74da5d713007658f957fe8875707f"])))),UtxowFailure (FromAlonzoUtxowFail (WrappedShelleyEraFailure (MissingVKeyWitnessesUTXOW (WitHashes (fromList [KeyHash "46398973fe50eabaeba88b4b2c3a448a4108b2ffddbf6ad23351da4f"])))))])

[HeptaSean]

@Ralph_L_Aurage

ScriptWitnessNotValidatingUTXOW

You are providing a script that is not needed, …

@Ralph_L_Aurage

MissingVKeyWitnessesUTXOW

…, but did not provide a payment key signature that is needed.

[Ralph_L_Aurage]

Oh I see, I’m getting this error now:

Command failed: transaction submit Error: Error while submitting tx: ShelleyTxValidationError ShelleyBasedEraBabbage (ApplyTxError [UtxowFailure (FromAlonzoUtxowFail (WrappedShelleyEraFailure (ScriptWitnessNotValidatingUTXOW (fromList [ScriptHash "a9b5b9d4e78b26fecdb4fc49acc74da5d713007658f957fe8875707f"]))))])

[HeptaSean]

@Ralph_L_Aurage

ScriptWitnessNotValidatingUTXOW

Searching through old forum threads: This can happen if you try to mint with a time lock, but do not provide the corresponding --invalid-before and/or --invalid-hereafter arguments to the transaction.

[Ralph_L_Aurage]

Thank you, I had an issue with the slot number on the --invalid-hereafter parameter