Two questions please: the rpcauth works in cli only? I get an error at a rpc call (php). What exactly does this output mean: “tx-expiring-soon: expiryheight is 475751 but should be at least 476053 to avoid transaction expiring soon”? I cannot send the funds from a multisig address (testnet).
Thanks 4 your answers!
No, it’s not limited to the CLI. It is however only available from localhost by default more here: Zcash.conf Guide — Zcash Documentation 5.2.0 documentation. For PHP I have used GitHub - denpamusic/php-bitcoinrpc: Fully unit-tested Bitcoin JSON-RPC client based on GuzzleHttp. before which I can confirm works.
For transaction expiry see Transaction Expiry - Electric Coin Company for an overview and there is an issue here for some additional context: v3 transaction feature: expiry height · Issue #3317 · zcash/zcash · GitHub. The
expiryheight argument has since been added to
createrawtransaction see createrawtransaction - Zcash 4.5.1-1 RPC Docs
tnx for the answer. I meant cookie rpcauth like at bitcoin.conf ( rpcauth=alice:f7efda5c189b999524f151318c0c86$d5b51b3beffbc02b724e5d095828e0bc8b2456e9ac8757ae3211a5d9b16a22ae). I dont want to store the password plain at scratch.
Thanks 4 the expiry hint - totally missed that point.
The cookie auth works for anything that can read the local disk, knows where to look for the cookie, and has permissions to read it. If you’re having issues, please raise a ticket at Sign in to GitHub · GitHub!