Avatar
Perlover
0d3f0394b117eee4832bd31ee415733d0386928c7daae05525483ff8c9eb046b
Lightning & Bitcoin Maximalist ;-) openpgp4fpr:8f63e103a538fc16222d5ff44c3fc769514425bc

When I look at the balance of my #bank account, where the amount is less than a $1, I think out of habit, "very small #UTXO... Will I be able to send it?" Only then I remember that #banks don't have a dust problem :)

Does anyone have the same thoughts?

#Bitcoin #fiat

The people in charge of bitcoin don’t care about you, fiaters... :-)

Replying to Avatar Dima Loshagin

https://cdn.nostr.build/p/4aJq.mp4

#photography #portrait #studio #фотография #студия #портрет #artstr #nostrart #art #photostr #photo #artists #video #видео #mp4 #hot

I have read NIP-46 and I think it's exactly same. Yes?

I have a suggestion for a new protocol. Maybe something similar already exists, but I do not know. The essence is as follows. Organizations and small companies may need to maintain a Nostr account. But it is dangerous to trust the key to employees - it can easily leak. You can make a similarity of the Nostr Wallet Connect protocol, but a server will work, the purpose of which is to store the key from the company's account, accept applications for signing notes from trusted clients (via the dedicated Nostr relay) who own a secret that can be revoked at any time (as in NWC). That is, if an employee is assigned to maintain an account, he receives a new secret, after which his client Nostr works the same way as with the original company account, but all notes are sent to the relay, listened to by the company with the key from Nostr. If the messages are signed with a valid employee key, then the note sent by them is unpacked from the padding field, then signed as the original with the company's Nostr key and sent to the network. Thus, the company will have an official account in Nostr, which can be accompanied even by several employees, and there will be a minimal risk that the account will be subjected to constant insider hacking.

Přečetl jsem si ještě jednou vaše pokyny - chápu správně, že pokud je kavárna nebo restaurace již na mapách, ale nemají pole pro qerko (currency:XBT, payment:qerko:lightning) - stačí zadat ID ve vaší tabulce a samotná pole budou automaticky přidána později? Předtím jsem ještě ručně přidával platební pole (currency:XBT, payment:qerko:lightning a další) i když místo již existuje, ale tato pole neexistují.

Všiml jsem si mnoha polí s adresou waklaf@bitlifi.com, ale když se podíváte na odkazy na OSM, neexistují žádná pole pro Lightning Qerco (currency:XBT, payment:qerko:lightning...). Možná jen pasuje ID na OSM. To znamená, že tento uživatel jednoduše napíše svou LN adresu, aniž by cokoli udělal. Dělá to někdo z vašich zaměstnanců jako zástrčku pro další úpravy?

I added the one new restaurant in OSM and after 10-20 minutes I see it at BTCMap with my filled data! 😳 Realtime updating? I was shocked!

Updated in your Google Drive table (qerko-osm@lnbits.f***) LN address ;-)

The 2 new restaurants added and one was edited ;-)