Python bitcoin library
active 2023-11-02 → 2026-05-25 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 936 days from 2023-11-02 to 2026-05-25. Pushes: 7 total, peak 2 in a day. Pull requests: 2 total, peak 1 in a day. Issues: 26 total, peak 4 in a day. Comments: 29 total, peak 9 in a day. Stars: 10 total, peak 1 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
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| 4tochka | 9 | 0 | 0 | 5 |
| madnadyka | 7 | 7 | 0 | 0 |
| Yatishs03 | 6 | 0 | 0 | 4 |
| roshyvasanth | 5 | 0 | 0 | 5 |
| Coolgamerburst | 4 | 0 | 0 | 1 |
| Nyx38 | 4 | 0 | 0 | 2 |
| emmanueloshin | 2 | 0 | 0 | 2 |
| MrSadanandKunar | 2 | 0 | 0 | 2 |
| Msmcloud9bm | 2 | 0 | 0 | 2 |
| K1LL3RC0D3 | 2 | 0 | 0 | 1 |
| angus14 | 2 | 0 | 0 | 1 |
| JReeza | 2 | 0 | 0 | 1 |
| Segalanya-bit | 1 | 0 | 0 | 0 |
| goodlookingull-stack | 1 | 0 | 1 | 0 |
| Corruptedsonic | 1 | 0 | 0 | 0 |
| MrSadanandKumar | 1 | 0 | 0 | 0 |
| jafar1524 | 1 | 0 | 0 | 0 |
| antvpk | 1 | 0 | 0 | 0 |
| iguha0 | 1 | 0 | 0 | 1 |
| likme | 1 | 0 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
- Issue#79antvpk2026-05-25 09:037 Novel Vulnerabilities in shamir.py — Static Analysis Report
- Issue comment#43MrSadanandKunar2026-04-16 02:18Critical Vulnerability in SSSS Implementation: Missing Prime Modulus and Use of Non-Prime Modulus (2²⁵⁶)** ---
- Issue#76Nyx382026-04-12 09:57Vulnerability Report: Entropy Threshold Risks in SSS Implementation
- Issue#72likme2026-02-26 22:38Restore succeeds with fewer shares than configured threshold
- Pull request#71Dargon7892026-02-21 02:18
- Issue comment#48moetneos-maker2026-01-19 08:39Bug report
- Pull request#66goodlookingull-stack2026-01-15 01:11
- Issue#65Petah04112025-12-13 02:08Design Flaw: Per-Byte Shamir Splitting of BIP-39 Mnemonics Causes Entropy Collapse and Non-Unique Reconstruction
- Issue#64BTRMMD2025-12-07 02:57*Title*: `Exploring Shamir (3-of-5) with 2 Shares - ZeroNights X Bounty` - *Body*: Hi @bitaps-com team, exploring PyBTC for the ZeroNights X bounty. Given 2/3 shares: - Share 1: `session cigar grape merry useful churn fatal thought very any arm unaware` - Share 2: `clock fresh security field caution effort gorilla speed plastic common tomato echo` Tested `recover_secret`, no critical flaws yet. Suggestions: sanitize logs, test edge cases, document partial-share handling. Goal: break the
- Issue#63bakaxbaka2025-11-30 22:49Coefficient-Correlation Weakness in pybtc-legacy Shamir Implementation
- Issue#62Corruptedsonic2025-11-15 14:07Critical Security Vulnerabilities Identified in pybtc (Entropy, Shamir, Crypto Failures)
- Issue#60Nyx382025-10-16 19:37Security Report — Bitaps pybtc Shamir Secret Sharing (SSS) Issue
- Issue#59joseHbernardino2025-09-22 12:08Threshold Bypass in Shamir Secret Backup Scheme: Full Mnemonic Recovery With Only 2 Shares (Intended 3-of-5)
- Issue comment#42Nyx382025-09-08 00:31Shamir's secret sharing and security vulnerabilities
- Issue comment#42iguha02025-09-05 21:36Shamir's secret sharing and security vulnerabilities
- Issue comment#57angus142025-08-19 12:56Shamir SSSS: enforce non-zero leading coefficient & require CSPRNG (prevents 2-share byte leaks)
- Issue#56angus142025-08-08 16:57Vulnerabilities
- Issue comment#55Vykkinko2025-08-05 16:49[BUG] Static Share Index Predictability Weakens Shamir SSS Security (Potential Brute-force)
- Issue comment#53roshyvasanth2025-07-13 17:041 BTC Bug: 2 Share Recovery via deterministic x-values in Shamir Scheme
- Issue comment#53roshyvasanth2025-07-13 17:011 BTC Bug: 2 Share Recovery via deterministic x-values in Shamir Scheme
- Issue comment#53Yatishs032025-07-13 11:371 BTC Bug: 2 Share Recovery via deterministic x-values in Shamir Scheme
- Issue comment#53roshyvasanth2025-07-13 10:211 BTC Bug: 2 Share Recovery via deterministic x-values in Shamir Scheme
- Issue comment#53Yatishs032025-07-13 10:181 BTC Bug: 2 Share Recovery via deterministic x-values in Shamir Scheme
- Issue comment#53roshyvasanth2025-07-13 08:391 BTC Bug: 2 Share Recovery via deterministic x-values in Shamir Scheme
- Issue comment#53Yatishs032025-07-13 08:101 BTC Bug: 2 Share Recovery via deterministic x-values in Shamir Scheme
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 10 stars here means stars gained during the window, not the repo's star count.