Hashpool is interesting for different reasons but what's incredibly cool is the ability to audit the pool's liabilities – unlike with any other Bitcoin mining pool.
Assets are easy to verify: the block reward. But how to check if the pool isn't skimming some sats off the top?
This problem is called proof of liabilities (POL). Since Hashpool issues mining rewards (or hash rate futures) as ecash, we can use Cashu's POL to verify that the pool operates honestly.
The challenge with POLs is that they work best if almost every user does the check. With normal wallets it's not that easy: users often don't open their wallets for long periods of time. Some just disappear forever etc.
With Hashpool, you can pretty much guarantee that most users will be perpetually online and this will run the POL verification automatically.
Cashu's POL relies on the idea of keyset epochs, essentially simulated bank runs that force the mint to show their hand. In a wallet system, epochs are maybe rotated every month or less.
With Hashpool, you could rotate much more frequently, maybe even for every block. This makes detecting fraudulent behaviour of the mint much more likely.
Users would be able to catch a cheating pool and prove it, allowing others to make informed decisions (to shame the operator and) to look for another pool to point their hash rate to.
Very excited to see how ecash can help improve Bitcoin — usually it's the other way round.
Ecash is also used in Wabisabi coinjoins due to its privacy properties which we haven't even touched on here (also improves Hashpool).
I'm sure there's more to discover along the way!
calle
npub12r…485vg
2025-06-11 21:40:26
Author Public Key
npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vgPublished at
2025-06-11 21:40:26Event JSON
{
"id": "6c766a879f3df0291b7a96aa13f7a9bc3939eb84d243fac9ccefbfca7928990d",
"pubkey": "50d94fc2d8580c682b071a542f8b1e31a200b0508bab95a33bef0855df281d63",
"created_at": 1749678026,
"kind": 1,
"tags": [],
"content": "Hashpool is interesting for different reasons but what's incredibly cool is the ability to audit the pool's liabilities – unlike with any other Bitcoin mining pool.\n\nAssets are easy to verify: the block reward. But how to check if the pool isn't skimming some sats off the top?\n\nThis problem is called proof of liabilities (POL). Since Hashpool issues mining rewards (or hash rate futures) as ecash, we can use Cashu's POL to verify that the pool operates honestly.\n\nThe challenge with POLs is that they work best if almost every user does the check. With normal wallets it's not that easy: users often don't open their wallets for long periods of time. Some just disappear forever etc. \n\nWith Hashpool, you can pretty much guarantee that most users will be perpetually online and this will run the POL verification automatically.\n\nCashu's POL relies on the idea of keyset epochs, essentially simulated bank runs that force the mint to show their hand. In a wallet system, epochs are maybe rotated every month or less.\n\nWith Hashpool, you could rotate much more frequently, maybe even for every block. This makes detecting fraudulent behaviour of the mint much more likely. \n\nUsers would be able to catch a cheating pool and prove it, allowing others to make informed decisions (to shame the operator and) to look for another pool to point their hash rate to.\n\nVery excited to see how ecash can help improve Bitcoin — usually it's the other way round. \n\nEcash is also used in Wabisabi coinjoins due to its privacy properties which we haven't even touched on here (also improves Hashpool).\n\nI'm sure there's more to discover along the way!\n\n",
"sig": "a5019daa5c6d5e10592e5bbbee097e5dd0871e2ba840955681be9710210d08cb0ded5e69a68c3734e0e4427b359eba7f407e44f8aa772f3ce23ff8a76f021ff7"
}