Thread

Zero-JS Hypermedia Browser

Relays: 5
Replies: 11
Generated: 07:25:49
A solo mining pool is basically stateless (it just provides a work based on a template, and hasta la vista). A proxy pool, and a regular pool, has a lot of state: it has to remember all unpaid work shares, rewards, payments, etc. So a proxy pool implementation is more complex than a solo pool implementation. Zappool is a proxy pool 😎 #zappool #proxy-pool
2025-11-11 14:08:21 from 1 relay(s) 2 replies ↓
Login to reply

Replies (11)

Well, indirecly. I've learnt about the #hashpool project of nostr:nprofile1qqsdxpfv503a2ga3ajqxw843hws9z7302ghpj4mcmjpa6qagmp9pwrs8222jg , and I saw two avenues: 1. build a new pool from scratch, starting with small hashrates (=very long times for finding a block), and bridge the long times with a local market for hash-ehash (custodial but blinded, option to early exit via market) 2. a proxy pool, based on Ocean, with periodic payouts from Ocean. But then I realized that in this case there is not really a need for a hash market, nor for ecash in fact. I chose to pursue 2, and pivoted my focus to a proxy pool, which is old-style custodial, but only for a day (and small user amounts). I realized there is a lot of synergy with Nostr, so I focus on that now with Zappool. For home miners, zapping away is a perfect and fun usecase for the the small daily payouts. Miner ID being a Nostr ID also opens up some possibilites -- payout to LN address of the npub, payout as zap, donation to someone else's npub, payout as nutzap, nostr login to your bitaxe, etc. In the long term I keep in mind hashpool as something interesting for miner decentralization. For now I want to push the Nostr-bitaxe synergy, and the proxy pool concept (I'm not aware of a working proxy pool). #hashpool #proxy-pool #zappool
2025-11-11 15:35:53 from 1 relay(s) ↑ Parent 2 replies ↓ Reply