Now my question is, is it possible to just set up and run electrum alone? Totally separate from my trezor? As I dont really want them linked but still be able to send and recieve from both
Yes... simply use the "File -> New\Restore" option in Electrum, select the "Standard Wallet" option and create yourself a new Electrum wallet that is not linked to your Trezor. Just remember that you will need to ensure that you write down and safely store the 12 word seed mnemonic that Electrum generates when you do this. |
|
|
|
Do you have to know if the coins in your Nano S wallet are in legacy address(es) (starts with "1")... or in a SegWit address(es) (starts with "3")? The only things I can suggest are relatively obvious: 1. Try and reset the Mycelium app on your device (clear cache only first... then try cache+data if that doesn't work)... note that clearing data will wipe ALL of the data for Mycelium app 2. Try your Nano S with another device (laptop/desktop etc) and try using the Ledger Live software. If #1 doesn't work, and #2 isn't an option... then you might be better off logging the issue on the Mycelium GitHub... |
|
|
|
LOL... 10/10 for observation skills... Just glad I'm not the only one who has done this sort of thing! hahaha  Guess you'll need to fire up the old btcrecover and use the seedrecover.py script to figure out what your mistake is... if you know at least one address (that is close to the beginning of the derivation path), it should be able to figure it out in a reasonable amount of time. |
|
|
|
I was fairly sure he meant LoyceV... After all, LoyceV posted the correct answer. All I did was expand on it a little bit. I don't expect any reward... just trying to help out where I can  However, if bigpoppa0008 did mean me... my address would be: 33o4MoDSFrfKSznHLBzwKigpTQvMiWWsHr  |
|
|
|
Perhaps the conclusion in this story is that users need to set up passphrase on hardware wallets, but this option is often recommended only to advanced users.
The passphrase is only a password that cannot be reset, and can be more "simple" compared to "password" standards because an attacker cannot try any passphrases without physical access to the device, and there is no way of knowing how many passphrases there are that contain anything of value. That isn't technically true... If you have access to the seed mnemonic, you can attempt to bruteforce passphrases. Granted, the algorithms required during mnemonic->seed->keys will slow things down, but if you use a stupidly simple passphrase, it would be possible for someone to bruteforce it in a relatively short space of time. The trick of course is to get hold of the seed mnemonic... which apparently has now been patched as well So, without physical access to the device (and knowledge of the PIN) or stumbling across someone's seed mnemonic backup... an attacker is going to struggle as things currently stand with the new patches. What I am encourage by, is that "whitehats" are actively trying to find these flaws (hopefully before the "blackhats" )... and the companies are doing their best to patch the devices to mitigate the vulnerabilities. |
|
|
|
Apparently this cannot be shipped to my country... from Amazon   And indiegogo supports shipping to my country but adds US$10 to the price... still, cheaper than CryptoSteel... but starting to push the total cost up a bit. |
|
|
|
Wait... did Electrum not give you a "BIP39 checksum: failed" message on the seed input screen?  That would be extremely odd if it didn't... I mean, I know it will happily let you use seeds with a "failed" checksum when you have BIP39 seed selected... but it should at least warn you! Or were you trying to restore on the command line on the Pi? |
|
|
|
I tested it... it is definitely m/0' for the wallet I created today. The "full" path to the first address is actually m/0'/0/0... Electrum seems to automagically add the first "0" when it starts looking for "receive" addresses... and then the 2nd "0" for address at index 0. If you use bitcoinj and do a dump with --dump-privkeys, you'll see something like this right at the end of the dump: addr:1K2rCAnAvqHETgG9rHrzysJ4PPue9Lr7EQ hash160:c5cbbe73ae2c4d1ce0eaaa5303b27d9c0d120292 (M/0H/0/0)
That is the address I see in the app when I click the QRCode to see my receive address... and the address that Electrum generates when I use m/0' as the derivation path when importing For reference, the full dump of my testing wallet is: Wallet
WARNING: includes private keys!
Balances:
0.00 BTC ESTIMATED
0.00 BTC AVAILABLE
0.00 BTC ESTIMATED_SPENDABLE
0.00 BTC AVAILABLE_SPENDABLE
Transactions:
0 pending
0 unspent
0 spent
0 dead
Last seen best block: 567262 (2019-03-16T01:11:02Z): 0000000000000000001da8b54a299a642ba92d50f0d20078f9781c1accd9be9d
Keys:
Earliest creation time: 2019-03-15T20:52:59Z
Seed as words: shed cruel trap raccoon planet lecture harvest night narrow grass surround noble
Seed as hex: 3bd7c9cc0397b3023ba83fcbd1deec5fef1c68a3ed947ee7a326f186fe005f5f6c58040d39df3f32864f4fb2b8557caa4bc41dde1e6b2eb639d0fa4ff5a45815
Seed birthday: 1552683179 [2019-03-15T20:52:59Z]
Ouput script type: P2PKH
Key to watch: xpub69G3fM82T2Xmx9VsUeeYWnmYRGGrQrD3pCe2msvVDf4MhRZ5j9HsnFmJvpMBmMX9wZJ8JdSwzU8am2MA8RSttzZ1eUEHMuVtCii9JkR7yLy
Lookahead siz/thr: 100/33
addr:1J1eAbKcRQTsgwzhn8buqUM8pPQ8A2duRm hash160:ba99299424eda8ed8b453835738850ade43fcea0 (M, root)
DeterministicKey{pub HEX=02f0a36dde523f7d7cff5232f3f0ddaf61778e40ee1c47cc3e8cb82b8c46300fa9, priv HEX=c8866c5513583249996bc6b0d05571d2322e7c7f85d6fdbe00fa47d966bbba57, priv WIF=L3wWGbkcaQeG5iCJcnJrXgwEovMLn2HsJktG4TqtvvH1c3hg4wbG, creationTimeSeconds=1552683179, isEncrypted=false, isPubKeyOnly=false}
addr:1LDUZuuv37oPWE1NU2EnFjvVVgrTEe3XtF hash160:d2c664c1efad9bb8ba6d44a5893bd7c911a67897 (M/0H, account)
DeterministicKey{pub HEX=03598fe12ea45f4f669242079f59b6233ec0a2ae3a73162bf650c8afebab0b2fd7, priv HEX=2a8c3c0b102a27142fffbc8d271f242ea246cbb3f4a797bef727c437508506aa, priv WIF=KxeRDArBfhAPyTmzQgRfDua5tX1p9ogh2an9B358sMbnMyNJfLSw, isEncrypted=false, isPubKeyOnly=false}
addr:14qUE7sA8ZvAYXsxi3RhmWfMVKvwjiYQLv hash160:2a13121f118f0861f5a9720601b5c2698564c2ec (M/0H/0, external)
DeterministicKey{pub HEX=039f5643f48c77d434bfbdbcac72fe72dfef272caf7db901a7932963b4ab041180, priv HEX=aca6d3c371812845e01af4ff6dfcf1a08aa69ade7d41a1d437827775c3f8658f, priv WIF=L31KhNsP3orEfLRZFAzTPAcuUa7HttyAN1iA3pTsU3DZjPAuZPTn, isEncrypted=false, isPubKeyOnly=false}
addr:1P1tUWAYAxv68wA8nfmXA1fjQUM6M3mdMF hash160:f17dbc58d385fc27047904337c3fe79f3421fdd2 (M/0H/1, internal)
DeterministicKey{pub HEX=034049298d152957146885596e731e5d94b80013558341fe82648562f19cb6e745, priv HEX=579c14f425a527cf9adfcdd4f58286dd9af9bc0586976c0e47dbcbd5e44880d8, priv WIF=KzA1guaT4BmrJsW7n4DFx7kn7BTMCLkEim3tnqbxd6Qeawdy1voR, isEncrypted=false, isPubKeyOnly=false}
addr:1K2rCAnAvqHETgG9rHrzysJ4PPue9Lr7EQ hash160:c5cbbe73ae2c4d1ce0eaaa5303b27d9c0d120292 (M/0H/0/0)
DeterministicKey{pub HEX=02269536b52e9f2ca55b60f191b04fee96454fc9c7da046e2520cf0723456cafed, priv HEX=9b32a1c99c54379935bef01c8ab56015f7280337e7f200b50db8f1c9166c03cc, priv WIF=L2RPsKyWe1pERXbxLRmNJrT99Uv25nJokNNLCf6TsSZ4jQKdoavV, isEncrypted=false, isPubKeyOnly=false}
|
|
|
|
I believe the commandline argument for that is: --satoshi-portYou either start Armory and include that command with the port number, or put it in your armoryqt.conf etc. More details in the Armory FAQ on btcarmory.com |
|
|
|
|
Ahhhh ok, right, you extracted the seed from the backup wallet file by decrypting and then dumping it out using bitcoinj... fair enough.
In that case... in Electrum, try using "Legacy" as the script type, and setting the Derivation Path to: m/0'
That should generate the correct addresses.
|
|
|
|
Right. Either the 8 words are the privkey (which is possible if OP did some brute forcing - I've done something similar myself, several years ago now, for a puzzle), or it's a hash.
Either way, it's finding the right 32 chars. I have been assuming that they are from the question itself, like others have been.
Why would that require brute forcing? You "simply" pick 8 words that total up to 32 chars as your answer: WeCreateAnAnswerThatIsEightWords Then pick whatever method you like to use that as your private key: char->hex method... which yields private key: 5765437265617465416e416e737765725468617449734569676874576f726473 (18LpdmS7UPHRPsNmD384LRRawHjVXprJy1) or brainwallet (sha256) method... which yields private key: 8EAFEFFE8CEE0E1E43A53314FFEC31BE09B378A4E733A516BBBAEB177CC151FD (15idakESXkA4N5Uyjts2xTFupBLD9Pibz2) You can then send your X BTC prize to the address you just "created" The problem we have is that there is no definitive answer as to whether we should be doing "char->hex" method or "brainwallet" method. I guess the solution to that problem is to simply check both! |
|
|
|
Yeah, trying to follow the http ://keys.gnupg.net... link also redirects me to the https ://analytics.sumptuouscapital.com... page ??!?  Very strange... I suspect some sort of DNS issue somewhere along the line... possibly because my local router is configured to use OpenDNS? Just FYI, out of all the GPG keyservers that are listed when you search "gpg keyserver" on Google, the most reliable I've found seems to be: https://keyserver.ubuntu.com/ Most of the others return errors |
|
|
|
There are: - Fingerprints... basically the FULL length code, in this example: 0x6694d8de7be8ee5631bed9502bd5824b7f9470e6 - Long "Key ID"... the last 16 chars of the fingerprint: 2BD5824B7F9470E6 - Short "Key ID"... the last 8 chars of the fingerprint: 7F9470E6 Clear as mud? The KeyID stuff is explained quite well here: https://davesteele.github.io/gpg/2014/09/20/anatomy-of-a-gpg-key/ (scroll down to the KeyID section) |
|
|
|
... and now I'm stuck with a seed on my phone and no idea how to use it (I'm restoring on my raspberry pi for security reasons, can anyone help me the schilbach wallet fees are a bit high).
What exactly are you trying to restore from? As far as I know, Bitcoin Wallet for Android does not provide a seed mnemonic at all... it simply uses (encrypted) backup files? Are you sure that this "seed" that you have is from the Bitcoin Wallet for Android? Or did you get it from another wallet? |
|
|
|
Ledger creates either Legacy ("1-type" addresses) or "Nested" SegWit (aka P2SH-P2WPKH, "3-type" addresses) wallets. However, Electrum, by default, will attempt to create a "Native" SegWit (aka P2WPKH, "bc1" bech32 address) wallet... even when you use a BIP39 seed, it defaults to the "native segwit" option on the Derivation Path selection screen. To generate the same wallet as your Ledger and/or Trezor, you will need to select either Legacy (if your addresses start with a 1) or the "p2sh-segwit (p2wpkh-p2sh)" option if your Ledger addresses start with a "3":  |
|
|
|
is it basically possible to make sure that a transaction is broadcasted through my own group of nodes I'm running?
Even if there is some sort of propagation issue stopping the transfer of your transaction across the network... You can 100% guarantee that each of your personal nodes knows about any given transaction by simply using the sendrawtransaction on each node (via bitcoin-cli or console in GUI) passing in the "raw hex" of the transaction. This will guarantee that the transaction is added to the local node's mempool, assuming it is a valid transaction |
|
|
|
I'm running bitcoind/ bitcoind -regtest on Windows 10 and am already able to use bitcoin-cli -regtest along with json-rpc methods to perform basic operations and get balances etc. When I try to do this programmatically on python 3 using Jeff Garzik's python-bitcoinrpc package (https://github.com/jgarzik/python-bitcoinrpc) I get a modulenotfounderror. However, my pip3 freeze shows python-bitcoinlib==0.10.1 and also python-bitcoinrpc==1.0. What am I doing wrong? Well... according to the install instructions on github... it looks like this might be Python 2 only... change the first line of setup.py to point to the directory of your installation of python 2.*
Have you tried it with a Python 2.7 install? |
|
|
|
I still can't see any Amazon/Ebay links... the only "Buy" link I can find takes me to "Weidian.com"... which is all in Chinese $20 is a fantastic price point compared to cryptosteel... and I think it's possible you could sell quite a few units... if users can actually buy it! |
|
|
|
That depends on what you mean by "play with the system"... If you're not trying to manipulate blocks or other data files, then I don't see how you can do anything that would really warrant needing a backup. In any case, if anything goes really bad, you can always simply delete all the data files/blocks/chainstate etc and then simply re-sync... However, if you have plenty of space (like a spare ~260Gigs laying around) and feel like backing it all up... it won't hurt. Making a full backup takes as long as it takes to copy the ~260Gigs to your backup location... whatever that might be (external drive, internal drive, network storage etc) |
|
|
|
Yeah... I've never really been a bit fan of "upgrading" Windows OS installs... it is usually a lot less hassle in the long run to wipe the computer (or get another harddrive) and start with a fresh install. Anyway, glad you managed to get it sorted finally! Good luck with the sync |
|
|
|
|
Show Posts
