Disable built-in ledger cache and browser tools when using IndyScan as the ledger browser
- Dominant language
- Python
- Stars
- 170
- Forks
- 189
- PR merge metrics
- No merged PRs in 30d
Description
Support for linking to an IndyScan instance for ledger browsing was recently added, bypassing the build-in ledger browsing tools. However, in the background, the ledger cache is still maintained and updated, and the built-in browser tools are still available.
The cache and build-in browser tools should be disabled when using IndyScan as the ledger browser. i.e. When `INDY_SCAN_URL` is set. This will save on memory and disk usage.
Contributor guide
Research direction
Start by tracing where INDY_SCAN_URL is read and where the ledger cache and built-in browser tools are initialized or exposed. Verify the behavior with IndyScan configured: the cache should not be maintained or updated, and the built-in browser tools should not be available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, distributed-systems
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100