Thread

Zero-JS Hypermedia Browser

Relays: 5
Replies: 2
Generated: 04:24:55
The past year on the road, merchant adoption has been a priority for us. Why? They are the key to network effects for acceptance/payments. We’ve been talking about a maturity model and finally put it on paper last night. Here is v1 based on our interactions with merchants and our bitcoin preferred juice shop in Uganda. Would appreciate your feedback/comments on this. We see the maturity of a merchant in three levels based on how money is used. Level 1: SoV OR MoE (merchant onboards with either user case based on their need/pain) Level 2: SoV & MoE Level 3: SoV & MoE & UoA There is maturity within each use case (ie SoV: storing in exchange vs cold storage). We’re weak on the UoA use case so if you have experience with merchants pricing in sats, would love your thoughts! We’re hoping to continue flushing this out to create more collateral to help further merchant adoption. image
2024-08-28 08:23:27 from 1 relay(s) 1 replies ↓
Login to reply

Replies (2)

Just close the circle: 1. accepting payments => btc pay server, they can connect to your umbrel or other OS, can set up lighting also with breez 2. Hot wallet connected to Node = they can use your node for privacy 3. Cold wallet multisig, offline pc with tails os for electrum, or ubuntu and sparrow, and then use jade diy and/or blue wallet on phone cold wallet multisig and/or other diy solutions such as trezor diy 4. Exchanges, depending on your location 5. P2p exchanges such as bisq or in person groups
2024-08-30 18:49:07 from 1 relay(s) ↑ Parent 1 replies ↓ Reply