Some background: https://blog.lopp.net/congress-is-criminalizing-privacy/

First of all, kudos for the novel idea to do this because it is a legitimate problem. I'm torn that you're using OP_RETURN because normally I think it should be used very sparingly but this might be a use case that is deserving. However, I feel this doesn't scale and is ultimately the wrong approach.

You mentioned the SeedHammer project but they're actually using the Uniform Resources standard which need not be stamped onto metal. So in a multisig setup where you store each private key (in whatever medium) you should also store the descriptor in UR format to allow for proper recovery (and aide privacy).

I think the bigger issue here is that the backup procedure of wallets should also include the descriptor (and for multisig in UR) in addition to the seed. This seems to be a cultural change though.

I don't agree with your arguments that hardware wallets undermine one's sovereignty. They are just a specialized tool to aid you sign your transactions more securely. Perhaps you could argue that ten years ago you could get locked into their system but almost all current hardware wallets use the open standards (BIP32, BIP39, output descriptors) so you can easily migrate to any other hardware or software wallet.

The most compelling argument to use them is that they are specialized computers so their attack surface is greatly reduced compared to any general purpose computer. If you're using a general purpose computer you're at greater risk to hardware and software attacks. Setting aside hardware attacks, to securely use a general purpose computer you need to verify the OS and your wallet software each time you use it. All it takes is one time you don't do it. Then you have to hope that no upstream libraries have been poisoned (e.g. XZ backdoor). There's a reason why the Dark Skippy attack was done on a SeedSigner. It's just so much easier to create a modified version and there's no secure boot protection.

Lastly, just to address your point about hardware wallet manufacturers shilling their product and creating FUD. I think a more correct assessment of the situation is that they have identified problems with using generic hardware/software and are providing a solution to remedy that. I haven't ever see them make false claims what they're doing just to sell more devices.

For real. I can't believe how few people haven't called him out. And the sheer fucking hubris of continually asserting, "Darth is always right".

How did you know?

Thanks. I'll have a look again. Problem I had before was that neither accepted my country of residence, Paraguay, in conjunction with a US bank.

I have tried for quite a long time. I ran my own BTCPay server which integrated into my invoicing system and gave discounts if payment was in bitcoin. But none of my clients will pay in bitcoin. I can't legally demand it so not sure what else I can do. I suppose I can get "better" clients but that's potentially not even doable.

I was just in the middle of doing some channel management.

Can take over a minute for me. Fastest is like 15 seconds until it's ready to use.

Does the extremely slow load times not irritate you?

Thanks. I just searched on Reddit and saw posts describing the same thing. When I was signing up a few months ago I vaguely remember answering the question whether I would have US operations. I answered yes, because it's possible not thinking much of it.

But this is fucking annoying as Wise don't offer cards anymore (I think because Evolve, who they used, got nervous and suspended it). Seriously, fuck banks.

Where in their terms of use does it say this? I also started using Mercury and have only non-US clients but haven't heard anything from them.

The software and experience is quite user friendly but you'll need to make sure you understand what you're doing lest you make a mistake.

First, you'll need to generate a few private keys offline. You can use the SeedSigner (same hardware) to do this if you want or hardware wallets. Then you must create a wallet descriptor using these private keys. It is imperative that while doing this you don't expose your private keys on an internet connected computer.

Then, on the SeedHammer controller, you need to enter each private key and scan the wallet descriptor. Be sure to check that the descriptor contains the same private keys you generated in case the computer you used to generate the descriptor is compromised. Then all you need to do is follow the instructions on the screen of the controller which is periodically changing plates. Each plate engraving takes a maximum of 20 minutes. The engraving is very loud though so you should do this in a place where you won't disturb people. I had to stop because my apartment neighbors complained.

The device itself has no memory or storage (it's intentionally chosen because it's dumb) so you can loan it to whomever you want. If you're more paranoid you can use a new controller (Raspberry Pi) if you're borrowing someone's but as long as you personally prepare the SD card (and verify the software) then you'll be fine.

I just started using Invoice Ninja, working well so far. Only thing is I wish it would support SQLite. It also has BTCPay server integration.