active 2024-08-16 → 2025-07-31 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 350 days from 2024-08-16 to 2025-07-31. Pushes: 0 total, peak 0 in a day. Pull requests: 1 total, peak 1 in a day. Issues: 4 total, peak 2 in a day. Comments: 13 total, peak 2 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
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| fleupold | 7 | 0 | 0 | 5 |
| cankisagun | 3 | 0 | 0 | 3 |
| acanidio-econ | 2 | 0 | 0 | 2 |
| sambacha | 1 | 0 | 0 | 1 |
| cmagan | 1 | 0 | 0 | 1 |
| sunce86 | 1 | 0 | 0 | 0 |
| mfw78 | 1 | 0 | 0 | 1 |
| MartinquaXD | 1 | 0 | 0 | 0 |
| avivkeller | 1 | 0 | 1 | 0 |
Recent activity
Latest issues, pull requests and releases
- Pull request#23avivkeller2025-07-31 14:34
- Issue comment#17cankisagun2025-01-16 19:12research: single cross-chain mechanism
- Issue comment#17fleupold2025-01-13 13:07research: single cross-chain mechanism
- Issue comment#17cankisagun2025-01-10 12:28research: single cross-chain mechanism
- Issue comment#17fleupold2025-01-08 16:41research: single cross-chain mechanism
- Issue comment#17acanidio-econ2025-01-06 09:43research: single cross-chain mechanism
- Issue comment#17acanidio-econ2025-01-06 08:50research: single cross-chain mechanism
- Issue comment#17fleupold2025-01-02 18:00research: single cross-chain mechanism
- Issue comment#22fleupold2025-01-02 16:24research: Introduce the option to define conditions on order that require participation of a specific solver or a threshold of solvers that participated in the auction
- Issue comment#22cmagan2024-12-06 12:40research: Introduce the option to define conditions on order that require participation of a specific solver or a threshold of solvers that participated in the auction
- Issue comment#22mfw782024-12-06 11:53research: Introduce the option to define conditions on order that require participation of a specific solver or a threshold of solvers that participated in the auction
- Issue comment#22fleupold2024-12-04 12:08research: Introduce the option to define conditions on order that require participation of a specific solver or a threshold of solvers that participated in the auction
- Issue comment#21sambacha2024-11-25 12:23research: Use MEV Blocker to decentralize solver bidding
- Issue#21fleupold2024-10-30 13:10research: Use MEV Blocker to decentralize solver bidding
- Issue#20fleupold2024-10-30 10:39research: Use blobs for decentralised order posting
- Issue comment#17cankisagun2024-09-18 16:42research: single cross-chain mechanism
- Issue#19MartinquaXD2024-08-23 07:49research: Simplify handling of surplus fees
- Issue#18sunce862024-08-21 08:05research(contracts): auction_id as part of the settlement contract
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.