romanz/electrs

Implement a history pruning limit

Open

#184 opened on Oct 25, 2019

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Rust (551 forks)github user discovery
enhancementhelp wantedperformancequestion

Repository metrics

Stars
 (1,366 stars)
PR merge metrics
 (PR metrics pending)

Description

Is possible to implement so called history pruning limit to Electrs? The number means how many transactions the server may keep for every single address (example 20 the latest transactions). This could be adjustable value. This will decrease db size and might get small performance boost.

Contributor guide

Research direction
Examine the current transaction storage structure in Electrs, implement a configurable pruning limit that keeps only the latest N transactions per address, and ensure performance impact is minimal.
Tech stack
rust
Domain
backenddatabase
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
RustBitcoin
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40