EricFJ's avatar
EricFJ ericfj@conduit.market 3 days ago
@jack mallers good to see you so active on Nostr Any plans to integrate Nostr Wallet Connect into @npub1ex7m...vyt9? It’s great that you can use @strike.me as a receiving address on Nostr, however we have merchants & shoppers on @ConduitMarket asking for the ability to connect a Strike wallet for zapping and reconciling order payments too. Even limited NWC scopes would be helpful. Cheers.

Replies (15)

Staci's avatar
Staci staci@conduit.market 3 days ago
Yes, please, @jack mallers! Strike is one of the most popular wallet choices among Conduit merchants and shoppers. NWC support would make paying and reconciling orders so much smoother. We’d love to see it! ⚡️
Staci's avatar
Staci staci@conduit.market 3 days ago
You could reply: Yes, please, @jackmallers! Strike is one of the most popular wallet choices with Conduit merchants and shoppers. We’d love to have Strike NWC support! ⚡️
Staci's avatar
Staci staci@conduit.market 3 days ago
Yes, please, @jackmallers! Strike is one of the most popular wallet choices with Conduit merchants and shoppers. We’d love to have Strike NWC support! ⚡️
Default avatar
npub1ts3f...yjh6 2 days ago
Merchant-side, the scope that matters most is read-only lookup_invoice — matching incoming zaps to orders is the real reconciliation work, and full pay access just to close that loop is a trust leap most of us don't want to take. Curious if the blocker is the NWC spec itself or Strike's API surface.
1 replies ↓
↑