I imagine, for the purpose of privacy, you could replace the wordlist to one which contains alphanumeric gibberish or even grammatically-correct text but with the wordlist in a scrambled order, so that in the event that people find your phrase and try to recover it, they would be confounded by its inability to be imported into normal Electrum builds.
o_e_l_e_o is correct. If fact, as I noted, you can import that phrase to Electrum without issues. You can take the bunch of bananas (pun intended  ) nc50lc has posted above As the standard unit of scale, I used " banana" to count the number of words in my custom word list. To newbie readers: do not use it, it's only for testing purposes. |
|
|
|
what if I only have the seed and switch my wallet to Sparrow,
I could imagine that some addresses are not displayed, how do I make these addresses visible on another wallet if i only have the seed?
How does it work with a Watch Only address, do I just need to insert the xPub and then i can see all the coins from every receiving and change address that come from this xPub?
Sparrow wallet has an " Addresses" tab where the change and receiving addresses are listed. You can change the gap limit in " Settings->Advanced->Gap limit" to view more in case it isn't synced. For watching-only, it depends on the master key imported to create the watch-only wallet, but mostly all, including electrum, the 'xPub' is the " account extended public key" so it should be able to derive both the receiving and change addresses. |
|
|
|
for what are these keys and what can i do with these keys.
BIP32 Root Key
Account Extended Private Key
Account Extended Public Key
BIP32 Extended Private Key
BIP32 Extended Public Key
Are you familiar with 'derivation path'? yes? If so, here's what it looks like if you plot those master keys in BIP44's standard derivation path for example: m/44'/0'/0'/0/address_index
BIP32 Root Key/44'/0'/Account Extended Private Key/BIP32 Extended Private Key/address_index" BIP32 Root Key" is the master private key derived from your hdseed ( 'BIP39 Seed' in iancoleman). " Account Extended Private Key" is the extended private master key at the 'account index'. " BIP32 Extended Private Key" is the extended private master key at the 'chain index'. " Extended Public Keys" are just the pubKey pair of those prv master keys. Notice that if you change the " Account", the 'Account Extended Private Key' will change as well. And if you change " External / Internal" ( chain), 'BIP32 Extended Private Key' will change but the master keys at higher hierarchy wont change. |
|
|
|
-snip- Since there are many miners competing with each other, what's confusing me now is that what if these miners get the same answer at the same time?
That mathematical puzzle's answer is the Double SHA256 result of the block header. For that to happen to competing miners, we're looking for a SHA256 collision which is highly unlikely to happen with the Bitcoin network's total hashrate. |
|
|
|
This particular question is unclear to me: is it the wallet or the nodes that generate transaction fees? I understand that transaction fees are generated, but how? Please help me out.
There's no particular entity that sets the transaction fee. It's the wallet's estimation depending on different or unique factors; or what's set by the user. For example, Electrum has 3 transaction fee sliders which work differently: ETA which uses complex algorithm based from the newest blocks and mempool. Mempool which is solely based from the size of your server's mempool. Static which is a set pre-set values. For generation of " fee", it's simply the difference between the inputs' and the output's amount. The " fee rate" is the 'fee' divided by the transaction's virtual size. |
|
|
|
Ah! Thanks for all that. I think it's fair enough to close this thread.
You can close it yourself by using the small " lock topic" button at the lower-left hand side of the page. |
|
|
|
I initially thought like 300 MBs was the limit after which the purging would start almost immediately to keep below 300 MBs but now that It's way above that, so;
mempool space is probably keeping track of all unconfirmed transactions but has its own algorithm to compute the default " Purging" fee rate. On a side note, " observing the mempool" is quite a tedious task since each node has its own unique mempool. Additionally, for the 14day default expiration, some nodes may have set it higher so transactions may not get totally dropped after 14days. |
|
|
|
and there's an interesting answer that identifies the "S" as "Spend", he didn't included a source though.
Small makes more sense though since these are indeed "small" strings that are used to derive a private key -snip-I think it's just following the ( old) standard paper wallet print format which labels the private key as " Spend". Notice that in most paper wallet generators or some printable wallet private key exports, the private key is printed with the word 'Spend'. |
|
|
|
-snip-
From my investigation I can see that bitcoin and sent in batches. I bring it up here because I did not get right. I appreciate OELEO that gave me a link that guide me I now understand that batches can also called output Are you perhaps using a " centralized wallet" or exchange? Because withdrawals from those are usually sent in batches; and it's not initiated by you, but by their system. The reason they do that is because it's cheaper to send transactions with multiple outputs than multiple transaction with single output and change. Normal transaction outputs are commonly just the recipient and change. |
|
|
|
-snip-
Curiously, there are some different wordlists in electrum repo.
...and to satisfy that curiosity, it'll still work if they decided to use it even if the words aren't included in BIP39 wordlist nor for having 1626 words. Electrum's seed doesn't actually need a fixed wordlist, you can even edit the english.txt with your own set of words and it will produce a valid seed ( given that there's enough to produce a valid one). e.g. ( SegWit - Can be imported to Electrum): banana110206 banana110312 banana021413 banana061112 banana030713 banana130608 banana020311 banana010311 banana010306 banana101112 banana020705 banana091106 |
|
|
|
Does anyone know this problem and has a solution to it?
According to you other thread, your Ledger Nano X is new. So, have you updated its firmware yet? Because the device that you've received might have an outdated firmware. |
|
|
|
The private key is equal to one. However, for 3JvL6Ymt8MVWiCNHC7oWU6nLeHNJKLZGLN it is possible to sweep coins, but for 33q2i3GDkpHFAXnD3UdBsKhxzg7pvwAqtN it cannot be done. Why?
The reply above is correct. And to answer this question, 3JvL6Ymt8MVWiCNHC7oWU6nLeHNJKLZGLN is derived from the compressed public key of the private key 0x01 While 33q2i3GDkpHFAXnD3UdBsKhxzg7pvwAqtN is derived from the uncompressed public key. It's published in BIP143 as the default policy: github.com/bitcoin/bips/blob/master/bip-0143 |
|
|
|
It does say create unsigned. I am newer to core, so that means it will allow a psbt?
Yes, it can create partially signed raw transaction ( without any signature) but cannot sign since it only contains master public key. So it can't spend your bitcoin. |
|
|
|
What are the possible way forward to put fund online and be able to send micro funds to the paper wallets ?
'Close all' should've have worked if there's no issue with your node. You can try post it as a new issue in GitHub and see if the developers can help: https://github.com/rootzoll/raspiblitz/issuesBTW, I checked your node in 1ML site and your channels seem to be active still ( excluding onion): 1ml.com/node/03443d4d2248e25ed0bc726aaba3a9a858561f452f62e3c3baa36abe5d99e74d65Alternatively, try to find if there's a " Force Close" option or after getting the developers' opinions. Take note that force closing channels will lock the funds for a few days before you can spend them. |
|
|
|
I want so send small satoshis to 20 btc address that a paper wallets, the values are small and the security is not of prime issue. This is for educational purpose.
What do I need to do to be able to send fund out satoshi from the LND wallets to my 20 receivers?
You can't send funds from your channel to bitcoin addresses. The funds has to be on-chain first to be able to send to paper wallets. For that, you'll have to close the channel and proceed to create an on-chain transaction with multiple outputs ( if Raspiblitz doesn't support 'pay-to-many', use a wallet that can do so). Since you only have 1 channel open, " close all" will do: https://github.com/rootzoll/raspiblitz#close-all-closing-all-open-channels |
|
|
|
However, the balance is spendable on core. I want it to be watch only on core. I've tried to add disableprivatekey=1 in config, doesn't work.
I've tested it, the wallet in Bitcoin Core isn't spendable since it shows " private_keys_enabled": false," in getwalletinfo command. You can also check the Send tab in the GUI if it has " Create Unsigned" in place of the " Send" button. |
|
|
|
-snip-
My reply isn't about the overall security but the difference between the randomly generated seed phrase and the one with edited word as a response to his follow-up question. |
|
|
|
The question is still unclear from me. Will it be less safe to change a word and the checksum of a randomly generated seed (by myself or by hardware wallet), or it won't make a difference?
Thanks!
It's less safer in terms of RNG. Because you basically reduced it from 256-bit. One word is approximately 11-bit so if you've replaced one word, you've reduced the number of randomized portion of the seed by that amount. But changing only one word out of 24, IMO isn't much of a safety issue, I'm not recommending it though. |
|
|
|
The idea would be to avoid trusting the hardware wallet seed.
Your hardware wallet's seed is generated randomly in the device itself, not by the manufacturer. The only trust issue is if the hardware's RNG is bad or rigged which is never the case in genuine famous hardware wallets. If your hardware wallet came with a pre-generated wallet or seed phrase, avoid using that device entirely. |
|
|
|
|
Show Posts
