vacuumlabs/cardano-hw-cli

MultiSig/Minting testing

gitmachtl opened this issue · 8 comments

gitmachtl commented

@KubqoA whats the version to use with the ledger right now to test the multisig/minting support? i tried your branch and also the versions of the cardano-app (3.0.0). but when i try the following i get an error about the app-version:

$ cardano-hw-cli address key-gen --path 1855H/1815H/0H --verification-key-file mint-hw.vkey --hw-signing-file mint-hw.hwsfile
Error: Device app version unsupported. Please upgrade to 2.4.

$ cardano-hw-cli version
Cardano HW CLI Tool version 1.7.0-rc0
Commit hash: 23406fe8c4e58e83e166b44be102a902a9ae4938

$ cardano-hw-cli device version
Ledger app version 3.0.0
KubqoA commented

Hi, it should be this PR: #98, but it seems you got that right according to the commit hash. Can I ask how did you build the tool, it seems to me that the issue is in the ledgerjs-cardano-shelley library and the fact that it seems you are not using the version that supports multisig. Are you sure you updated the yarn dependencies before building the tool?

gitmachtl commented

Hi, i tried the current version of https://github.com/vacuumlabs/ledger-app-cardano-shelley and also https://github.com/LedgerHQ/app-cardano . Should be in sync right now for the multisig support.
About the hw-cli, i cloned the repo in a new directory and ran yarn build-linux-tar like always. Any additional steps needed before building the latest version?

KubqoA commented

Are you sure you are using the ja/multisig branch for the cardano-hw-cli?
I tried to build the develop branch of cardano-hw-cli and using that I am able to replicate the error you reported. However, when I build the ja/multisig branch of cardano-hw-cli it works just fine.
I quickly added one more commit that bumps the version on the ja/multisig branch. If you build that branch the version of cardano-hw-cli should now show:

$ cardano-hw-cli version
Cardano HW CLI Tool version 1.8.0-rc0
gitmachtl commented

ok strange, now i can't compile it anymore:

$ yarn build-linux-tar
yarn run v1.22.15
$ ./scripts/build-common.sh && ./scripts/build-linux-tar-gz.sh && rm _package.json
$ rm -rf ./dist && rm -rf ./node_modules
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
error An unexpected error occurred: "https://github.com/vacuumlabs/ledgerjs-cardano-shelley/releases/download/v4.0.0-multisig-rc4/cardano-foundation-ledgerjs-hw-app-cardano-v4.0.0-rc4.tgz: Request failed \"404 Not Found\"".
info If you think this is a bug, please open a bug report with the information provided in "/home/administrator/cardano/compile/compile-cardano-hw-cli/cardano-hw-cli/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
$ tsc
/bin/sh: 1: tsc: not found
error Command failed with exit code 127.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
$ nexe ./dist/index.js -o ./build/linux/archive/cardano-hw-cli/cardano-hw-cli -t linux-x64-12.16.2
/bin/sh: 1: nexe: not found
error Command failed with exit code 127.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
./cardano-hw-cli/
./cardano-hw-cli/Release/
./cardano-hw-cli/Release/HID.node
./cardano-hw-cli/Release/usb_bindings.node
./cardano-hw-cli/Release/HID-hidraw.node
./cardano-hw-cli/package.json
Done in 2.25s.
KubqoA commented

It seems like the download for the rc4 release of ledgerjs-cardano-shelley library changed it's name. I updated the branch to use rc5 and now you should be able to build it. Can you please try again?

gitmachtl commented

yes, that worked. now also the cardano-app 3.0.0 is working with the hw-cli, thx!

$ cardano-hw-cli version
Cardano HW CLI Tool version 1.8.0-rc0
Commit hash: 477ae160f0ff2a1515b1709d641f21e9047b58d3
KubqoA commented

Glad to hear that!

gitmachtl commented

@KubqoA

$ cardano-hw-cli transaction witness --tx-body-file /tmp/funds.txbody --hw-signing-file assets/hwpolicy.policy.hwsfile --testnet-magic 8 --out-file /tmp/hwpolicy.witness
Error: Missing payment hardware signing file
$ cat assets/hwpolicy.policy.hwsfile
{
    "type": "PaymentHWSigningFileShelley_ed25519",
    "description": "Payment Hardware Signing File",
    "path": "1855H/1815H/0H",
    "cborXPubKeyHex": "58403812865f6859c42eb1eb8ab93c8f0e8783be193d8ef5fe257b567f31b47576c23707c93f6e14b65e174e586993abe87a14bb61fc159af72675d88d013a747563"
}