You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A cashu mint extension linked to the Alby Hub backend node. An "uncle Jim" should have also this option in his Alby Hub, it is very useful in very specific cases. A simple mint management, like it was used on LNbits + some other admin basic features.
Use case scenario
Nowadays the cubans are struggling to use Bitcoin on their remote isolated island. Their internet conditions are very harsh and limited.
They have daily blackouts and internet can be used with Bitcoin only behind Tor. That makes extremely difficult for them to run nodes, especially mobile ones like Zeus, Blixt, Breez etc.
Also they are mostly poor users where each sat is very valuable, so managing large LN channels is quite costly for them. Even using Phoenix mobile wallet is costly for them, due to splicing fees.
My proposal for cuban users
I proposed them to run a community Alby Hub with "uncle Jim" sub-accounts, for easy transacting using Alby Go.
This central node will have a good liquidity for the entire community and will maintain a correct connection, even behind Tor. Is not really necessary to be a public node, can ba a private one, running with few good channels to the exterior using some well known LSPs.
But then come the problem of the blackouts. So between them cannot transact if there's no electricity.
Here comes cashu, that can be used offline and when the power comes back, they can update their balances.
This will help cubans to create a circular economy using the cashu tokens and if they want to transact with external world, the tokens are converted automatically in sats.
My proposal to Alby team
Add a cahu mint into Alby Hub with basic features to manage it and maybe monitor the issuance of all tokens (if is possible).
Add a feature in AlbyGo to support such mints. If not, they can use Minibits or eNuts or cashu.me app for that. But will be nice to have all in Alby, like a package.
The text was updated successfully, but these errors were encountered:
Description
A cashu mint extension linked to the Alby Hub backend node. An "uncle Jim" should have also this option in his Alby Hub, it is very useful in very specific cases. A simple mint management, like it was used on LNbits + some other admin basic features.
Use case scenario
Nowadays the cubans are struggling to use Bitcoin on their remote isolated island. Their internet conditions are very harsh and limited.
They have daily blackouts and internet can be used with Bitcoin only behind Tor. That makes extremely difficult for them to run nodes, especially mobile ones like Zeus, Blixt, Breez etc.
Also they are mostly poor users where each sat is very valuable, so managing large LN channels is quite costly for them. Even using Phoenix mobile wallet is costly for them, due to splicing fees.
My proposal for cuban users
I proposed them to run a community Alby Hub with "uncle Jim" sub-accounts, for easy transacting using Alby Go.
This central node will have a good liquidity for the entire community and will maintain a correct connection, even behind Tor. Is not really necessary to be a public node, can ba a private one, running with few good channels to the exterior using some well known LSPs.
But then come the problem of the blackouts. So between them cannot transact if there's no electricity.
Here comes cashu, that can be used offline and when the power comes back, they can update their balances.
This will help cubans to create a circular economy using the cashu tokens and if they want to transact with external world, the tokens are converted automatically in sats.
My proposal to Alby team
Add a cahu mint into Alby Hub with basic features to manage it and maybe monitor the issuance of all tokens (if is possible).
Add a feature in AlbyGo to support such mints. If not, they can use Minibits or eNuts or cashu.me app for that. But will be nice to have all in Alby, like a package.
The text was updated successfully, but these errors were encountered: