transaction times out if address is in multiple accounts across different wallets
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 493
- PR merge metrics
- No merged PRs in 30d
Description
Jack is aware of this one and it's a strange scenario, and not sure how often it's happening in the wild. I ran into it by having multiple synced wallets in a database which had imported channels, so I ended up with 2 accounts that had the same wallet address. If you tried to create a transaction that affected that address, the on transaction message would list the address twice and time out. The transaction itself would get sent.
Would need to take a deper dive to see if this is affecting any of the timeouts we are seeing on lbry.tv/youtube sync.
on transaction log: bFrFeWx1tmS53Rhh1HTBqh47kAM8tx8uCy,bJ1JYKc4LhfELwj7xJvZVyxL9Miyq4MUkA,bVfinziL24CSLZChR3XEMAzu9W8FjZ4YQ7,bVfinziL24CSLZChR3XEMAzu9W8FjZ4YQ7
Contributor guide
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 or test is named. Start by reproducing the scenario with duplicate addresses across synced wallets and trace the transaction message and timeout handling; done means the transaction no longer lists the address twice or times out, with the effect on lbry.tv/youtube sync timeouts assessed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100