I don’t want to worry about managing my own Lightning node (channel balancing, liquidity, uptime, watch towers, etc) and I worry about having my sats on Wallet of Satoshi (the risk of being rug pulled is immense) so in that sense Aqua delivers a good balanced solution for my worries.

Having said that, Aqua has more coins that I’m not interested in, which makes it not the easier “Lightning wallet” to use. So I decided to make Helm Wallet, a Liquid wallet that uses Boltz submarine swaps to disguise itself as a Lightning wallet that even your grandma can use.

It's a PWA, which means it is immune to app store censorship. The web app is completely independent, no server required. You can clone it, build it and run it from your own computer. Everything runs on the browser.

You can use Tor to hide your IP address from Boltz and the chain explorers.

You can try it (testnet is available) on:

Every base is base 10

You don't consolidate addresses, you consolidate UTXOs.

Your assumption is correct, you get 1 new UTXO every month, and at the end of the year you consolidate 12 UTXOs into 1.

The above is true if you use 13 different addresses, the same address for every UTXO or even a mix: it doesn't matter.

This site is excellent explaining Bitcoin: https://learnmeabitcoin.com/technical/transaction/utxo/

Those are not related:

Re-using addresses does not reduce (or increment) the number of UTXOs

Satoshi's coins are locked to his pubkey (P2PK), not to the pubkey hash, because P2PKH was "invented" later. This means an attacker will first go for Satoshi coins, where he has all the time in the world (instead of 10 minutes) to try to steal the coins.

So, if someday some of the Satoshi's coins move, we should start worrying. Until then is business as usual.

Not true.

When receiving a P2PKH payment, what is revealed is the pubkey hash, the pubkey stays hidden. The pubkey is only revealed when the unlocking script gets to the mempool and stays revealed on the blockchain when the transaction is confirmed.

So, if for some remote chance QC is able to break ECDSA (i.e. find the private key from the pubkey), your UTXO could be "hijacked" only when the attacker finds your pubkey, which is only when you try to spend it and the spending transaction arrives to the mempool.

This means the attacker has around 10 minutes to do it (could be longer), or else the transaction would be confirmed and the UTXO is no longer "hijackable" since it's already spent.

This is another reason to not re-use addresses (remember, a P2PKH address has the pubkey hash in it).

IMHO QC will never break ECDSA, but I could be wrong.

Soon you'll be implementing Lightning on top of Ark 😏

SoBrief makes a good job summarising books:

For me, the best hack is having no alarm clock and waking up naturally (ie a the end of sleep cycle). This simple rule changed my life.

11

Solution:

At first glance this puzzle seems unsolvable. But it has something weird, and this is the fact of “the last digit of the product of their ages” being a clue. How can something so vague be a clue? Unless it’s not that vague. Let’s explore it a little bit.

We make a table with all possible ages for each daughter and calculate the last digit of their product - i.e. (a*b).mod(10)

We can get rid of half the table (since 6x4 = 4x6) and since the problem says they are not twins, we can also get rid of the main diagonal, the one with the square numbers.

Now let's evaluate each digit on the table, and see what we get.

Let’s start with digit 1: it appears once (on 7x3) and the sum of the factors is 10.

Digit 2 on the other hand, appears 6 times (on 2x1, 4x3, 6x2, 7x6, 8x4 and 9x8) and the sum of factors is 3, 7, 8, 13, 12 and 17

Here is the final table

So, in order for the final digit to be a clue, it must tell us something unique. Looking at this table, we realize only 2 digits fulfill this, the digits 1 and 9. So, if the last digit of the product of their ages is 1, that means they are 7 and 3 years old. And if the final digit is 9, that means they are 9 and 1 years old.

Now we have two possible answers, how to proceed? Well, the problem is not to guess their daughters age, but the sum of it. And since in both cases the answer is 10, that’s your answer.

If you wanna know more about Ark, for real, you can start with my (a bit old) ark explainer and keep a look at arkdev's blog

Yes, helm-wallet.com.

It's there, black on white, not trying to fool anyone:

"Helm is a Liquid wallet that uses Boltz submarine swaps to disguise itself as a Lightning wallet that even your grandma can use."

Hi. I have some shell scripts that fetch articles from a RSS feed (from pinboard.in) and post them daily into nostr, see if it helps:

Example note published:

Ahhhh, now I understand the FUD :) At first I thought you just don't understand Ark.

Like in mainnet, you can aggregate several VTXOs into a larger VTXO. The problem would be if you have one single VTXO with small value. Which isn't exactly a problem, is it?

Correct. Remember, he didn't ask for her ages, he asked for the sum of it. In both possible solutions, the sum is the same, 10 ;)

I have one for you:

A friend of mine has 2 daughters (not twins) under 10 years old and wants you to guess the sum of their ages, but the only clue he gives is that the last digit of the product of their ages is the number of their house's door.

Definitely Ark: you can aggregate thousands of transactions into one single onchain transaction while users never loose control of their funds.

Try https://helm-wallet.com/, the Lightning wallet even your grandma can use.

Your grandma doesn't need to manage any liquidity, it just works.

If you have any issue, reply to this post and I will try to help you.

Sort of.

Unlike Muun, it's a PWA (so no app store censorship) that uses Boltz to perform submarine swaps between Lightning and Liquid (for lower fees). You fully own your funds on Liquid and you send and receive Lightning payments via Boltz.

Give it a try, you can use testnet: https://helm-wallet.pages.dev/

Also, https://helm-wallet.com/ the Lightning wallet even your grandma can use.