Tezos Stack Exchange is a question and answer site for users, experts, and developers of the Tezos blockchain project. It only takes a minute to sign up.
Sign up to join this community
How do I know that remote-signer socket started is working expected and accepting signing requests from my baker server without actually sending a transfer transaction.
Right now I just do a transfer .00005 from <key1> to <key2> just to test if remote-signer setup is working.
Is there any other way like any transaction that require signing but don't require transfer of tz.
I just prefer to do this...it's a direct request to sign data without any possibility of forgetting to add the --dry-run flag.
tezos-client sign bytes 0x03 for <tz alias or tz address>
Here 0x03 is just any old random number. You could put any hex value here. If the remote signer is working you'll get back a message like:
Signature: sigPab0p1MdqojAaNTvASSvLo4ULEujfNFurF71EdoruABoPLLwmSxEDJf4NfQx8nJi3ncjfMEJbiWojTDXDUB8wNF5fgFIbA
I figured out that you can use the --dry-run option in the transfer statement so that node will send transaction to remote-signer to sign, and you can check the remote-signer logs to see if everything is working fine or not.
--dry-run will not actually send the transaction to the network.
Another option would be to use Kiln. Kiln monitors your baker and will notify you if you miss any baking or endorsement opportunities (which will indicate that the signer is down).
It can be found here.
signer is working and this software will not do so.