Melvin Carvalho's avatar
Melvin Carvalho _@melvincarvalho.com 9 months ago
Use it. Use on-chain bitcoin. Use layer 2 bitcoin, such as liquid. Block should create an elements side chain at massive scale. Where the cost of a tx is close to the cost of storage (about 1msat). Integrate it. Integrate it into X. Into nostr. Into google. Use on-chain zaps. Use bitcoin as legal tender. Use all the layers, without forking bitcoin contentiously which may cause a chain split. Use the programmable layers. Use #lnbits. Use merge mining. Use single-use seals. Use RGB. Use client side validation. Use testnet. All these things are here today, and just need to be used. Once we see native currency levels, we can think about increasing the capacity of the mempool. Let's use bitcoin for commerce.
↑ Parent

Replies (4)

Default avatar
npub1x5tp...55am 9 months ago
Testing zap receipts for this note… we made five attempts to⚡zap this note, at melvincarvalho@btip.nl, over a period of 3 minutes. Five of the zaps were successfully paid... Please check for 5 satoshis received. Problem: we found that your lightning address server **did not** produce any zap receipts. This means that nobody else could see see that you got zapped... no number appears next to the ⚡icon after zapping.... also FYI... your server at btip.nl is responsible for creating your zap invoices, and we found that it responded slowly... invoice generation took an average of 3033ms (3.0 seconds). We consider this slow... generally, zap invoices should be created in under one second. We recommend that you use a cloud-based Lightning node to get more reliable zaps.
↑