#nostr algorithms creating an arvin cluster on my feed nostr:npub12zkknmund6ynu2yaptqamn0q29uje7ms3mqq6uu05v9d7t6tguyqcsaz8h

😂😂 who's in charge of this thing!
Any plans to pass an ecash note string in directly to redeem soon?
Just claimed it back to myself. The bots aren't on this one as yet 🤭
🟠 Dave Portnoy on #Bitcoin “We are going to have all of these Bitcoin billionaires and rich people who just bought #Bitcoin and didn’t do anything else.” 😂
Never sell your #Bitcoin, everyone knows the rules.
#Plebchain #Nostr #bitcoin https://video.nostr.build/447f8d0d880065a4ea0637b27576d1d4dbe477492ff0e7ff632746f6e5882eee.mp4
We're gonna see soooo much more of this 🤣 #cope #stayhumblestacksats
Thoughts on BitVM? 👀
nostr:npub1kvaln6tm0re4d99q9e4ma788wpvnw0jzkz595cljtfgwhldd75xsj9tkzv I have feedback about your description character limit 👀
#m=image%2Fjpeg&dim=902x1920&blurhash=%5B26a%40tVy%3FwD%2500%25h9Ft8%5E-X*-rNF-%3AxII-WEXNQ%3AtkIU%247R%7EMyR%25DhbWH%40kB_MMK%252IU9Xru9En%2C&x=882c6a8da72c602270bc80caf25f26e0df7b6ef778b972b574d364ccdc855e6f
Dammit, sorry my bad this was nostr:npub1dx5q2el8nd4eh3eg9t2e25fd7zuqg7zxz6ldkc3uzgh66ss2yc6st288sj
nostr:npub1kvaln6tm0re4d99q9e4ma788wpvnw0jzkz595cljtfgwhldd75xsj9tkzv I have feedback about your description character limit 👀
#m=image%2Fjpeg&dim=902x1920&blurhash=%5B26a%40tVy%3FwD%2500%25h9Ft8%5E-X*-rNF-%3AxII-WEXNQ%3AtkIU%247R%7EMyR%25DhbWH%40kB_MMK%252IU9Xru9En%2C&x=882c6a8da72c602270bc80caf25f26e0df7b6ef778b972b574d364ccdc855e6f
Oh interesting, are you chatting with anyone (maybe nostr:npub14tq8m9ggnnn2muytj9tdg0q6f26ef3snpd7ukyhvrxgq33vpnghs8shy62) about that as yet?
Bertie's, every time 🤤
#m=image%2Fjpeg&dim=1295x1500&blurhash=%7BmM%3F%23jO8njW-nOWB_Nwg-%3Df%2BWUj%5DV%40ofx%5BWC%25%23WEX7jbj%5Boej%3FfkS%23nin%2BaybbaxRPoeWEjZjaa%7BbHW.V%40W%3At7Wqbaf6oLa%7BRjbHtRazbGjtjbo1ofj%5Bozn%25n%2BfPbaayWBj%40ozayayf7bGbFaebH&x=983216954d7e5a4183604049aa44f846b2f5b9c69f2ff2ee71c3e98c35f1771e
Very interesting, just picked up some zapping sats with my Play Store linked c/c via Primal 👀

Adding a little context, here's where we guard against this for nostr:npub13ljnkd633c7maxatymv3y2fqq8vt3qk7j3tt0vytv90eztwgha9qmfcfhw
nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm
here is my analysis (assumption)
And I think it won’t be too difficult for alby to fix it.
1. When the payee requested to receive a payment, he uses the Web UI to create an invoice and Alby call it’s LND, record this in DB and send to user
2. If the payee sends this invoice to the payer, which happens to be another Alby user, Alby only record this operation on DB and update both sides balances (i.e. deduct from payer and credit to payee).
3. However, that invoice is not revoked, even it’s actually used and Alby system is aware about this fact.
4.Then someone from an external wallet tried to pay this invoice. Since it’s not technically used, LND will accept this payment and Alby LND node still receive sats.
5. However, when Alby try to look up payee in internal db but found this invoice “has been used internally”. Some errors throw, and balances not updated nostr:note19jgtjprckcnxk4fphtnq826l37scvk68wn9hya8uw0fhaghkdnvsu0t2qu
I was just going to suggest this might be what's happening when you were able to replicate with WoS as well. It's something we explicitly had to guard against in nostr:npub13ljnkd633c7maxatymv3y2fqq8vt3qk7j3tt0vytv90eztwgha9qmfcfhw
This OneKey? 😳
#m=image%2Fjpeg&dim=965x1920&blurhash=%5D6R%7B%23%3B9E%5EmxG%25g%5ETD%25EJIospyXtl9FbEM%7B5O9FxJRks%3A%7Dv%25154WUIUR%7EIURiITt8OTt8MyoOS0%3FIE1TIRiM%7CEfn%25MxWVso&x=313b8c5c37bc220775ef9ac4e72d2e31c6137106eb9e91e4b45fd1d052cab9cb
Well...
nostr:naddr1qqrrxdeexger2q3qu8lnhlw5usp3t9vmpz60ejpyt649z33hu82wc2hpv6m5xdqmuxhsxpqqqp65w73757p

