hey @HeptaSean (or anyone), I’m adapting some of our old scripts along these lines & noticed something I can’t figure out in our offline environment, running cardano-cli transaction build like so:
cardano-cli transaction build \
--mainnet \
--tx-in $(cat payment.utxo) \
--tx-out $(cat wallet.addr)+$(cat rbal) \
--change-address $(cat low/payment.addr) \
--withdrawal $(cat low/stake.addr)+$(cat rbal) \
--out-file tx.draft
It gets this error, as if we weren’t properly pointed to a live node to submit a transaction:
Command failed: transaction build Error: Error while looking up environment variable:
CARDANO_NODE_SOCKET_PATH Error: "CARDANO_NODE_SOCKET_PATH"
Why would any transaction building, designed to work offline, require a connection to a live Cardano node?
We didn’t notice this before since our automation was still using the old transaction model of building the dummy transaction first & are finally getting rid of that old stuff now.
If there was a memo about cardano-cli transaction build only working on a node machine, or with a connection to one, then I definitely missed it. Hopefully I’m making some dumb mistake regarding the syntax or context.
I was thinking it might need a timing reference from a live node if --invalid-hereafter were not specified, but it gets the same error even using that option. 