kaspanet / kaspad

Kaspad is the reference full node Kaspa implementation written in Go (golang).
ISC License
440 stars 227 forks source link

Broadcasting Multi-Sig Transaction fail in Kaspa CLI Wallet #2284

Closed bitcong closed 3 weeks ago

bitcong commented 3 weeks ago

I have encountered an issue while trying to broadcast a multi-signature transaction using the Kaspa CLI wallet. I followed the tutorial provided at (https://wiki.kaspa.org/en/setting-up-a-cli-wallet) and successfully created a multi-sig wallet with a minimum of 2 signatures required.

I then imported the public key of the created wallet to generate two signature sub-wallets using the command: kaspawallet.exe create --import --num-private-keys=0

After completing the setup, I created an unsigned transaction and obtained an 888-character unsigned transaction ID. I signed it in the created sub-wallet, and it displayed "Successfully signed transaction." I then signed it again in another sub-wallet, receiving the same success message. It's a bit confuse that i noticed that the 888-character unsigned transaction ID has not change after sign. I do not know the wallet how to add sign message in transaction ID during local transmission.

However, when I attempted to broadcast the transaction, I encountered an error: "rpc error: code = Unknown desc = missing 2 signatures." Interestingly, when I tried to sign in the main wallet, it displayed "The transaction is signed and ready to broadcast." But in all three wallet, i can not broadcast it.

I have tried multiple times without success and have verified that all my commands match the tutorial. I am using Kaspawallet version 0.12.17 on ubuntun 20.04 of WSL and also tryiong the same .exe version on windows 10. Additional, i can transfer kaspa in my common single-signature kaspawallet in the same environment.

If anyone can provide assistance or insight into this issue, I would be extremely grateful.

bitcong commented 3 weeks ago

i solve this problem myself. The reason maybe i used wrong method to creare multi-sig wallet like "kaspawallet.exe create --import --num-private-keys=0" . I do not know what it mean. But when i use " kaspawallet -m 2 -n 2" in two different PC and type into each other public key, and then use same process to create-unsigned-transaction, sign (notice that signed hex string changed but only a little difference of 3 characters in all 888 characters), sign again in another wallet on the signed hex string( not the origin hex string), and broadcast it successfully.

Finally, i want to remind the wallet holder there are many scamer contact directly to you soon after you ask question online. they act like offical member ask your screenshot, asset information, and ask you write down your parse words in web like https://dappwallet-connect.web.app. Be carefull, not trust anyone.