pull down to refresh
0 sats \ 0 replies \ @bordalix 19 Apr \ parent \ on: Who pays for Bitcoin wallets? bitcoin
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.
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
Probably could tweak relaying to lower minimums, but that hasn't happened in part because going below the base units becomes indistinguishable from spam
I disagree.
Min relay fee was introduced in 2013, when BTC was worth ~$100.
A sat is now worth 1000 times more. If the value of a sat was sufficient to prevent spam in 2013, why can't we use a fraction of it today to prevent spam?
Nodes can use 0.1 sats/vbyte (or less) as min relay fee today. So, if a tx has 138 vbytes, it would need to pay at least 14 sats in fees (you need to round it up).
1 sat/vbyte is a relay rule, not a consensus rule: a 0 fee tx is perfectly valid. Nodes don't relay tx with less than 1 sat/vbyte to prevent spam attacks, but they accept 0 fee txs in blocks.
This limitation was introduced when BTC was worth a couple of bucks, it can be lowered to 0.1 sats/vbyte (or even lower) while maintaining the original security assumptions.
So, a 138 vbytes tx would need to pay at least 14 sats to be relayed by the nodes.
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:
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:
-
Every time you receive a payment, you get a new UTXO regardless of the address you gave to receive the payment
-
Every time you pay you could get a new UTXO (your change, if any) regardless of the address you use to receive the change
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.