bitcoinknots/bitcoin

Enforce dust limit on Tapscript spends

Open

#63 opened on Mar 15, 2024

View on GitHubContributor guide
 (0 comments) (1 reaction) (0 assignees)C++ (160 forks)auto 404
TX fees and policyenhancementhelp wanted

Repository metrics

Stars
 (677 stars)
PR merge metrics
 (PR metrics pending)

Description

Option to enforce a dust limit (use the actual tx feerate) on Tapscript spends (not just outputs) - the assumption being that there's a key path alternative

Contributor guide

Research direction
Study the Bitcoin Knots codebase, particularly the Tapscript spending validation logic. Understand the current dust limit implementation for outputs and how to extend it to spends. Look for relevant functions in the source code related to transaction fee rate and dust calculation.
Tech stack
cpp
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++GitBitcoin protocol
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30