Why can't ecash be for payments? I personally wouldn't want large amounts of long-lived amounts stored in a fedimint. The former reducing overall rug risk and the latter reduces the chance of inflationary practices (aside from running a client that validates the version of fedimint run by guardians).
Fedimint doesn't explicitly have to be a "bank", although, admittedly, that's been a advertised use case from louder voices than mine own.
Laying out an example:
I'm visiting LA. I somewhat know people in the area, maybe I'm visiting them. There's a smaller network of merchants that participate in a fedimint. Similar to handling cash, they don't keep large amounts in the drawer (in the fedimint). Just enough to do business of the day. When i arrive, I can peg-in (on-chain or with LN) to the fedimint and now have ecash to spend. Each merchant and myself don't have to mange LN nodes and the complexity inherent to it.
Another:
Remove the ecash/BTC/LN modules and insert a password manger or any other arbitrary data. Since the data is validated via consensus among fedimint nodes, the risk and access is distributed. It enables the syncing and validity across disaggregate nodes.
I personally would love to auto-sync my bitwarden instance between home and office servers. I understand there are solutions to that with some automation, but fedimint could offer this out of the box for the less technically inclined.
Myriad of solutions and fedimint could be one. Definitely not the end all be all, but i have to pick something to focus on with my limited time. 🫠
EthanTuttle / Ethan Tuttle
npub1tm…7el78
2023-10-06 19:22:16
in reply to nevent1q…t5qz
Author Public Key
npub1tmycvul7aj4fxhypg5qkjgsjtx30zvnrfeufrgx9xlwtv0hne7cs67el78Published at
2023-10-06 19:22:16Event JSON
{
"id": "8abb0b5be2404e92ffa82481d08be3a3a1c7c0577906a130b0883f0601a33cac",
"pubkey": "5ec98673feecaa935c81450169221259a2f132634e7891a0c537dcb63ef3cfb1",
"created_at": 1696612936,
"kind": 1,
"tags": [
[
"p",
"e6ce6154325b54e69c9478c46cf1284e093f790e658b6a70f9df6eed275e3444",
"wss://nostr.zebedee.cloud",
"noKYC ⚡︎"
],
[
"p",
"77953b3a63bcf1c748dbdeef109bd56de48c30edcd27d2092440c3adca31c975",
"wss://nostr.zebedee.cloud",
"Cyber Seagull"
],
[
"p",
"4ffc11bfa2f8516ae8bc7c6bf82275d358e47045446250be2d0e5612e2140828",
"wss://nostr.zebedee.cloud",
"Sovereign Matt"
],
[
"p",
"2590201e2919a8aa6568c88900192aa54ef00e6c0974a5b0432f52614a841ec8",
"wss://nostr.zebedee.cloud",
"j"
],
[
"e",
"f0ac94de513ff050398430fc8e5f55cdfb0ccda354b7602efc9be025205e3374",
"",
"root"
],
[
"e",
"682c16457fd165c74e0c8e3ada919a3fe959a4a7ef80a633932bb028146ab6e3"
],
[
"e",
"ed55099e78eeaf6c8be9c27a50277ad3146db13bee33e985e0245fbad3d3e844"
],
[
"e",
"ae02adbd37e7a5cb2e812be0b5a7f8be99ad3ceced01b2b0059e94474f5ad65f"
],
[
"e",
"f1b2fd4b0458659b5c5746aa410940f0d57f7afd0e0234e7e6defb82f7cacdf2"
],
[
"e",
"5dc732d576dc4186d3a10363843642d8b407705909d296c3f8c80d3280ef193d"
],
[
"e",
"3897fcf2bb664b6669842ffa371867910aeca671da1995b1d35561b509bfd89a"
],
[
"e",
"23dc6af9bd97d6dbdb56d5bd2a20433259b31ae4ae8f5a9e340239509470ff82"
],
[
"e",
"8b1d7ee70fb2fd9fd11b6cdb35d9e9a11e0d4a74c8df124c6dc6560357fe5232"
],
[
"e",
"fe76215993e8d4fa8ef3d06a60789f856c9828fe3a0465987cc2dce44516b553",
""
],
[
"e",
"77f096ce9d59031e1e0d712c404dfb0d63ab86e0efafd94cf7b07355b8f6a78d",
"wss://relay.damus.io",
"reply"
]
],
"content": "Why can't ecash be for payments? I personally wouldn't want large amounts of long-lived amounts stored in a fedimint. The former reducing overall rug risk and the latter reduces the chance of inflationary practices (aside from running a client that validates the version of fedimint run by guardians).\n\nFedimint doesn't explicitly have to be a \"bank\", although, admittedly, that's been a advertised use case from louder voices than mine own.\n\nLaying out an example:\nI'm visiting LA. I somewhat know people in the area, maybe I'm visiting them. There's a smaller network of merchants that participate in a fedimint. Similar to handling cash, they don't keep large amounts in the drawer (in the fedimint). Just enough to do business of the day. When i arrive, I can peg-in (on-chain or with LN) to the fedimint and now have ecash to spend. Each merchant and myself don't have to mange LN nodes and the complexity inherent to it.\n\nAnother:\nRemove the ecash/BTC/LN modules and insert a password manger or any other arbitrary data. Since the data is validated via consensus among fedimint nodes, the risk and access is distributed. It enables the syncing and validity across disaggregate nodes. \n\nI personally would love to auto-sync my bitwarden instance between home and office servers. I understand there are solutions to that with some automation, but fedimint could offer this out of the box for the less technically inclined.\n\nMyriad of solutions and fedimint could be one. Definitely not the end all be all, but i have to pick something to focus on with my limited time. 🫠",
"sig": "50611f4af01e3a2e0b5683736d1f4ae13ba07f077182802b7db6ab6bb5914ed20d0a9c8c76df65b36dbfa8efa36da1e309e51dc7c844f48d932a3e2d32399409"
}