Runes: terrible idea or idée terrible?
active 2023-09-27 → 2024-11-30 (UTC)
Partial coverage20,547 / 26,300 hourly files (78%) · 2 absent upstream · 5,750 failed, retryable2023-08-15 → 2026-08-14 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
862
Pushes
15
Pull requests
18
Issues
298
Stars
163
Forks
23
Activity over time
Daily event counts in the loaded window
Line chart, 431 days from 2023-09-27 to 2024-11-30. Pushes: 15 total, peak 6 in a day. Pull requests: 18 total, peak 6 in a day. Issues: 298 total, peak 18 in a day. Comments: 332 total, peak 43 in a day. Stars: 163 total, peak 37 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| casey | 426 | 15 | 15 | 143 |
| summraznboi | 46 | 0 | 0 | 41 |
| Psifour | 31 | 0 | 0 | 19 |
| sondotpin | 25 | 0 | 0 | 16 |
| stet | 15 | 0 | 0 | 14 |
| raphjaph | 11 | 0 | 0 | 7 |
| owenstrevor | 10 | 0 | 0 | 7 |
| cliobitcoinbank | 9 | 0 | 0 | 9 |
| lugondev | 7 | 0 | 0 | 6 |
| elocremarc | 5 | 0 | 0 | 4 |
| jerryfane | 4 | 0 | 0 | 4 |
| 0xbrito | 4 | 0 | 0 | 1 |
| devords | 4 | 0 | 0 | 4 |
| utxo-detective | 3 | 0 | 0 | 2 |
| winktool | 3 | 0 | 0 | 3 |
| afeezaziz | 3 | 0 | 0 | 3 |
| HubertusVIE | 3 | 0 | 0 | 3 |
| YuurinBee | 2 | 0 | 1 | 1 |
| wanyvic | 2 | 0 | 0 | 2 |
| revofusion | 2 | 0 | 0 | 2 |
Recent activity
Latest issues, pull requests and releases
- Issue#104raphjaph2024-04-13 21:58Look up runes by number
- Issue#174raphjaph2024-04-12 20:53Add runes link to nav bar
- Issue#188raphjaph2024-04-12 20:53Allow cancelling and resuming etching
- Issue comment#217wanyvic2024-04-11 06:08Using commit_tx.confirmations to determine the validity of etching runes can lead to inconsistent judgments on the validity of runes during node operations
- Issue comment#217casey2024-04-11 04:50Using commit_tx.confirmations to determine the validity of etching runes can lead to inconsistent judgments on the validity of runes during node operations
- Issue comment#217wanyvic2024-04-11 04:45Using commit_tx.confirmations to determine the validity of etching runes can lead to inconsistent judgments on the validity of runes during node operations
- Issue comment#217casey2024-04-08 04:39Using commit_tx.confirmations to determine the validity of etching runes can lead to inconsistent judgments on the validity of runes during node operations
- Issue#217alexha1231232024-04-08 02:51Using commit_tx.confirmations to determine the validity of etching runes can lead to inconsistent judgments on the validity of runes during node operations
- Issue#216sondotpin2024-04-04 06:09Etch Rune with cenotaph should be store in reserved
- Issue#216sondotpin2024-04-04 05:42Etch Rune with cenotaph should be store in reserved
- Issue comment#104lugondev2024-04-02 04:33Look up runes by number
- Issue#171casey2024-03-31 20:30Reset Signet & Testnet indexer
- Issue#160casey2024-03-31 19:05Genesis runes
- Issue#205casey2024-03-31 19:01Use checked adds for rune arithmatic in updater
- Issue#201casey2024-03-31 00:19Test that minting a rune in a cenotaph still records the mint
- Issue#195casey2024-03-30 23:51When etching, set default output to premine change output
- Issue#178casey2024-03-30 23:49Add a test for pushnum in runestone
- Issue#200casey2024-03-30 05:56Test that etching a reserved run in a cenotaph still reserves that rune
- Issue#211casey2024-03-30 01:48See what test coverage is like
- Issue#192casey2024-03-30 00:43use a relative locktime to prevent reveal transaction from being mined prematurely
- Issue#164casey2024-03-29 22:51Add runestone round-trip encipher and decipher tests
- Issue#57casey2024-03-29 02:38Documentation
- Issue#82casey2024-03-29 02:37Host spaces about runes
- Issue#82casey2024-03-29 02:37Host spaces about runes
- Issue#170casey2024-03-29 02:36Test etching rune with commit before activation height
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 163 stars here means stars gained during the window, not the repo's star count.