bcgov/indy-tails-server

Cache transactions retrieved after a pool request

Open

#12 opened on Dec 9, 2020

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (54 forks)auto 404
enhancementgood first issuehelp wanted

Repository metrics

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

Description

When publishing a new tails file, the server needs to read the current state of the targeted ledger in order to check the state of the revocation registry.

Every time a new file is pushed, the server needs to "start from scratch" and re-read all of the transactions from inception on the specified ledger (via the genesis file specified during upload + new entries on that ledger).

To speed-up this process, it would be nice to have the last know state for a specific ledger cached so that only transactions newer than the last update - if any - will need to be fetched and refreshed.

Contributor guide

Research direction
Investigate the current tails file publishing flow, identify where ledger state is read, and propose a caching mechanism to store the last known state (e.g., last transaction sequence number or timestamp) to allow incremental updates. Consider using an in memory or file based cache, and ensure cache invalidation when ledger changes.
Tech stack
python
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.
Mostly clear
Prerequisites
PythonHyperledger Indy basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55