Avatar
arvin
50ad69ef936e893e289d0ac1ddcde051792cfb708ec00d738fa30adf2f4b4708
👨🏾‍💻 plumbing bits at npub1gal0y3vuj3c5sme6444ncsr8xcfm9axehfcsuqfamz5v926m6f2s4yz3t2 | #trinistr 🇹🇹 1/2 ChainDuo npub1kd3nlw09ufkgmts2kaf0x8m4mq57exn6l8rz50v5ngyr2h3j5cfswdsdth w/ npub1y67n93njx27lzmg9ua37ce7csvq4awvl6ynfqffzfssvdn7mq9vqlhq62h

Just claimed it back to myself. The bots aren't on this one as yet 🤭

Thoughts on BitVM? 👀

Replying to Avatar arvin

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

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

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 👀

Replying to Avatar Sherry

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