Looks like it
and yet ?
Network.Socket.connect: <socket: 13>: does not exist (Connection refused
That’s a screenshot of the mainnet Daedalus running, but according to your post, you are trying to run the testnet CLI with the testnet socket.
Hi yes once again you are 100% right so I adjusted the paths below
/Applications/Daedalus\ Mainnet.app/Contents/MacOS/cardano-cli query tip --mainnet
Command failed: query tip Error: Error while looking up environment variable: CARDANO_NODE_SOCKET_PATH Error: “CARDANO_NODE_SOCKET_PATH”
export CARDANO_NODE_SOCKET_PATH=~/Library/Application\ Support/Daedalus\ Mainnet/cardano-node.socket
/Applications/Daedalus\ Mainnet.app/Contents/MacOS/cardano-cli query tip --mainnet
cardano-cli: Network.Socket.connect: <socket: 13>: does not exist (No such file or directory)%
so I restarted and Deadalus is not syncing yet I will give it more time not sure why ?
After nearly an hour again heres the command looks better
/Applications/Daedalus\ Mainnet.app/Contents/MacOS/cardano-cli query tip --mainnet
{
“hash”: “51ce4018647700352cc5cb0458df82bd46a8b0522cd34ca94f694cf1bebcce43”,
“block”: 6812773,
“slot”: 51823040,
“syncProgress”: “100.00”,
“era”: “Alonzo”,
“epoch”: 317
Di i need this equivalent ?
cardano-cli address build --payment-verification-key-file payment.vkey --out-file payment.addr --mainnet
As my UTXO is blank ?
/Applications/Daedalus\ Mainnet.app/Contents/MacOS/cardano-cli query utxo --address $paymentaddr --mainnet
TxHash TxIx Amount
only thing I can think of is at this stage there is no txhash here ?
paymentaddr=$(/Applications/Daedalus\ Mainnet.app/Contents/MacOS/cardano-cli address build --payment-verification-key-file payment.vkey --mainnet)
Yes still not outputting tx hash ?
cardano-cli query utxo --address $paymentaddr --mainnet
TxHash TxIx Amount
Did you even transfer ADA onto that address?
Does the content of $paymentaddr look like the correct address?
Is the node fully synced?
Hi thanks again
Did you even transfer ADA onto that address?
Not yet is guessing thats why theres no TX hash right if so thats so obvious I overlooked it ?
Does the content of $paymentaddr look like the correct address?
yes
Is the node fully synced?
Yes
How much should I can do like we did last time overpay and then we set a send change parameter I remember something about that, apologies my memory is not perfect am picking through my notes
You can’t guess the correct value. That we are giving a --change-address for the rest to go back into $paymentaddr is not overpaying, but it’s expected. You don’t want to load new ADA into that $paymentaddr for every single mint. That also costs transaction fees.
You need ADA in there for fess and the minimal ADA that have to go with minted tokens, when sending them to other addresses.
I have loaded my minting payment address with 10 ADA, so that it should be enough for around 5 mints of single little NFTs. If you plan on doing more – or messing up more often – put a little more into it.
You seem to be doing/learning a lot of things at the same time. I could not fully understand what I am doing that way, but do as you want.
Yes thanks again I should of repeated the process sooner and then it would of been fresh ?
The Ada arrived so onto the next step Policies from what I recall and then tx build ?
1 Like
Yes, policy. And then minting transaction.
1 Like
Hi Yes thanks and if successful this time I can look at burning the others. I have done some reading will come to that after this mint
And this time I remember to run policyid=$(/Applications/Daedalus\ Mainnet.app/Contents/MacOS/cardano-cli transaction policyid --script-file policy.script) after nano the policy
Submit error again this time its slot numbers back to that again ?
Applications/Daedalus\ Mainnet.app/Contents/MacOS/cardano-cli transaction submit --mainnet --tx-file matx.signed
Command failed: transaction submit Error: Error while submitting tx: ShelleyTxValidationError ShelleyBasedEraAlonzo (ApplyTxError [UtxowFailure (WrappedShelleyEraFailure (UtxoFailure (OutsideValidityIntervalUTxO (ValidityInterval {invalidBefore = SNothing, invalidHereafter = SJust (SlotNo 51889677)}) (SlotNo 51889761))))])
Increase the validity interval or remove it completely, it is optional for most of the transactions.
We are somewhere around slot 51889889. That is larger than 51889761.
You did not give enough room. Or forgot to update the before in the policy.script and the --invalid-hereafter.
Ok I removed --invalid-hereafter 51889677 \ and now this
Command failed: transaction submit Error: Error while submitting tx: ShelleyTxValidationError ShelleyBasedEraAlonzo (ApplyTxError [UtxowFailure (WrappedShelleyEraFailure (ScriptWitnessNotValidatingUTXOW (fromList [ScriptHash “8dec95dfd60b05de0c97a703e1d1baff330fb0f4cba86b92e005aa4a”])))])
Yes, since you want to do a time-locked mint, you need an --invalid-hereafter.
Ah ok so --invalid-hereafter 51889761 \ ?
No, that’s in the past. It needs to be in the future, so that the transaction is allowed. And it needs to match the policy.