{"type":"rich","version":"1.0","author_name":"Rizful.com (npub1jl…pp2kq)","author_url":"https://nostr.ae/npub1jluy3twvf338v6zlujzzdhjkzjy8ezj34ksydr8vw8a6jwp89ygshpp2kq","provider_name":"njump","provider_url":"https://nostr.ae","html":"Note for users of the new Primal wallet:  The new wallet denoted as \"self-custodial\" by Primal uses Spark.\n\nSpark is an API provided by the Los Angeles company LightSpark. ( https://www.lightspark.com/ ) \n\nLightSpark is a competitor to Megalith \u0026 Rizful, so we're generally committed to keeping our mouth shut with regard to LightSpark's overall merits.\n\nBut: everyone should know that LightSpark payments over the Lightning network can have significant LATENCY...... \n\nLightSpark is doing quite a lot of complicated stuff \"on top\" of the Lightning network.  \n\nIf, for example, you were using the previous Primal wallet (provided by Strike), you might have been able to zap a user and get a confirmation of successful zap within 1 to 2 seconds. Using LightSpark's API,  by contrast, our tests indicate that a zap confirmation can take upwards of 10 seconds. (TEN SECONDS!)\n\nWe're bringing this up because we're seeing a lot of \"I can't zap\" complaints recently. \n\nIf you're having problems, check your lightning address service -- if it's run by LightSpark -- in this includes many wallets marketed as \"self-custodial\", such as Breez, Wallet Of Satoshi, Primal, and others.... it might be that you CAN zap and zaps DO work, but that you're just not used to waiting 10 seconds for a confirmation, so you're giving up and closing out of the zap attempt early...."}