bitcoinknots/bitcoin

Whitelist and/or discounting privacy transactions

Open

#65 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

Currently, Samourai privacy transactions (tx0) are using over the default datacarriersize limit of 42 bytes. This isn't ideal, and while they should really fix their end to not require datacarrier at all, it makes sense to whitelist it until then.

This needs some way to differentiate their tx0 from other datacarrier txs.

Maybe it would make sense to have an option to then prioritise them further (but that might not be fair unless it can detect other privacy txs too)

Contributor guide

Research direction
Research how Samourai tx0 transactions are structured and how to differentiate them from other datacarrier transactions. Then modify the policy to allow or discount them.
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.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C++Bitcoin transactions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40