I've been thinking about inheritance, and I discovered something called the Liana wallet. It seems almost like a perfect solution. I created a script address that allows me to spend without any restrictions, while adding a time-lock condition for heirs—giving them the ability to spend after a relative time-lock of one year. No third parties or additional requirements needed. As long as I don't die suddenly and my heir doesn't simultaneously lose access to their device, it's quite secure. And since the script allows great flexibility, I can enhance safety further by using multiple keys in a multisig setup, while maintaining the same overall structure. As long as I remember to make one on-chain transaction every year, it should be nearly perfect.

There used to be a few things about real estate that I just couldn't wrap my head around. Take the 'squatting' controversy in the West, for example. The idea that someone could illegally occupy a vacant house, stay there long enough, and suddenly gain rights that make it impossible for the owner to evict them seemed absurd. I honestly thought America was turning into a socialist country when I first heard about it. Then there’s the fact that anyone can legally snoop on a property's registry just by knowing the address. I couldn't understand why complete strangers were allowed to check if a house was rented, owned, or heavily mortgaged just to guess someone's net worth. Or the lack of absolute 'legal conclusiveness' in the real estate registry. You hear these incredibly unfair stories of people buying a house trusting the official state ledger, only to lose their home later because the ledger had been forged sometime in the past. And finally, the concept of a tenant's 'opposing power'—the rule that a tenant must officially register their move-in to protect their deposit. I always thought, "If I signed a lease and handed over my money, shouldn't my deposit just be naturally guaranteed?" Life is full of laws that don't seem to make sense, so I mostly just brushed them off at the time. But as I dove into Bitcoin and started questioning what it truly means to 'own' something, all these disjointed mysteries suddenly clicked into place. The complex rules around a tenant's rights exist for a very specific reason. A lease is basically a private contract (a claim) between the tenant and the 'previous owner.' When the house is sold, from the perspective of the new owner who legitimately paid for the property rights, it is logically correct to argue, "Your deal was with the last guy, not me. Get out of my house." But what happens if the law just unconditionally protects the seemingly vulnerable tenant? A scammer could take out a massive mortgage, default on it, and then pull out a fake, backdated lease agreement made with a relative to screw over the bank when they come to seize the asset. That is why 'public disclosure' is required. By making the existence of a legitimate contract public at a specific time (like registering a move-in date), the government promises to review and recognize that right later. It’s a compromise. And the reason anyone is allowed to look up another person's property registry is precisely to maintain this public disclosure system. But herein lies the critical dilemma: the ledger managed by the government—which effectively acts as a 'monopolistic sequencer'—doesn't perfectly guarantee the truth. This is exactly why courts don't grant absolute legal conclusiveness to the real estate registry. Historically, there have been too many cases where the name written on the state ledger didn't match the true owner of the land. Fraudsters have long exploited wars or administrative chaos to manipulate the ledger and hijack property rights while the true owner was unaware. So, to make up for this flawed ledger, what happens if the law starts prioritizing 'actual physical possession' over paper documents? You end up with the exact squatting crisis we see in the West today. Whichever path is chosen, scams exploiting the legal loopholes will inevitably follow. The fundamental reason real estate is so legally tangled and fraught with endless lawsuits is that, technically speaking, perfectly proving ownership of a physical asset is impossible. It can only ever be 'presumed.' High-level verification requires massive costs. People wanted to protect their assets but didn't want to bear those verification costs, so they handed this complex arbitration over to a central authority: the government. This has become the root of many modern social problems. When the government unfairly takes a side, or when it becomes a player itself and intervenes in the market, we are left completely defenseless. This is the core reason why I don't see real estate as the ultimate store of wealth. I look beyond simple inflation hedging to the true essence of an asset: "Can I truly own it? Can I prove my ownership without needing anyone's permission?" For me, the only assets that pass that test are physical precious metals and Bitcoin.

I’ve previously mentioned that I wasn't entirely convinced about the future of Bitcoin. To put it briefly, my argument was that even with the Lightning Network, there are inherent limitations to Bitcoin evolving into a global-scale payment solution. I was curious to see how Bitcoiners would respond to this, but at the time, I received no answers, which led me to believe it might be an unsolvable problem. However, I recently started looking into Layer 2 solutions other than Lightning, and I found one that seems quite promising: the Ark protocol. While it’s impossible to explain exactly how it functions in a single post, the conclusion is that it appears to effectively address the limitations of Lightning. Based on my understanding of their documentation, here is how the UX of Ark works: Off-chain payments do not provide the same level of finality as Lightning immediately. To achieve Lightning-level finality—meaning no one can touch my funds, and I am cryptographically guaranteed a unilateral exit to Layer 1 without relying on anyone else—I must participate in what is called a 'batch settlement transaction.' This is an on-chain transaction that anchors to Layer 1 to achieve finality. One might ask, 'If it requires an on-chain transaction, how is this a scaling solution?' The key is that this batch settlement transaction involves multiple people simultaneously, allowing the fees to be shared among them. Furthermore, the size of this batch transaction does not scale proportionally with the number of participants; it remains a fixed size. In other words, it is an on-chain transaction that enables true 1/n cost efficiency. With Lightning, the decisive obstacle to global scale is that when you open a channel, you have to pay for that on-chain transaction yourself. Ark solves this by allowing for massive, shared efficiency. If this becomes fully realized, it is theoretically possible to achieve self-custody without ever needing to make an on-chain transaction in your lifetime. This is made possible through Taproot and other technical mechanisms, and based on my current knowledge, it seems theoretically sound. While it still requires code-level verification, this discovery has resolved my only lingering doubt about Bitcoin. I now have genuine hope that it can function as a global-scale payment solution.

