Have you (or are you) planning on putting your Python BIP38 code up on GitHub or similar?  Might be useful for someone in the future if they have don't have to "reinvent the wheel"  |
|
|
|
But, we should never loose site of telling them that it's not optimal and there will be more issues doing it that way. And possibly it might be better to save up a little more and do it a better way.
I concur... just because "you can", it doesn't mean that "you should". I got as far as "AWS EC2 EC2 T3 Micro Instance" in the OP and already knew what the likely cause of this issue was. Running on anything less than a "T3.medium" would be asking for all sorts of trouble. |
|
|
|
|
Indeed... but it's impossible to say one way or the other. The code is closed source and cannot be examined. I'm not sure if Exodus wallet encryption was or is as bad as other wallets (like Jaxx etc) that have done stupid things like use a 4 digit PIN for encryption or store the phrase in plaintext etc.
However, it is also impossible to know for sure what the user has or hasn't done either. It's possible they used the same recovery phrase in another (compromised) wallet/website... it's possible they stored their seed in an email or on a cloud drive or as a screenshot... it's possible their computer was compromised etc.
|
|
|
|
... Let's go back to now, I don't remember that I made a password in the first place, but when I run the wallet it asks me for the password.
When exactly is it asking for a password? Bitcoin Core only prompts for a password when you are attempting to do something that requires access to the private keys contained in the wallet.dat. For instance, create and sign a send transaction, signing a message or using the dumpprivkey or dumpwallet commands on the console. It does not prompt for the password when you start Bitcoin Core or just try to load the wallet. So, when is it prompting for a password? and can you please provide a screenshot of this? |
|
|
|
... My sister claims they could see it in some separate "legacy wallet" showing up on the trezor interface??? It is not clear to me exactly what she is talking about and I don't think they have any screen shots. But I can interrogate her further on this if necessary.
By "Legacy Account" they're probably referring to this:  The Trezor Suite has a similar section:  Have you been using the Trezor Suite or the wallet.trezor.io website to connect up the Trezor and investigate the available accounts? |
|
|
|
-ERROR - 09:57:27.140: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:1503) Headers DB has no block at height: 0
-ERROR - 09:57:27.140: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:1483) No headers at height 0
-ERROR - 09:57:27.156: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:445) Missing file map for output scan, this is unexpected
-ERROR - 09:57:27.156: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:447) Has the following block files:
-ERROR - 09:57:27.156: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:451) Was looking for id #4294967295
Looking at the error messages from your ArmoryDB log file, it seems that your Bitcoin Core node is running in "pruned" mode... Unfortunately, Armory will not be able to work correctly with a pruned Bitcoin Core node. Do as nc50lc has suggested and ensure that Bitcoin Core is not pruned... and then get Bitcoin Core fully synced. Note that this will require ~400+ Gigs of free storage space for Bitcoin Core to download and store the block data. |
|
|
|
"You can also try that to check if you can reproduce those addresses into your blockchain(dot)com's unused addresses list." Could You, please, send the hint for this to be managed?
Note that if you clicked the "trash can" icon to delete the address in the blockchain UI:  You won't be able to "recreate" that address in Blockchain. Having said that, it shouldn't matter... if the address was from that wallet, it should automatically show in your balance and/or in the "used" addresses section (You may need to click the "Reveal Addresses" button) All of this is under the "gear" icon and then "Wallets & Addresses":  Then click the "manage" link on the right hand side of the screen for the wallet you're trying to get the addresses from:  Speaking of... how many wallets are actually showing in that list for you? Do you only have one or are there several? |
|
|
|
decided to update to 0.21.1
how exactly did you "update" bitcoin core? It sounds like the location of the bitcoind binary is no longer included in your PATH. Do you know where the bitcoind binary is located? |
|
|
|
Is this specifically the Armory Database directory... or is it ignoring the Bitcoin Home Dir as well? |
|
|
|
Have been trying to get Armory TESTNET setup again after a reinstall... ArmoryDB is consistently encountering a buffer overflow error while scanning the transaction history: Log file opened at 14:02:11.000: C:\Users\HCP\AppData\Roaming\Armory\testnet3/dbLog.txt
-INFO - 14:02:11.000: (e:\users\goat\code\armory3\cppforswig\main.cpp:32) Running on 12 threads
-INFO - 14:02:11.000: (e:\users\goat\code\armory3\cppforswig\main.cpp:33) Ram usage level: 50
-INFO - 14:02:11.000: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:915) blkfile dir: E:\Bitcoin\testnet3\blocks
-INFO - 14:02:11.000: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:916) lmdb dir: C:\HCP\jared\AppData\Roaming\Armory\testnet3\databases
-INFO - 14:02:11.000: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 14:02:11.032: (e:\users\goat\code\armory3\cppforswig\bdm_server.h:263) Listening on port 53481
-INFO - 14:02:11.032: (e:\users\goat\code\armory3\cppforswig\bitcoinp2p.cpp:947) Connected to Bitcoin node
-INFO - 14:02:11.032: (e:\users\goat\code\armory3\cppforswig\noderpc.cpp:57) RPC connection established
-INFO - 14:02:11.032: (e:\users\goat\code\armory3\cppforswig\blockdatamanagerconfig.cpp:919) waiting on node sync: 99.9999%
-INFO - 14:02:11.032: (e:\users\goat\code\armory3\cppforswig\noderpc.cpp:425) Node is ready
-INFO - 14:02:11.032: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:1108) Executing: doInitialSyncOnLoad
-INFO - 14:02:11.063: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:199) Reading headers from db
-INFO - 14:02:13.141: (e:\users\goat\code\armory3\cppforswig\bdm_server.cpp:1121) registered bdv: 4c90f9ec131d57ab02e5
-INFO - 14:02:21.875: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:238) Found 2098850 headers in db
-INFO - 14:02:33.188: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:64) Rewinding 100 blocks
-INFO - 14:02:33.188: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:71) updating HEADERS db
-INFO - 14:02:33.219: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:493) Found next block after skipping 13363bytes
-INFO - 14:02:33.250: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #200
-INFO - 14:02:33.250: (e:\users\goat\code\armory3\cppforswig\blockchain.cpp:248) Organizing chain
-INFO - 14:02:33.360: (e:\users\goat\code\armory3\cppforswig\blockchain.cpp:370) Organized chain in 0s
-INFO - 14:02:33.360: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:76) updated HEADERS db in 0s
-INFO - 14:02:33.407: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 14:02:33.407: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:1231) verifying txfilters integrity
-INFO - 14:02:34.219: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:1314) done checking txfilters
-INFO - 14:02:34.329: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:1891) Enabling zero-conf tracking
-INFO - 14:02:34.454: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:401) Starting address registration process
-INFO - 14:02:39.032: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #0 to #206498
-INFO - 14:02:46.125: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #206499 to #266421
-INFO - 14:02:52.891: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #266422 to #348885
-INFO - 14:02:59.641: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #348886 to #500981
-INFO - 14:03:05.016: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #500982 to #584256
-INFO - 14:03:12.157: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #584257 to #606023
-INFO - 14:03:22.235: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #606024 to #624331
-INFO - 14:03:30.485: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #624332 to #627777
-INFO - 14:03:39.297: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #627778 to #631898
-INFO - 14:03:46.500: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #631899 to #715747
-INFO - 14:03:54.485: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #715748 to #723331
-INFO - 14:04:00.844: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #723332 to #892111
-INFO - 14:04:07.188: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #892112 to #919668
-INFO - 14:04:14.250: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #919669 to #947235
-INFO - 14:04:20.954: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #947236 to #1012869
-INFO - 14:04:28.094: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1012870 to #1035245
-INFO - 14:04:34.016: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:52) no history to scan
-INFO - 14:04:36.797: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1035246 to #1056411
-INFO - 14:04:44.610: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1056412 to #1086200
-INFO - 14:04:50.157: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1086201 to #1148030
-INFO - 14:04:57.657: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1148031 to #1208116
-INFO - 14:05:04.407: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1208117 to #1254501
-INFO - 14:05:10.297: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1254502 to #1297809
-INFO - 14:05:17.282: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1297810 to #1353958
-INFO - 14:05:25.219: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1353959 to #1355659
-INFO - 14:05:33.672: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1355660 to #1356566
-INFO - 14:05:41.438: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1356567 to #1381119
-INFO - 14:05:48.672: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1381120 to #1382081
-INFO - 14:05:56.360: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1382082 to #1382937
-INFO - 14:06:03.079: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1382938 to #1383526
-INFO - 14:06:11.360: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1383527 to #1384130
-INFO - 14:06:19.563: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1384131 to #1384752
-INFO - 14:06:27.563: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1384753 to #1407983
-INFO - 14:06:35.782: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1407984 to #1409496
-INFO - 14:06:44.985: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1409497 to #1410221
-INFO - 14:06:54.907: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1410222 to #1410889
-INFO - 14:07:03.516: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1410890 to #1412060
-INFO - 14:07:11.782: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1412061 to #1412639
-INFO - 14:07:21.219: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1412640 to #1413330
-INFO - 14:07:27.360: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1413331 to #1456125
-INFO - 14:07:33.032: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1456126 to #1511988
-INFO - 14:07:39.141: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1511989 to #1564606
-INFO - 14:07:47.375: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1564607 to #1579649
-INFO - 14:07:53.157: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1579650 to #1607217
-INFO - 14:07:59.547: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1607218 to #1664477
-INFO - 14:08:05.875: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1664478 to #1696698
-INFO - 14:08:12.329: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1696699 to #1775205
-INFO - 14:08:18.594: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1775206 to #1834985
-INFO - 14:08:25.516: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1834986 to #1895923
-INFO - 14:08:30.797: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1895924 to #1970185
-ERROR - 14:08:34.829: (e:\users\goat\code\armory3\cppforswig\binarydata.h:1333) buffer overflow
Log file opened at 14:18:04.000: C:\Users\HCP\AppData\Roaming\Armory\testnet3/dbLog.txt
-INFO - 14:18:04.000: (e:\users\goat\code\armory3\cppforswig\main.cpp:32) Running on 12 threads
-INFO - 14:18:04.000: (e:\users\goat\code\armory3\cppforswig\main.cpp:33) Ram usage level: 50
-INFO - 14:18:04.000: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:915) blkfile dir: E:\Bitcoin\testnet3\blocks
-INFO - 14:18:04.000: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:916) lmdb dir: C:\Users\HCP\AppData\Roaming\Armory\testnet3\databases
-INFO - 14:18:04.000: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 14:18:04.047: (e:\users\goat\code\armory3\cppforswig\bdm_server.h:263) Listening on port 56593
-INFO - 14:18:04.047: (e:\users\goat\code\armory3\cppforswig\bitcoinp2p.cpp:947) Connected to Bitcoin node
-INFO - 14:18:04.047: (e:\users\goat\code\armory3\cppforswig\noderpc.cpp:57) RPC connection established
-INFO - 14:18:04.047: (e:\users\goat\code\armory3\cppforswig\blockdatamanagerconfig.cpp:919) waiting on node sync: 100%
-INFO - 14:18:04.047: (e:\users\goat\code\armory3\cppforswig\noderpc.cpp:425) Node is ready
-INFO - 14:18:04.047: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:1108) Executing: doInitialSyncOnLoad
-INFO - 14:18:05.079: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:199) Reading headers from db
-INFO - 14:18:07.141: (e:\users\goat\code\armory3\cppforswig\bdm_server.cpp:1121) registered bdv: 56feb8cc2276cf9848f0
-INFO - 14:18:18.297: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:238) Found 2098851 headers in db
-INFO - 14:18:29.360: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:64) Rewinding 100 blocks
-INFO - 14:18:29.360: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:71) updating HEADERS db
-INFO - 14:18:29.375: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:493) Found next block after skipping 32115bytes
-INFO - 14:18:29.407: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #200
-INFO - 14:18:29.407: (e:\users\goat\code\armory3\cppforswig\blockchain.cpp:248) Organizing chain
-INFO - 14:18:29.532: (e:\users\goat\code\armory3\cppforswig\blockchain.cpp:370) Organized chain in 0s
-INFO - 14:18:29.532: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:76) updated HEADERS db in 0s
-INFO - 14:18:29.563: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 14:18:29.563: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:1231) verifying txfilters integrity
-INFO - 14:18:30.344: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:1314) done checking txfilters
-INFO - 14:18:30.454: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:1891) Enabling zero-conf tracking
-INFO - 14:18:30.563: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:401) Starting address registration process
-INFO - 14:18:35.016: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #0 to #206498
-INFO - 14:18:43.125: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #206499 to #266421
-INFO - 14:18:48.907: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #266422 to #348885
-INFO - 14:18:55.735: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #348886 to #500981
-INFO - 14:19:01.922: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #500982 to #584256
-INFO - 14:19:09.094: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #584257 to #606023
-INFO - 14:19:17.204: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:52) no history to scan
-INFO - 14:19:17.860: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #606024 to #624331
-INFO - 14:19:25.000: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #624332 to #627777
-INFO - 14:19:34.422: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #627778 to #631898
-INFO - 14:19:42.375: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #631899 to #715747
-INFO - 14:19:50.688: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #715748 to #723331
-INFO - 14:19:57.422: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #723332 to #892111
-INFO - 14:20:03.594: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #892112 to #919668
-INFO - 14:20:10.563: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #919669 to #947235
-INFO - 14:20:17.188: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #947236 to #1012869
-INFO - 14:20:25.188: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1012870 to #1035245
-INFO - 14:20:32.235: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1035246 to #1056411
-INFO - 14:20:39.735: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1056412 to #1086200
-INFO - 14:20:45.829: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1086201 to #1148030
-INFO - 14:20:52.125: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1148031 to #1208116
-INFO - 14:20:58.329: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1208117 to #1254501
-INFO - 14:21:04.297: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1254502 to #1297809
-INFO - 14:21:10.954: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1297810 to #1353958
-INFO - 14:21:18.875: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1353959 to #1355659
-INFO - 14:21:27.329: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1355660 to #1356566
-INFO - 14:21:35.141: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1356567 to #1381119
-INFO - 14:21:42.594: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1381120 to #1382081
-INFO - 14:21:50.172: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1382082 to #1382937
-INFO - 14:21:57.563: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1382938 to #1383526
-INFO - 14:22:04.750: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1383527 to #1384130
-INFO - 14:22:12.813: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1384131 to #1384752
-INFO - 14:22:20.954: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1384753 to #1407983
-INFO - 14:22:29.454: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1407984 to #1409496
-INFO - 14:22:39.094: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1409497 to #1410221
-INFO - 14:22:48.469: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1410222 to #1410889
-INFO - 14:22:56.985: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1410890 to #1412060
-INFO - 14:23:05.266: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1412061 to #1412639
-INFO - 14:23:14.360: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1412640 to #1413330
-INFO - 14:23:20.516: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1413331 to #1456125
-INFO - 14:23:27.235: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1456126 to #1511988
-INFO - 14:23:33.688: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1511989 to #1564606
-INFO - 14:23:40.735: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1564607 to #1579649
-INFO - 14:23:47.563: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1579650 to #1607217
-INFO - 14:23:52.735: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1607218 to #1664477
-INFO - 14:23:58.813: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1664478 to #1696698
-INFO - 14:24:04.766: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1696699 to #1775205
-INFO - 14:24:10.750: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1775206 to #1834985
-INFO - 14:24:17.625: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1834986 to #1895923
-INFO - 14:24:22.735: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #1895924 to #1970185
-ERROR - 14:24:26.594: (e:\users\goat\code\armory3\cppforswig\binarydata.h:1333) buffer overflow
I have tried this about 5 times now... and every time it buffer overflows in the same place. Note: Armory mainnet is working fine. @goatpig Any ideas for a fix? |
|
|
|
But I see no reason why the person should downgrade his wallet as it will take much time, although it is an option that can be used, but why the person do not just use the latest version, click on view -> console and type in the first command above which will bring up seed phrase to generate legacy address and import it on the latest version of Electrum wallet directly, it is as easy as that.
It doesn't really take any time at all... and you don't need to downgrade anything. Simply download the portable version of Electrum 4.0.9 and run it in it's own folder somewhere. It won't affect your current installed/standalone version or existing wallet files... and you'll be able to generate all the "legacy" seeds you like using the GUI without having to worry about renaming/moving wallet files, or messing about with the console commands. Additionally, any wallet files made with 4.0.9 portable can be easily copied over to (or opened with) your 4.1.5 (or later) version and "upgraded" without issue. |
|
|
|
|
IMO, the important takeaway of all of this... is that as long as the user is aware of the potential "flaws" of a given system, then they can make an informed choice as to whether or not they wish to continue using it.
Some users really don't give two shits about their privacy... they'll happily use exchanges/web wallets etc. because "it's easy" or "it just works" or "it doesn't require downloading anything"... and that's completely "OK"... as long as they're aware of it and are consciously making that choice.
The issues come when people look at Electrum and TOR and coin control etc and think "wow, Electrum is really great for privacy as well as security"... when they are busy leaking information all over the place connecting to random servers etc.
Can Electrum be used in a way that helps maintain privacy? Yes... it can. Does it do this "out of the box"? No... it does not.
|
|
|
|
One other thing. I could store powerledger in nano ledger s right? I check online and it seem this is done with ETH app? So there isn't a powerledger app in nano ledger? Because when i was checking the apps to install on the nano ledger, i didn't see powerledger app.
But does it need to be used with myetherwallet.com though? I remember years ago someone said you did... which is why i decided to just leave my powerledger in exchange instead of keeping it in my own wallet.
PowerLedger is an ERC-20 token (POWR)... so there is no "app" for it on the Ledger Nano. You simply use MEW or MyCrypto in conjuction with the ETH app on your Ledger Nano. You will likely need to use the "add custom token" functionality in MEW/MyCrypto and the PowerLedger contract address: 0x595832f8fc6bf59c85c527fec3740a1b7a361269 to be able to "see" and transact your POWR tokens in MEW/MyCrypto (in addition to have ETH available to pay gas fees etc) |
|
|
|
But if your passphrase isn't a real complex word... is it still not that good?
Example your passphrase is
jerrywentoverthereagain
jerrylikestodrinkvodka0
I mean that is pretty good passphrase as long as you can remember it or write it down somewhere or store it in password manager as long as your seed isn't online?
Neither of those are good passphrases. They are "long"... but they are not "good". Length is not necessarily directly proportional to security. It can help, but isn't necessarily the only factor. For example, thequickbrownfoxjumpedoverthelazydog is a really long password, but because it is essentially just 9 common english words concatenated together, it's probably only marginally more secure than a 9 character password. Another thing to remember is that just like "characters" in a password should be random... your "word" selection should be too. Ie. "lounge fall lung hole award" is arguably more secure than "jerry went over there again" |
|
|
|
Sim swapping has been an issue forever.  It still bothers me that there are services that insist of using either email or SMS as part of a 2FA system, as they're so easily exploitable. I really wish more services would use TOTP as standard. While not perfect, they are much better than email or SMS. |
|
|
|
Thanks. Once they are then back in a wallet then the private key comes into play again?
More correctly, once you get the coins from Coinfloor into your Electrum wallet... then your Electrum seed phrase comes into play. If you have those 12 words, you'll be able to recreate your entire Electrum wallet. That is to say, any and all private keys that it generates from that seed phrase. Those 12 words are all you require. Make sure you have them securely and safely backed up offline. Do not store a screenshot of them, do not store them unencrypted in digital form on an online computer or cloud backup service etc. |
|
|
|
the log appeared again and this is what it says; hope this helps
That's the Armory log... not the Bitcoin Core log. When you said this: So I literally just spent the last three weeks downloading Bitcoin core and it was almost done (about 88.24% of the way done) and I get an error message "an internal error message has occurred, please check the log".
Was that an error displayed by Armory or by Bitcoin Core? Did you actually run Bitcoin Core manually yourself... or had you opened Armory first and it was running Bitcoin Core in the background? I am really kind of desperate for help here and really wishing i never used Armory. I really hate this.
You could take the advice of Rickorick and export your keys. I have a tutorial here: https://bitcointalk.org/index.php?topic=4746784.msg43255691#msg43255691 |
|
|
|
now that I can't open wallets on version 3.X (I'm getting error that the version is too old) I can't sign the transactions.
Electrum wallet files have a built in "version" number. When modifications are made to the wallet file format (adding/removing fields etc), Electrum "upgrades" this wallet file version and once your wallet file is "upgraded", you can't open it in a lower version of the application. This is the reason why you are getting the "version is too old" error message. Your wallet file was opened in a newer version of Electrum and has been updated. The only way back would be to use an old backup copy of the wallet file, or to recreate the wallet in an older version of Electrum using your seed. |
|
|
|
The obvious solution would be the simplest. 1. Back your wallet.dat files (which you already appear to have done) 2. Install the latest version of Bitcoin Core from: https://bitcoincore.org/en/download/3. Load copies of backups of the wallet.dat files into the latest Bitcoin Core. DO NOT use the originals! 4. Let Bitcoin Core fully sync and then see what the results are Once fully synced, Bitcoin Core should show you the accurate balance of each wallet. From there you can then make some decisions regarding what you want to do with the coins that you have available. Do you know if the wallet.dat files are password protected? If they're not, then the above may not be the "safest" way forward... as if the computer is compromised, and someone gets the unencrypted wallet.dat, they could take all your coins. If the wallet.dat files are encrypted, then that helps mitigate the risk of the wallet.dat files being exposed. |
|
|
|
I'd love to see something similar for encrypting a 12/24 word seed. Even better if the result is just represented as a seed again: to restore, enter the encrypted seed, the password and wait a few seconds (yes, seconds!) to decrypt it. I'd feel much safer than just storing the unencrypted seed words in plain text.
I'm still struggling to understand why you need something other than the currently available plain text encryption options. This really does seem like reinventing the wheel to me... Is it because you want wallets to provide built in methods to encode/decode the mnemonic string? Noting that if you end up with "random" text, it sort of defeats one of the core purposes of the mnemonic in the first place... ie. reduction of transcription errors. Turning the result into another mnemonic string sounds like it should be possible... but then, why not just use the original seed and a strong BIP39 passphrase? Surely this ends up effectively resulting in the same thing... a mnemonic string + passphrase? It seems like creating a .zip file with a password and then putting that into a .rar archive with another password... or am I missing something? |
|
|
|
|
Show Posts
