When it says command not found, you were most certainly not doing the line continuation escaping right. The backslash has to be immediately before the newline. There may not be a space after it or something like that.
Has the same effect: The space between amount and policy id is not interpreted by the shell as separation of arguments, but is given to cardano-cli as part of one argument to the parameter --tx-out.
This command worked thanks I just need to remember how to balance the outputs now there is 4
Command failed: transaction build Error: Non-Ada assets are unbalanced: 994429215 lovelace + -175750000 80d9b32ae2b30e62bbc5234e7cf90f1dd4190fa3b682ed01f6f80115.Vilvi
It seemed to come down to policy.script syntax, I rebuilt everything and submitted successfully to Testnet with the bare minimum policy.script it would not accept the syntax for time locking so its almost vanilla just keyhash this isn’t what I need for Mainnet minting.
I have been building the mainnet minting transaction for so many hours it fails.
Its not particularly clear on any forums I did some IT trouble-shooting and search on non google browsers. Eventually I came up with this
If you have ANY additional json in policy.script It will fail transaction build UNLESS it has this
'–invalid-hereafter $slotnumber
More searching I found an explanation on github – Forget the Man page
Building and signing transactions
Transactions vary in complexity, depending on their intended outcomes, but all transactions share a number of attributes:
Input - contains funds that are spent by the transaction. It is simply the output of an earlier transaction. A transaction can have multiple inputs.
Output - determine where the funds go to. An output is given by a payment address and an amount. A transaction can have multiple outputs.
Payment address - an address that can receive payments, This is the only type of addresses that can be specified in a transaction output.
Payment and stake key pairs - sets of files containing a public verification key and a private signing key.
Invalid-before - The slot that the transaction is valid from. This can only be specified in the Allegra era and onwards.
Invalid-hereafter - represents a slot, or deadline by which a transaction must be submitted. This is an absolute slot number, rather than a relative one, which means that the --invalid-hereafter value should be greater than the current slot number. A transaction becomes invalid at the invalid-hereafter slot.
Era - Transactions can differ between the eras (e.g have new features such as multi-assets) so we must specify the era we are currently in.
To create a transaction in the shelley era we need to follow this process:
So my options here and now unless someone can help is mint with no time lock on the policy seems a bit strange that it only works if the policy script has only the sig and keyhash values.
If you have changed the policy script, it is also a changed policy id. The latter is a hash of the former. Everytime you change the file, you have to redo
Earlier I did run this command
policyid=$(/Applications/Daedalus\ Testnet.app/Contents/MacOS/cardano-cli transaction policyid --script-file policy.script)