fastfrank@~ $ sui keytool list
Sui Address | Public Key (Base64) | Scheme
----------------------------------------------------------------------------------------------------
0x4cb2a458bcdea8593b261b2d90d0ec73053ca4de | AMapcI6o/KufoT+GZvKl+BT/lVsAq7Qe84fkI9e3Dnas | ed25519
0xcc9e52e70a2233fe80fea5458a24b94272a1b0e9 | AgNgevhsriSuu3jwL8TeY9g7rQJHOdCdVC9RbAgwi7NeeA== | secp256r1
fastfrank@~ $ sui client active-address
0xcc9e52e70a2233fe80fea5458a24b94272a1b0e9
fastfrank@~ $ sui client gas
Object ID | Gas Value
----------------------------------------------------------------------
0x5b93e69354fd073908031c80d8e4247c60662245 | 9999861
0x72229b3ec58a5e92922093fc65750487ebf16c69 | 9999861
I then do:
fastfrank@~ $ sui client serialize-transfer-sui --sui-coin-object-id 0x5b93e69354fd073908031c80d8e4247c60662245 --to 0x4cb2a458bcdea8593b261b2d90d0ec73053ca4de --gas-budget 500
Data to sign: AAAAAANMsqRYvN6oWTsmGy2Q0OxzBTyk3gDMnlLnCiIz/oD+pUWKJLlCcqGw6VuT5pNU/Qc5CAMcgNjkJHxgZiJFjQAAAAAAAAAgYTgPH7LLHk4u7jN/SpNEnGfHdJLuuftXjuekE6E7OacBAAAAAAAAAPQBAAAAAAAA
However; when I use sui keytool sign I get:
fastfrank@~ $ sui keytool sign --address 0xcc9e52e70a2233fe80fea5458a24b94272a1b0e9 --data AAAAAANMsqRYvN6oWTsmGy2Q0OxzBTyk3gDMnlLnCiIz/oD+pUWKJLlCcqGw6VuT5pNU/Qc5CAMcgNjkJHxgZiJFjQAAAAAAAAAgYTgPH7LLHk4u7jN/SpNEnGfHdJLuuftXjuekE6E7OacBAAAAAAAAAPQBAAAAAAAA
2023-01-14T21:47:34.834967Z INFO sui::keytool: Data to sign : AAAAAANMsqRYvN6oWTsmGy2Q0OxzBTyk3gDMnlLnCiIz/oD+pUWKJLlCcqGw6VuT5pNU/Qc5CAMcgNjkJHxgZiJFjQAAAAAAAAAgYTgPH7LLHk4u7jN/SpNEnGfHdJLuuftXjuekE6E7OacBAAAAAAAAAPQBAAAAAAAA
2023-01-14T21:47:34.834996Z INFO sui::keytool: Address : 0xcc9e52e70a2233fe80fea5458a24b94272a1b0e9
unexpected end of input
based on what you posted, you may be using a sui before this fix is landed. can you make sure you use the latest sui build? and make sure what you pass in for the signing command is the one from âIntent Message to Sign: ${DATA_TO_SIGN}â?
Donât know why our messages are being flagged in this channel.
Anyway, I had downloaded the binaries after 0.21.0 was deployed. I will re-fetch the binaries and try again, although the steps I took are the same in your documentation no?
I just did another binary install and there arenât any changes that would have made a difference in the error. I guess I will wait for when your fix is deployed as I think the CLI usage I posted above shouldnât need to change, correct?
Update: I was able to build sui from main in repo where keytool finished with good results!!
Yes, the stack exchange accepted answer Method #2 would be the route if the PR you noted wasnât going to happen. For now the âbrute forceâ approach is working but hitting RPC to fault to changing the âvâ is rather nasty.
Thanks for this follow up, I usually push a new pysui version within 24 hrs of a Sui release. All good!