Trezor TT 2.8.10 multisig tx signing
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.6k
- Forks
- 3.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 61
Description
Description
I found two issues shen signing outgoing transaction
- screenshot number one, its send to my self transaction and you have to confirm recipient #1 and recipient #2 even you are sending to one recipient
- screenshot number two , this transaction only shows locktime and amount summary hold to confirm, no screen with address of recipient
fw T2T1-2.8.10-41b7863
Electrum Version 4.5.8
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
No source file, test, or entry point is named. Start by reproducing both multisig signing cases with T2T1-2.8.10-41b786 and Electrum 4.5.8, then trace the Trezor signing flow; done means recipient confirmations and recipient-address screens match the transaction being signed.
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
- Needs clarification
- Newbie friendliness
- 25/100