Inherit labels in change addresses
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.6k
- Forks
- 3.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 61
Description
Would be great to not have manually re-label all change addresses after sending transaction. It's important to have some separate addresses you don't want to cross, and gets super annoying when we use privacy change (not 1 change address but more). Ideally should just set the label of the input address. If multiple inputs with different labels are used, concatenate them.
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 file or test entry point is named. Start by locating the transaction change-address labeling flow and trace how input labels are available when privacy change creates multiple addresses. Done means change addresses inherit one input label, or a defined concatenation of multiple input labels, without manual relabeling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100