I'm trying to switch the wallet setup in my phone's Nostr client to use a local relay (specifically @npub1hqlx...gspw) and @zeus for fast responsiveness, but it doesn't work properly in almost all clients. I suspect it's because they automatically block WS connections instead of WSS. Only amethyst allows zaps, but even there, balance and history checks don't work. Blocking WS is fine, but localhost should be whitelisted as an exception.

@ZEUS Apps connected via NWC are extending beyond a single page, but scrolling isn't working, so the initially registered ones are not visible.

@npub16g4u...kv4h How do I get rid of the red inquiry button floating on the screen? It's really annoying.

Am I the only one who thinks it's weird that the playback bar, play/pause button, or settings button cover the video when watching? Isn't this way too annoying?

Zapstore

ClipRelay — Zapstore

Automatically syncs clipboard between your devices. All communication goes through Nostr relays, encrypted with NIP-44. Authentication via NIP-46 b...

I had Claude build me a clipboard sync tool using Nostr. I've always found it extremely cumbersome to copy something on one device and paste it on another by having to open a messenger app, find the chat-with-self room, paste it there, then on the other device open the same messenger, go to that chat room, tap on the message, and copy it again. Sure, similar tools probably exist out there, but these days with Claude around, it's so quick to just ask an AI to build it—so I went ahead and made one. Here are the app's key features: - Supports only NIP-46 login (direct use of private keys is not supported. Aside from security concerns, the problem remains of how to transfer that private key to another device. Isn't it ridiculous if you still have to use a messenger just that one initial time to send it over?). - Tracks in real-time the relays and Blossom server specified by the user, and transmits data through those servers. - Text is encrypted using NIP-44 self-encryption; images are encrypted with an AES-GCM one-time key, then the encrypted binary is uploaded to Blossom, while the SHA-256 hash and decryption key are sent via NIP-44 encryption. General file types (beyond images) are not currently supported. - Supported on Windows, Linux, Mac, and Android; iPhone is not supported. - Usage: On desktops, after installation and login, there’s nothing else to do—copy on one device, and it automatically appears on the other's clipboard. On mobile, there is a persistent notification—after copying, tap the persistent notification to send it to the other device. When receiving, a separate incoming notification appears (distinct from the persistent one), and tapping it copies the content to the clipboard. - Currently free. I'm considering a payment system for the future—specifically when large file support is added, I'm thinking of passing charges directly through the Blossom server (not that I intend to collect payment directly). Enabling economic incentives for Blossom server operators was actually one of my motivations for building this app. I plan to support it once a smoother payment standard emerges. - On mobile, the app attempts to stay running continuously unless explicitly closed by the user (though this cannot be guaranteed). - Care has been taken to ensure plaintext is never stored outside the app’s own storage (e.g., in notification systems), though this cannot be fully guaranteed. - Clipboard history is stored plaintext on the device itself. - Logging out deletes authentication data along with the history. - The NIP-46 communication private key is stored in the OS-specific secure key storage. I’ve put effort into encryption, but given my own technical limitations, I can't be certain there are no data leaks somewhere. I do not recommend using this app for highly sensitive or critical information. It’s intended only for everyday, routine use—something that replaces the kind of casual content you’d previously share over messenger apps.

CTO wants to have a 1-on-1 meeting on Monday. It seems like the time has finally come. If I get laid off, I should take a good two-month break to rest.

Nostr client developers really need to make it easier to add friends via QR codes — especially when meeting users in person, not just following them online. Many clients are quite inconvenient in this aspect, and some don't even have this feature at all. It's unreasonable to expect users to manually type long public keys, and given that Nostr is decentralized, search functions are already limited. It’s frustrating that even when you meet someone in real life, adding them as a contact can be such a hassle.

I was using Zeus Wallet and thought I wouldn't need Alby anymore since it supports NWC, so I uninstalled Alby. But it turns out Zeus isn't as reliable for payments—while it works fine when using Zeus directly, it often fails when connecting through apps via NWC. Probably because Zeus runs locally on mobile, whereas Alby operates via server. Looks like I'll have to reinstall Alby.

I'm currently using @Minibits mint through @npub1h0uj...rwx8 , and I'm reaching out with a question. I'm personally developing a service that requires payment via hold invoice, and during development, I was testing the expiration/cancellation behavior by paying a hold invoice using the Keychat Cashu wallet. The payment attempt initially seemed to fail—although the payment did reach the recipient side, it remained in a "pending" state since it wasn't settled, which is expected. I didn't mind the unclear UI indication, since most wallets don't clearly display pending states anyway. However, the next day, after the invoice expired as intended and the payment properly failed, I noticed that the deducted balance in my Keychat wallet wasn't restored. Normally, when a hold invoice is canceled, the mint's Lightning node should recover the funds and reflect that credit back to the user's balance. If this were my own Lightning node, the balance recovery would have happened automatically. But with the Cashu wallet, since I had already paid ecash to the mint to initiate the payment, my balance was deducted up front. From the mint’s perspective, once the ecash was spent, the balance was marked as spent—even though settlement never occurred. And since the control had already been effectively transferred, the mint likely considered the payment as completed on its end. It doesn’t appear to track the subsequent cancellation status. Moreover, due to the anonymous nature of ecash, the mint likely can't identify who made the payment—even if they wanted to issue a refund, it might not be possible. I can provide proof of the hold invoice and confirmation that it was ultimately canceled (via DM). Surely a refund shouldn’t be impossible? I understand it might not be easy to verify, and while I understand if no refund can be issued (it's only 5,028 sats, not a large amount), this highlights a bigger issue: going forward, such payments need to be properly handled. Otherwise, it effectively means users permanently lose funds to the mint even when payments fail. This isn't just an issue with Minibits, but likely all #cashu mints. A proper mechanism needs to be developed to handle these cases.