dust output kept in some cases(?)
Open
Nobody has claimed this yet.
question ❓
- Dominant language
- Python
- Stars
- 8.6k
- Forks
- 3.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 61
Description
error: {'message': 'the transaction was rejected by network rules.\n\n64: dust\n[0100000001698499ec304433415d3e005e5e0e96230782af97a706cf4a46cdc78480bfe25a010000006b483045022100dbeaccd79262c7e1210b0fabe22f4c0d706c9dadada0eb0c790a3b00ee9051280220605756db8a317bf899b11785eb1866108679fd900e35959a1c43aac1c79f71c8012102156b6ba67d59956130ccc2699c2870adec8852011e4f9ef08ed44015396e5d48fdffffff02ae0000000000000017a91487e877227b456c75b1534cfd329a35f98c2007538765c00400000000001976a91448101a2aeeb61a6ffd8ede9401acddb8a76cfa8988acc20f0800]', 'code': 1}
this shit pops up every time i try to send bitcoins ANYWHERE
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, test, version, or reproducible transaction steps are named. Start by reproducing the reported failure when sending bitcoin and inspect how the displayed network-rules “dust” rejection is surfaced; done means the cause is identified and the behavior is covered by a verified change or a clarified report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- blockchain, payments
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100