Skip to content

MASQ-Project/MASQ-Node-issues

View on GitHub ↗Related repositories →

This repo contains the issues that are used for planning MASQ Node product work. It has no code in it, only GitHub issue tickets

active 2023-08-172025-12-07 (UTC)

Partial coverage23,747 / 26,314 hourly files (90%) · 2 absent upstream · 2,566 failed, retryable2023-08-152026-08-15 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
225
Pushes
0
Pull requests
0
Issues
140
Stars
0
Forks
1

Activity over time

Daily event counts in the loaded window

Line chart, 844 days from 2023-08-17 to 2025-12-07. Pushes: 0 total, peak 0 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 140 total, peak 15 in a day. Comments: 84 total, peak 8 in a day. Stars: 0 total, peak 0 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
kauri-hero1160034
dnwiebe390021
bertllll290011
utkarshg618005
czarte9005
masqrauder5004
Syther0073001
canny[bot]2000
Jarrel-doe1001
kriddreak1001
FinsaasGH1001

Recent activity

Latest issues, pull requests and releases

  • Issue#828utkarshg62025-12-07 13:49
    Run MASQ on Bitcoin's Lightning Network
  • Issue#826kauri-hero2025-11-16 20:55
    HOTFIX: Adjust daemon default setup value to avoid configuration
  • Issue#818kauri-hero2025-11-02 21:03
    BREAKING-CHANGE Are Chunked Responses Being Handled Wrong?
  • Issue#683kauri-hero2025-10-05 21:22
    More Automation in Handling of Pending Payment Errors
  • Issue#793bertllll2025-09-16 10:28
    Replace the `gas-price` configurable parameter with `gas-price-margin`
  • Issue#599czarte2025-08-18 15:28
    Create command to output a visual digraph with the dot_graph module
  • Issue#684kauri-hero2025-08-17 20:48
    Error Context Column in `PENDING_PAYABLE`
  • Issue comment#599kauri-hero2025-08-17 20:45
    Create command to output a visual digraph with the dot_graph module
  • Issue#823bertllll2025-08-15 08:27
    Dev sharing: Blockchain errors
  • Issue comment#818dnwiebe2025-08-08 11:29
    Are Chunked Responses Being Handled Wrong?
  • Issue#784czarte2025-08-06 10:49
    Geo Location and Free World Bit for Exit node
  • Issue#821dnwiebe2025-07-31 02:43
    Stop Believing Liars
  • Issue#788kauri-hero2025-07-13 21:03
    Change routing_engine() to handle CountryCode and Free World Bit for Exit Node in Request for the Route
  • Issue#819dnwiebe2025-07-08 12:04
    Don't help evil Nodes so much
  • Issue#818dnwiebe2025-05-28 12:23
    Are Chunked Responses Being Handled Wrong?
  • Issue#817utkarshg62025-05-09 06:51
    Add Failed Payments Table
  • Issue comment#447kauri-hero2025-04-20 21:37
    Public Descriptor changing automatically upon reconnecting to MASQ Network
  • Issue comment#447kauri-hero2025-04-20 21:19
    Public Descriptor changing automatically upon reconnecting to MASQ Network
  • Issue comment#562dnwiebe2025-04-02 12:10
    Research Spike - identify the self-healing mechanism in Node core
  • Issue comment#683kauri-hero2025-03-30 21:24
    More Automation in Handling of Pending Payment Errors
  • Issue comment#800kauri-hero2025-03-23 21:46
    Drain the Pipeline
  • Issue comment#773bertllll2025-03-11 22:06
    Service fee market price knowledge for PaymentAdjuster
  • Issue#815kauri-hero2025-02-23 21:39
    Defend against evil UI connections
  • Issue comment#740kauri-hero2025-02-16 22:03
    Implement TTL for receivables scan, to ensure if there is no response that the next scan can occur
  • Issue comment#744kauri-hero2025-02-16 21:48
    Set `BlockchainBridge` free from blocking caused by RPC calls

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.