joinstrvspublic-pool
Two self-hosted Cryptocurrency projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| joinstr | public-pool | |
|---|---|---|
| Score | 53/100 | 44/100 |
| Rank in category | #24 of 44 in Cryptocurrency | #35 of 44 in Cryptocurrency |
| GitHub stars | — | 452 |
| Stars, last 30 days | — | +1 |
| Stable releases, 12 months | 0 | 0 |
| Latest release | — | — |
| Setup | Advanced | Moderate |
| Official Docker image | No | No |
| License | mit | GPL-3.0 |
| Main language | — | Typescript |
Which one should you pick?
joinstr scores 53/100 against 44/100 for public-pool, so it is the safer default.
If you want the quickest setup, public-pool is easier to run; joinstr needs more configuration.
public-pool is growing faster right now (+1 stars in 30 days).
Key differences
- License: joinstr is mit, public-pool is GPL-3.0.
- Platforms only joinstr lists: Build from Source, Docker, Umbrel.
- Platforms only public-pool lists: NPM.
- Features only joinstr lists: CLI Client, Custom pool denomination and peer count, Hardware / air-gapped signing, Nostr relay coordination and 6 more.
- Features only public-pool lists: Bitcoin stratum mining server, Mainnet and testnet support, Per-worker connection limits, PM2 cluster-mode scaling.
joinstr details →public-pool details →All Cryptocurrency projects →
Swap a project
Keep joinstr, compare it with
Keep public-pool, compare it with