So is there any concern here? I'm surprised why it even let me enter any amount up to the maximum btc in my wallet even when I didn't connect my nano ledger yet? Again if you had an old account in your ledger live that isn't connected to your replacement nano ledger seed which you use now, then what happens?
Coins are not stored in your device... coins are not stored in your Ledger Live... coins "exist" as UTXOs recorded on the blockchain. Ledger Live has a copy of your master public key for any account that you have added into it... it uses this to determine what UTXOs exist that are controlled by the public keys generated from that master key. So, you don't need the device to create an unsigned transaction... and to create the transaction, you have to specify the amounts... hence why it lets you attempt to spend the full balance without needing the device attached. If, when prompted to attach the device to sign/confirm the transaction, you connected a device with a different seed, it obviously wouldn't be able to sign it as it would not have the appropriate private keys. Generally, if you add an account in Ledger Live (which requires the device attached), and you can see coins/balance... then you can be certain that you can control them. |
|
|
|
You'd need to understand how the wallet.dat encryption works then... it's not like the entire wallet is actually encrypted (if it was, you wouldn't even be able to open the wallet.dat in a "Core" application and see the addresses/transaction history etc without entering your passphrase). Instead, what happens is that it is just the private key data that is stored encrypted. As per the info here: https://en.bitcoin.it/wiki/Wallet_encryptionWallet encryption uses AES-256-CBC to encrypt only the private keys that are held in a wallet. The keys are encrypted with a master key which is entirely random. This master key is then encrypted with AES-256-CBC with a key derived from the passphrase using SHA-512 and OpenSSL's EVP_BytesToKey and a dynamic number of rounds determined by the speed of the machine which does the initial encryption (and is updated based on the speed of a computer which does a subsequent passphrase change). So, the encrypted private key and your passphrase alone are not enough to decrypt the private key... you actually have to decrypt the "master" key first... then use that master key to decrypt your individual private keys. There has been some discussion about this on another thread: https://bitcointalk.org/index.php?topic=5333765.msg56938441#msg56938441I've been able to get as far as extracting the encrypted master key and getting the IV, Salt, iteration count etc... but I'm not sure about how to actually decrypt the master key and then decrypt the individual private keys at this point. |
|
|
|
Yeah, I know the importance of enabling RBF while broadcasting a transaction but technically I just wants to know how long a transaction can stay in the mempool?
Theoretically... it can stay there forever (providing certain conditions are met). Don't forget, there isn't just one global mempool... each node has it's own mempool and they're not necessarily all configured the same. "Default" Bitcoin Core nodes, will generally drop a transaction after 14 days (or when the transaction fee falls below the "mempool min fee" value) etc... but not all nodes are configured like this... some will hold onto a transaction forever until it is confirmed or becomes invalid. Some nodes might even override the default behaviour and drop transactions after only 3 days or X days... or never! Additionally, if a node (or wallet) takes it upon itself to keep rebroadcasting the transaction, it might briefly drop from some (but not all) nodes after the 14 days, but then be put right back into those mempools because of the rebroadcast. I will never make a transaction more than 1MB depth from the mempool so I always keep an eye on the mempool chart whenever I want to make transactions but it's completely out of our hands when we use custodial wallets.
Not necessarily... *some* custodial wallets allow users to set fees... but yes, most don't... some use RBF (but that's generally useless to the user as they can't execute RBF transactions anyway, at least I've not seen any that support this)... and if you sending from a custodial wallet, CPFP might still be an option if the receiver is not using a custodial service. |
|
|
|
I haven't tested the same address yet, but I doubt it can be solved without a firmware update.
I didn't see any real mention of bug fixes in the release notes but it would be interesting to see if it was solved in the new 2.0.0 firmware update...  |
|
|
|
I don't think there were any "security" related patches in the new firmware... they were mostly QoL (quality of life)... and adding support for ETH2.0 Release notes here: https://support.ledger.com/hc/en-us/articles/360010446000-Ledger-Nano-S-firmware-release-notesSo, if you're happy with how things are for now, and don't require/need/want ETH2.0, then it's probably find to just stick with what you have... Just be prepared for Ledger Live to bug remind you about updates being available!  |
|
|
|
10 sat/byte is the minimum for the ViaBTC accelerator, but why would you pay that minimum if it is enough to pay 6 sat/byte and get the confirmation in the next block? Insurance against the "next block" not being mined for over an hour... tens of thousands of transactions being dumped into the mempool with fees skyrocketing and your 6 sat/byte transaction ending up 20 megs from the tip.  And before you claim "oh don't be so dramatic", I have had something like this exact scenario happen before... more than once.  Sure, it doesn't happen often, but it can happen. If your transaction is somewhat time sensitive... 4 sats/byte extra for a "standard" transaction is only going to cost you an extra 1000 sats... Hell, it even buys you a little wiggle room just in case fees spike only a little. |
|
|
|
|
Not sure when the feature was added, if it was in this new firmware, or has been in a while... but I noticed that when you attempt to access a particular coin in Ledger Live now, it will automatically prompt you on the device to open that coin app...
Whereas, before it would just stick on the "Open Bitcoin app on your device" prompt in Ledger Live until you manually went and selected the coin app... now it just pops up with "Open Bitcoin App" with the "approve/reject" options on the device... kinda like when you try to open Ledger Manager and it says "allow Ledger Manager?", it now does the same thing with the coin apps.
Granted, it's a very minor thing, but a nice little addition to the UX, imo.
|
|
|
|
Perhaps you might like one of these to go along with your dice rolled, paper, metal engraved, WIF, seed mnemonic, tattoo on your foot (I kind of lost track of what you were actually recommending as the best way to create/store a key)  https://mcphee.com/products/tin-foil-hat |
|
|
|
So true, already with just the key, you can do every thing. What hardware wallet is doing more than any software wallet? Other than security extras?
In terms of being able to send/receive bitcoins? Nothing In terms of security... a LOT. A good hardware wallet provides and extra layer of security by effectively "air-gapping" your seed/private keys from the world... even if it is connected to an internet enabled device. A software wallet on an internet enabled device does not. Malware or someone with remote access can copy your wallet file, keylog your passwords etc. With a hardware wallet, they cannot... because the only thing the HW wallet does is receive unsigned transactions, and output signed transactions. The private keys are not accessible (even by malware)... at least, that is theory! |
|
|
|
I have a problem and maybe you can help me  So, many years ago (2013) i used multibit on my mac. I just opened multibit, create an adress and used it to transfert bitcoin. I never used a password. During 2 years i send bitcoins 1 time per month. One day (2015) i sended bitcoin on my multibit adress before open multibit. When i opened it, SURPRISE ! the bitcoin adress had change ! and there is no bitcoin money. When i checked the public key i see the transfert and bitcoin money. Sounds like you opened a different wallet file... MultiBit Classic (and HD) had the ability to create multiple wallet files. MultiBit Classic could also generate multiple keys/addresses, even tho it wasn't an HD wallet... it just generated "Random" keys that were unrelated to each other and not derived from a seed. When i try to recover wallet or key in multibit file, nothing ! so after read some articles, i exported private key ... (too late). Now we 're in 2021, i find my multibit wallet from 2015 with the new adress. I try software to recover old multibit file from when i created the wallet but not files .wallet or .key ... I have a chance to backup my old wallet ? If when you look at the old 2015 wallet with the "new" address... you don't see the "old" address on the "receive" tab, then it definitely seems like you opened (and subsequently kept) the wrong wallet file Unfortunately, if you are unable to find or recover any old .wallet of .key files, then the chances of being able to recover your "old" private key/address are pretty much zero |
|
|
|
-I think Bitcoin keyspace refers to the possible no. of blocks that could ever be generated till the end of time. (If u know some cryptography before reading about cryptocurrency & the idea of Bitcoin u'll have the impression that mining is similar like performing a brute force attack to break a plain/cipher pair)
The bitcoin "keyspace" has nothing to do with blocks or mining... It is referring to the "total set" of valid, unique bitcoin private keys... so, imagine if you had a (very bad) cryptocurrency, where the only private keys were {1, 2, 3, 4, 5, 6, 7, 8, 9, 10}.... then that would be the "keyspace" for your cryptocurrency... it has a size of 10. Bitcoin on the other hand, has a keyspace that goes from: 1 to n-1 where n = 1.1578 * 10 77More precisely, the private key can be any number between 0 and n - 1 inclusive, where n is a constant (n = 1.1578 * 1077, slightly less than 2256)
You may want to read the "Mastering Bitcoin" book... it gives a really good explanation of a lot of the fundamentals of Bitcoin. This particular chapter explains Keys and Addresses quite well: https://www.oreilly.com/library/view/mastering-bitcoin-2nd/9781491954379/ch04.htmlWhat is keyspace exactly? is this refering to SHA256 keyspace?
As above, it is the "total set" of keys that you're looking at... so it could be the entire bitcoin keyspace, or you can look at a specific subset if you wanted to for some reason (like you know the puzzle keys you're looking for are between 2 16 and 2 20... How is it that the puzzle transactions were created in different keyspaces? They are effectively in a subset of the Bitcoin keyspace... ie. they simply picked numbers from a smaller range. Can you create a bitcoin address in a specific keyspace? Of course... simply say "pick a number between X and Y" where X and Y are within the total Bitcoin keyspace...et voila, you have created a bitcoin private key within a defined specific keyspace and can derive the public key/address from that... but it isn't a good idea to, because you're losing the "randomness" by reducing the overall size of the keyspace that you're picking from. When bitcoin addresses are made is the keyspace they are in random, or is there a preferable or more pseudorandom range that they are likely to appear in?
Bitcoin addresses are not "made"... they are derived by (hopefully) randomly picking a private key... then the public key is derived from the private key... then the public key is converted into an address using SHA256, RIPEMD160 and encoded with Base58 etc. Again, read: https://www.oreilly.com/library/view/mastering-bitcoin-2nd/9781491954379/ch04.htmlIt will explain things much better than I can!  |
|
|
|
What should I do if I need import a new private keys in my new wallet but my blockchain is pruned?
You either don't import new private keys... or you don't run in pruned mode. Attempting to do both is going to cause issues. If you import to a pruned wallet, you will need to either rescan (which will require redownloading and reprocessing the entire blockchain) or accept that your wallet may not show an accurate transaction history/balance for that particular address or addresses. If you think you're going to be importing private keys often (multiple times), get more storage and don't run pruned... or use a different wallet like Electrum that will allow you to import keys without storage/rescan penalty. |
|
|
|
I am surprised that more major pools don't offer similar services.
I would suspect that: 1. It takes a bit of effort to implement 2. In general, people with stuck transactions are like that because they don't want to pay high fees, so aren't likely to part with large sums of cash to push a transaction through. 3. If you had that sort of money to spend on getting a transaction sent, you'd just pay a high fee to start with So, personally, I don't think it would be much of a money maker at all... sure, you'd get the odd customer here and there... but making ~$300 on an accelerated transaction when you get US$350K+ per block is nothing... I'm not sure the ROI on trying to implement the payment/queueing system and messing with the pools mempool/transaction selection algorithm is really worth it. |
|
|
|
Aside from the fact that trying to find banks/services that actually offer safety deposit boxes is getting harder and harder (most new bank branches being built don't include them, and a lot of older ones are being disestablished)... then sure... splitting up your seed and storing it all over the place is "one way" of securing your seed backup. However, say that it is "pretty much ideal for just about everyone" is demonstrably false... what if you live in a country where the banking system doesn't have safety deposit boxes? Or you live in a sparsely populated area where there is only 1 bank within 200 miles of where you live? what if you don't trust banks? What if you read this: https://www.nytimes.com/2019/07/19/business/safe-deposit-box-theft.html ? There are literally infinite ways that one can store their seed backup phrase... using paper, using metal plates, using cryptosteel like devices... in one piece, in multi pieces... in plain text, or encrypted, or using shamir secret sharing methods... then factor in all the places you can store it... on a post-it note on your monitor, in your drawer, under you bed, in a book, in a safe, buried in your garden, in your brain... etc etc etc. As you have been told M.U.L.T.I.P.L.E. times... find a method that YOU are comfortable with and allows you to sleep at night... then use that. Don't worry so much about what anyone else is doing. We have no idea about your personal situation, how much crypto you're holding, what sort of area you live in, what your associates are like etc... so we cannot accurately assess the "risks" that you have... only you can do that... so assess your risks, and then take steps to mitigate them. If that means you think you need to break your seed in multiple pieces and store it all over the country... then so be it... go and do that. Asking rando's on the internet if that is a good plan is a complete and utter waste of time. Is breaking it into multiple pieces and storing it all over the country "secure"... yes... should you do it? only you can answer that. |
|
|
|
what format are pvt keys starting with
0014
I want to sweep these remain keys with some balance in them..but still cant get these out of core wallet in a transaction.
I want to sweep them into electrum but can find what format are they?
Perhaps a worked example will help demonstrate things slightly easier... when you do the dumpwallet in Bitcoin Core, you will receive a text file that looks something like this at the top: # Wallet dump created by Bitcoin v0.21.0
# * Created on 2021-05-06T20:36:15Z
# * Best block at time of backup was 0 (000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f),
# mined on 2009-01-03T18:15:05Z
# extended private masterkey: xprv9s21ZrQH143K3sXtTbREX6etUygbEAdZvbAcf9G893efunoDMEfYdrQDjmkGTqWMkj3CShGj2KFSDy4KnQLfsuZj3hQNuii7j3ykNVEb4i7
KysRpRgfFZxfnMWFAhzhXGH65fnFLvp3iJ5is2NX8qsftWWogVHd 2021-04-17T03:53:24Z reserve=1 # addr=bc1qqrp39satjv7ypx49q03437r4kwsnxpqr94p738 hdkeypath=m/0'/0'/290'
KwDuVUDeS7F1HMRYiFwz7k1zquLsqwgTg4Ywu97PgUidD15er7v8 2021-04-17T03:53:24Z reserve=1 # addr=bc1qq9sw3zz03lslr83v5jt02r3hhm8vmx7zqkgxcz hdkeypath=m/0'/0'/713'
L1Z6nLWgLUeLJZXdepwBptiBppxDaNMszB4dSWvkPTXkTDo3N1or 2021-04-17T03:53:24Z reserve=1 # addr=bc1qq8x6ym7mwdjphqh6ae8yj8qw0z9875n8mrl9tq hdkeypath=m/0'/0'/672'
...
and then about halfway down the file... the format will change to something like this: ...
L3dchw79ZyrPxvi85ujnrE3MQJzP4VCk4qrLQGqepHvAeFCXzUAv 2021-05-02T00:34:58Z reserve=1 # addr=bc1qu3e3xacqe0kjzrtq2p7jxtw9q83vlqvwctlpgt hdkeypath=m/0'/0'/1004'
0014b8661d5cc456b8e540600ffa8e51c6fffae4126f 0 script=1 # addr=31hGNmRu2vPRBK39BVKGCkJHasxUrKDe6i
0014213df6e25c0eb07482e378390ac71ac32e5fbcd3 0 script=1 # addr=31iV72rvQP68j7Fw5bC1HfiktEqyEWSdVe
00143a891a3850f0e1191e65b9807e13b88593cef356 0 script=1 # addr=31iyv6J7MrNBgpEAqQjpxLtdz64CyYqHow
0014071d27b5d13ba1526cfcad6cd5f8ab9767242c3a 0 script=1 # addr=31jX71XANGb63uK4JA2WCt3PomJn6GLppc
0014b6bec2d025a2f09d062b1eedabb914f764e07b11 0 script=1 # addr=31mqVD6fnpUp822H4cuizDNxWhWPYbim8j
0014110d9569de104f68802ab915a570c365baf3db9c 0 script=1 # addr=31nf63rr8NJY9gQUxjk89uJU5qkEpzsmwe
00143307bd876ac38e9f496b75bb55dfcf79a36efdc7 0 script=1 # addr=31pBvcAgFLocUotrjNoMnYsoLAGDyfJFf4
0014fb27c6b8e0fd067d94875edb9aab9caa1c1ce992 0 script=1 # addr=31pWZCNLZSXgEaRAZZMaFDXoagje9o3UNF
...
The 0014 "keys" are not actually keys, as nc50lc noted, they are redeem scripts for your "P2SH" addresses... And, for the purposes of importing to Electrum, they are not required. The standard WIF private keys in the top half are all that you need to shift to Electrum: So, as I'm sure you're aware... you use the "Import Bitcoin address or private keys" option:  If you click the "info" button, it will give you some guidance as to which "prefix" you need to use with the WIF private key to generate the address you require:  as you can see... to generate: - the old style legacy addresses ("1"-type), you use p2pkh- Nested Segwit ("3"-type), you use p2wpkh-p2sh- Native Segwit ("bc1"-type), you use p2wpkhSo, you can either create separate wallets for each type:  =>   =>  Or, you can just create one wallet with all the different types in it:  =>  NOTE: I didn't import the old school legacy (p2pkh) addresses simply because I was in a rush |
|
|
|
The passphrase is no problem as I already know it. I wonder if the salt and iteration are viewable within the wallet file? How do these various scripts find them?
The "mkey" data stored in the wallet.dat is unpacked as follows: encrypted_master_key, salt, method, iter_count = struct.unpack_from("< 49p 9p I I", mkey)
So, it's actually a 48 byte record called the "encrypted_master_key", the 8 byte salt, the 'method' (should be a 4 byte unsigned Int value 0) and the iteration count (4 byte unsigned Int). Then, the 48 byte "encrypted_master_key", is actually parsed as: iv = binascii.hexlify(encrypted_master_key[16:32])
ct = binascii.hexlify(encrypted_master_key[-16:])
first 16 bytes are ignored? 2nd 16 bytes are the "iv" (initialisation vector) last 16 bytes are the "ct" (cipher text) The hex that the walletinfo.py script outputs is: s = iv + ct + binascii.hexlify(salt) + iterations
return s
So it is actually iv (16 bytes) + cipher text (16 bytes) + salt (8 bytes) + iteration (8 bytes, it gets padded out from 4 bytes) I assume this is because the OpenCL portion of that project is expecting the data in this format (to test passphrases) with. |
|
|
|
This is a lot complicated than it looks then. I mean i thought the passphrase would be protecting you with your hidden wallet but if you use ledger live which i assume majority of people do... then you can't do that.
It does protect your hidden wallet... The fact that you say log into ledger live and click on add accounts and thats all it scan everything, how does even this passphrase even protect you much then?
Because it doesn't work like that... When you unlock your Ledger Nano S/X, you do it in one of three ways... 1. Normal PIN... this unlocks the "default" wallet (ie. 24 word seed) 2. Using "2nd PIN" (if enabled)... this unlocks the "hidden" wallet (ie. 24 word seed + "saved" BIP39 passphrase) 3. Using Normal PIN + "Temp Passphrase" functionality... this unlocks a "hidden" wallet (ie. 24 word seed + entered BIP39 passphrase) Assuming you have no accounts loaded in Ledger Live (ie. new install, or you deleted everything or "Reset" Ledger Live)... when you "Scan" accounts... Ledger Live will only be able to "see" the accounts that are associated to the current "seed"... which is dependent on how you unlocked it (PIN, 2nd PIN or PIN+temp passphrase). If you leave those accounts in Ledger Live... disconnect your device and then reconnect it and unlock it with a different method... you'll then be able to see the accounts of the previous method AND the new method. So, if you want your "hidden" wallet to stay hidden... 1. Setup Ledger Live with your "Normal" PIN wallet/accounts 2. When you want to see your "hidden" wallet, unlock device with 2nd PIN (or normal PIN + temp passphrase), add the "hidden" accounts 3. Do whatever you need with "hidden" wallet (check balance, get receive address, send coins whatever) 4. DELETE the "hidden" wallet accounts from Ledger Live5. Disconnect the device Now, if someone opens your Ledger Live... they'll only see your "normal" wallet accounts. This setup requires you to be methodical and remember to remove the hidden accounts if you ever add them... or, you could simply just completely reset Ledger Live every time you have finished using it and it will wipe everything for you. If someone forces you to hand over PIN, when they rescan in (empty) Ledger Live, they only see the "normal" wallet accounts... your "hidden" accounts will not show. |
|
|
|
Well Winklewoss Twins apparently store their seed in safe deposit places throughout the US.
Are you one of the Winklewoss Twins? If not, then it really makes no difference what they do... I see "famous"™ people do <insert activity here> all the time... it doesn't mean I would or should do the same... you know why? Because I have a brain and can think for myself. While it doesn't hurt to consider what other folks are doing... basing every single decision on what someone else is doing is not living your live... it's attempt to live other peoples lives. This usually ends sub-optimally... because you're not those other people... and most likely not in the same situation as them. |
|
|
|
However, they are quite expensive and AFAIK they only accept BCH which is a real downside.
Nope... while it defaults to BCH, they actually accept BTC, BCH and/or LTC  |
|
|
|
|
Show Posts
