pull down to refresh
21 sats \ 1 reply \ @bordalix 14 Mar \ on: How are mnemonic phrases generated ? bitcoin
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.
pub key is literally PUBLIC so is already revealed
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.
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.
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: