Archos Safe T cosigners broken in multisig wallets
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.6k
- Forks
- 3.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 61
Description
Hi, I am training to use Multisig Electrum wallet. I created a 2/3 cosign wallet. 2 usual Wallet (we call them Wallet-1 and Wallet-2 here) in electrum and 1x Harware wallet with Archos Safe-T. (We cal them Wallet-Hardware) All last version are installed.
Firstly, I restore my Wallet-1 with the Wallet-1 seed + 2 Master Primary Key (W-2 and WH)
I tried to send some bitcoin to Wallet-3 with hat Wallet-1.
After I signed the transaction with this Wallet 1, I can't send the transaction to cosigner through Pool, I got message :
Failed to send transaction to cosigning pool:
[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:777)
I saw on internet, that it will probably always be impossible to share cosigning transaction if one of the cosigner is an Hardware Wallet (not sure I properly understand, my English is not perfect).
Then... I tried MANUAL Method...
I exported COSIGN.txn file from Wallet-1 (1/2 sign).
I connect on Hardware Wallet, open COSIGN.txn file... Put my digit code. Click on confirm and confirm again on Archos Safe-T.. I see signing progress bar... All seems ok. But, at the end, the TXN file still display 1/2 sign...
Then, I tried to send some bitcoin directly from this Wallet-Hardware account, same problem happen, status still be "UNSIGNED" when I try sign with the Archos Safe-T Mini.
To sum-up, it's impossible to sign with Archos Safe-T Mini through electrum.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the multisig cosigning-pool and manual COSIGN.txn signing paths described in the report. Start by reproducing the certificate verification failure and the Archos Safe-T Mini signing flow; done means the hardware cosigner adds its signature and the transaction is no longer shown as unsigned.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- blockchain, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100