Zappool status update:
- The 60ksat giveaway was completed all right! It hasn't made a huge splash, but it got user interaction and many re-posts, and at least few users joined because of it.
- The hashrate is currently quite steady, at 35TH (on weekly, daily and hourly view as well)
- There was an issue affecting one user, sorted out (it was a DB issue following some changes, due to stale account handling)
- Ocean hashrate went down recently, and right now there were no blocks found in over 99 hours! Not to worry about, just mentioning.
- The lightning node reliability is acceptable, but not perfect. The payment from Ocean fails occasionally, and outgoing payments also fail sometimes (routing error), but succeed after a few automatic retries. Occasionally the invoice can't be obtained from the LN address/wallet provider, but that's an external issue.
Hashing forward!
Zappool
npub17q…akg7l
2026-02-03 12:18:45 UTC
Author Public Key
npub17qt0gf99uxe3n3aa8nj93hspe0x3vfn7wwmv42adfc96y8g8ngcqpakg7lPublished at
2026-02-03 12:18:45 UTCEvent JSON
{
"id": "8c9eb69067fa03b0f105f0104c2a41992e977132b55d2a771164a989f569bb07",
"pubkey": "f016f424a5e1b319c7bd3ce458de01cbcd16267e73b6caabad4e0ba21d079a30",
"created_at": 1770121125,
"kind": 1,
"tags": [],
"content": "Zappool status update:\n\n- The 60ksat giveaway was completed all right! It hasn't made a huge splash, but it got user interaction and many re-posts, and at least few users joined because of it.\n- The hashrate is currently quite steady, at 35TH (on weekly, daily and hourly view as well)\n- There was an issue affecting one user, sorted out (it was a DB issue following some changes, due to stale account handling)\n- Ocean hashrate went down recently, and right now there were no blocks found in over 99 hours! Not to worry about, just mentioning.\n- The lightning node reliability is acceptable, but not perfect. The payment from Ocean fails occasionally, and outgoing payments also fail sometimes (routing error), but succeed after a few automatic retries. Occasionally the invoice can't be obtained from the LN address/wallet provider, but that's an external issue.\n\nHashing forward!",
"sig": "71e37764ac0a29e0faefe46325efb4f5c423a901604b3834f45d212017cddb50973155a73909448bf0eb2a601416abec82f3fb69cc3a56a903c56349f3a8f560"
}