Lattice ECDSA attack
active 2023-08-16 → 2025-12-30 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 868 days from 2023-08-16 to 2025-12-30. Pushes: 0 total, peak 0 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 14 total, peak 2 in a day. Comments: 18 total, peak 4 in a day. Stars: 65 total, peak 5 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 |
|---|---|---|---|---|
| bitlogik | 11 | 0 | 0 | 5 |
| smartunia | 4 | 0 | 0 | 3 |
| arafatsegawa | 4 | 0 | 0 | 1 |
| antonio-fr | 3 | 0 | 0 | 3 |
| dmitriy0342 | 3 | 0 | 0 | 2 |
| bane77111 | 2 | 0 | 0 | 0 |
| iepuril1 | 1 | 0 | 0 | 1 |
| HichamINOX | 1 | 0 | 0 | 0 |
| KrashKrash | 1 | 0 | 0 | 1 |
| uith1hftkb | 1 | 0 | 0 | 1 |
| cloudnathy | 1 | 0 | 0 | 1 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#9uith1hftkb2025-12-30 20:53minimum number of signatures
- Issue comment#21KrashKrash2025-09-07 14:47known_bits and kp
- Issue#31bitlogik2025-03-18 23:01Notification
- Issue#31HichamINOX2025-03-15 18:48Notification
- Issue comment#21iepuril12025-03-01 08:03known_bits and kp
- Issue comment#30bitlogik2025-01-31 20:22Msb or lsb please help me
- Issue#30bitlogik2025-01-31 20:22Msb or lsb please help me
- Issue#29bitlogik2025-01-31 20:21kp is the **known leaked part of the internal eHello!Please explain.I have generated a dummy data file.json 1500 signatures,MSB 4 bit and inserted my Pubkey x,y and r,s there. Should I leave the hash as it is?phemeral nonce** during ECDSA. As this is supposed to be an internal secret, it can be read using a side channel. As it is a protected secret, sometimes we don't get it fully, but only a part, the starting bits, or the last bits. That's the exact purpose of LatticeAttack. If you know the no
- Issue comment#30antonio-fr2025-01-18 15:39Msb or lsb please help me
- Issue comment#30arafatsegawa2025-01-18 08:42Msb or lsb please help me
- Issue#30arafatsegawa2025-01-18 08:42Msb or lsb please help me
- Issue#30arafatsegawa2025-01-18 08:36Msb or lsb please help me
- Issue comment#30antonio-fr2025-01-16 18:22Msb or lsb please help me
- Issue#30arafatsegawa2025-01-15 00:03Msb or lsb
- Issue comment#21dmitriy03422024-11-26 08:39known_bits and kp
- Issue#29dmitriy03422024-11-23 10:25kp is the **known leaked part of the internal eHello!Please explain.I have generated a dummy data file.json 1500 signatures,MSB 4 bit and inserted my Pubkey x,y and r,s there. Should I leave the hash as it is?phemeral nonce** during ECDSA. As this is supposed to be an internal secret, it can be read using a side channel. As it is a protected secret, sometimes we don't get it fully, but only a part, the starting bits, or the last bits. That's the exact purpose of LatticeAttack. If you know the no
- Issue comment#21dmitriy03422024-11-23 08:55known_bits and kp
- Issue comment#28bitlogik2024-04-08 21:33Video example
- Issue#26bitlogik2024-04-08 21:32abdul
- Issue comment#28bitlogik2024-04-08 21:28Video example
- Issue#28bitlogik2024-04-08 21:28Video example
- Issue#28smartunia2024-04-07 17:58Video example
- Issue comment#8smartunia2024-04-07 16:02Running lattic_attack.py "private_value must be an integer type"
- Issue comment#1smartunia2024-04-07 16:01TypeError: private_value must be an integer type.
- Issue comment#8bitlogik2024-04-07 15:44Running lattic_attack.py "private_value must be an integer type"
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 65 stars here means stars gained during the window, not the repo's star count.