Profile: 60822084...

btcmap.org is awesome! I am not sure how up to date their square bitcoin merchant map will be though. I am guessing the map on CashApp is created directly from data on merchants turning on the accept bitcoin toggle in square.

I think some merchants may turn on the accept bitcoin option and not know about btcmap.org. I want to shop with them ( and maybe list them on btcmap.org while I am at it).

The problem I see with this design is that the server has to do L1 transaction + commit to locking funds up for possible time period without assurance from user that they will pay lightning invoice. I may be misunderstanding.

These problems could be mitigated with a fee that has to be played before the L1 transaction but I would like to hear your ideas for mitigation nostr:nprofile1qqszrqlfgavys8g0zf8mmy79dn92ghn723wwawx49py0nqjn7jtmjagppemhxue69uhkummn9ekx7mp0qy08wumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wshsud80st

Thanks! Very interesting idea!

I agree! Optionality is the way! (I don't like bip 177)

The gateways are separate from guardians. I believe the guardians must approve the gateways for their federation but anyone can run a gateway. The gateways are coded in such a way where the guardians and users never have custodial risk with the gateway.

I've learned a lot about fedimint from this guide: https://fedimint.org/docs/intro

I am very excited for this. I believe the settlement time for this transaction could be very low.

1: NFC to move ecash tokens to merchant device

2a: if merchant trust mint, reissue ecash to themselves.

2b: if merchant does not trust mint, sweep with lightning to themselves.

The case for 2b is a little more complicated because the sweep would incur fees that the merchant may want to charge the customer for.

Overall though this seems like a super good payments flow, I love it!