Avatar
Ethan Tuttle
5ec98673feecaa935c81450169221259a2f132634e7891a0c537dcb63ef3cfb1
professional ehash shill shill pioneer

https://github.com/fedimint/fedimint/pull/3583

Want to use FROST to do nostr things? Try it out with the nostrmint module. Technical skills needed to get up and running.

This is decentralization but rather redundancy. And yes, this is the fedimint model. There are multiple servers running fedimint and coordinating with each other to keep the mint "alive".

@npub15hvkk66pfgffwklusrexwgwgq5c8prlwqputh9gwcsv27jfmdxzsa6gjgu

FEDIMINT'S CAN HELP WITH INITIAL MICROPAYMENTS BEFORE THE SATS AMOUNT REACHES ECONOMIC REASONABILITY FOR LN FEES.

https://github.com/MutinyWallet/mutiny-node/tree/fedimint

MUTINY EXPERIMENTED WITH THIS IDEA. TBD IF IT WORKS OUT THAT WAY.

Any good diagram on how FROST would work? Like a flow chart one?

Fedimint is a federation ecash system (and can be much more since it's modular). Cashu is a non-federated ecash system. Both take in bitcoin and issue ecash notes. These ecash notes are 1:1 IOUs for bitcoin but use blinded signatures by the mint to preserve privacy. They also use LN for interoperability between other bitcoin projects/wallets/etc.

happy to go further if this wasn't detailed enough.

also check out https://fedimint.org

It shoudl "just work". Fedimint uses LN nodes are liquidity between each federation and the general LN network. Or you could redeem for on-chain from Bob's mint. This is one part of the UX that is being explored and actively discussed/developed. There's really only one mature client app for fedimint and that's Fedi. I don't have insight into how they do things exactly.

Fedimint uses something called a LN gateway. This is a LN node operator that runs a specific plugin/daemon alongside their node and can offer their liquidity to the fedimint. They're essentially a specialized client of the federation that deals in ecash<->LN contracts. If a LN invoice is given for internal to the mint, it just settles out ecash and the LN isn't touched.

I can get a bit more technical if you're LN tech savvy. or join the Discord and pop into #lightning to chat (chat.fedimint.org)

No worries! imho, the naming was an interesting choice. But there's something to branding for easy mental mapping that can be respected.

Yup! I've had the pleasure to meet Obi. Awesome dude. I've gave that one a listen.

Check out https://www.fedi.xyz/builders

They're a company running fedimint things and help on the protocol. Otherwise, it's really just technical people experimenting and iterating on this new and emerging protocol/tech.

> My most pressing question is what is being done to help educate new users about what these technologies do and how to use them safely?

This note. 😅 But seriously, it's one of my longer term goals is educating people on the topic and generally being a "developer advocate" aka professional tech shill. There's not a lot of content out there focused on it... yet. There's https://fedimint.org and https://cashu.space/ available for consumption and several podcasts on the topic. But as with anything bitcoin, there should be more podcasts.

> That’s a lot!

Definitely, that's why both ecash implementations have opted to do invoicing like lightning for payments and such. You can still dump `cashu...` notes everywhere but otherwise it can be just lightning style payments/interactions. nostr:nprofile1qqsxn2q9vlnek6umcu5z44v42yklpwqy0prpd0kmvg7pytadgg9zvdgpz3mhxue69uhkummnw3ezummcw3ezuer9wcq3gamnwvaz7tmjv4kxz7fwv3sk6atn9e5k7qgawaehxw309ahx7um5wgkhqatz9emk2mrvdaexgetj9ehx2aqln2edj is doing big things on this front and with nostr.

1. because you want ecash? it's offline capabale. the data is the asset. You can receive it on a piece of paper. you don't want to manage liquidity. you don't want the latency of VPN/TOR. you have a service where you already custody users funds and want to provide a different privacy trade off.