OP_TXHASH authors are Steven Roose and Brandon Black, not Russell O'Connor and Brandon Black.

You can verify it in https://bips.dev/346/

Also, for some reason in the left index TXHASH looses the prefix "OP_".

I don't mind AI slop, but you need to double check it.

I'm pretty sure you all know about when Top Gear tried to destroy a Toyota Hilux and didn't make it.

But if you don't know about it, here it is:

@januszgrze ?

Why is this better than sending onchain directly to the federation?

npub1vt803quxxq32fuwkp42g2lyaw2t9qupvnl3z0vyc3s9kudkyhn8qt28cxv

Clever usage of the OP_RETURN to reveal the block height used on the time lock for later wallet recovery.

Matt Morehouse (author of the Eclair disclosure) has a few other issues on his blog (LND, CLN, LDK...):

https://morehouse.github.io/

I think it's related to runestones:
https://www.xverse.app/blog/runestone-ordinals

Actually Lighting made it useful ;-)

Misty Breez, Aqua, Helm are all Liquid wallets that offer a Lightning interface via Submarine Swaps. Users pay swap fees per transaction but don't have to deal with channel management. Very appealing for non tech users.

Brilliant.

Yeah, that's why. Boltz swaps are limited between 1000 and 25 million sats.

Why is Send grayed out? Looks like I can receive, but not send?

If you don't have funds, what do you wanna send? ;)

I have to stop responding, stacker news is now asking for 1000 sats for the next answer. I know they are anti spam features, but it doesn't make sense to me now keeping spending sats like this.

Over and out.

You may want to be more explicit about the password, in terms of what it actually is. I wasn't sure if it was like a bitcoin passphrase (does Liquid even have that?) or it was just a password for that instance of Helm Wallet. It turns out it's for the later, because you can restore from one browser to another, just with the seed phrase. You may want to have more info on this.

The password is used to encrypt your mnemonic on local storage.

When I create a wallet, then tried to restore it, I was very confused. You see, when I first wrote down the seed words, you have them in this order:

Hint:

• copy your mnemonic to the clipboard
• click on input #1 and then paste the entire mnemonic
• the app will understand what you're trying to achieve and will fill all the fields

I don't understand the listings in the Network section. You have Liquid, Mainnet and Testnet. So when you choose Liquid, you're choosing plain Liquid (does it have a testnet equivalent?). And then the other options are Mainnet and Testnet - so at that point, you're actually using Bitcoin, instead of Liquid?

Did you see "Bitcoin"? Really? It should be Liquid (for Mainnet), Testnet and Regtest. Remember, Helm is a Liquid wallet, mainnet for it is Liquid, not Bitcoin.

You go to the main site and click on Open app. That takes you to a website with dev in the name https://helm-wallet.pages.dev/. That makes me think it's just for dev. Maybe have 2 separate links?

I need to improve the copy, that's for sure ;)

The code is mirrored in 3 sites (github, gitlab and bitbucket) for redundancy and censorship resistance (it will also be uploaded to IPFS as soon I reach version 1).

I then deploy the app on to two different domains, again for redundancy and censorship resistance. It's the same app, if you use the same mnemonic you will have the exact same experience.

I see now it may be confusing, I will change the copy.

No, sorry.

You can find me here, on X or Nostr, or open a issue on GitHub.

Both.

Actually it supports mainnet, testnet and regtest.

Just go to settings > network and change at will.

In my wallet, https://helm-wallet.com/ I receive a commission from the fees paid to Boltz for the swaps.

Helm is a Liquid wallet that uses Boltz submarine swaps to disguise itself as a Lightning wallet.

A quick visit to https://boltz.exchange/ and you can see the fees Boltz charges:

• Lightning => Liquid = 0.25%
• Liquid => Lightning = 0.1%

Having said that, I receive more sats from zaps that from Helm :p

You add one bit of checksum for every 32 bits of entropy.

This way the sum of bits will always be a multiple of 11:

• with an entropy of 128 bits (4 x 32) you add 4 bits of entropy = 132 bits (12 x 11)
• with an entropy of 160 bits (5 x 32) you add 5 bits of entropy = 165 bits (15 x 11)
• with an entropy of 192 bits (6 x 32) you add 6 bits of entropy = 198 bits (18 x 11)
• with an entropy of 224 bits (7 x 32) you add 7 bits of entropy = 231 bits (21 x 11)
• with an entropy of 256 bits (8 x 32) you add 8 bits of entropy = 264 bits (24 x 11)

Wheels are already in motion:
https://bitcointalk.org/index.php?topic=5528323.0