|
Can you post the log files? Use pastebin if it's too big. If it's too big for that, show us as much as you can from the most recent times you have tried to run Armory.
You should also try running Bitcoin Core separately. Uncheck the option for Armory to run Bitcoin Core in the background in the settings.
|
|
|
|
The person that helps the most in getting me my bitcoins back will get 1 bitcoin reward.
I have a wallet in Bitcoin core.
I think I upgraded to core 12.1 maybe 9 months ago, and my wallet is older than that.
0.12.1 was not released 9 months ago. It's much newer than that. I haven't used core very much, but decided to receive bitcoins to core wallet some time ago, which of course I expected to work.
I know I know, I shouldn't have used a wallet that didn't have the 12 words that will keep my private keys forever, but I knew that I had multiple backups of the wallet so I thought it couldn't be that risky to use Bitcoin Core.
However, now my core wallet doesn't work. I's saying that the password is wrong. I don't remember changing the password, and why would I do that anyway, because I had a nice system on it. But I cannot sign messages or send the bitcoins. It's as if the wallet file is corrupted or something, and now I cannot unlock the private keys. I've tried all kinds of password, but they don't work. The original password I set on the wallet is not working.
Are you sure you are using the correct wallet file? Is the correct file in the correct data directory? If I didn't know any better, I'd suggest that Core has changed the way it stores or retrieves the private keys in a way that's not working properly with the old way the keys were stored. So after upgrading maybe the new keys are not compatible with the wallet? I don't know.
No, nothing of that sort has changed. I have backup of the core wallet with a known password that can sign messages, but when I use those wallets, they don't generate the same bitcoin addresses.
I thought even core stored at least 100 addresses in the wallet file, but it seems these addresses are all generated on the spot, with no memory of what's happened before and no seed for the random generator.
No, you're wrong. Bitcoin Core does pregenerate 100 addresses and those are in fact stored in the wallet file. Joke aside, I know there's a guy in the bitcoin community that helps people with these kinds of things, and he has a reputation for doing a good job and being an honest person. I don't remember his name. Anyone know who I'm talking about?
Dave at wallet recovery services? If that's who you are thinking of (he brute forces wallets), he probably can't help if you have no idea what the password is.
I highly suspect that you either have the wrong wallet.dat file or the wrong data directory. Go to Help > Debug Window and look at the line labeled Datadir. Does it show you the data directory that you have been putting wallet files into? |
|
|
|
A.
For action number 6, I am told to enter "listaddressgroupings" to get a list of my public adress. Doing so will give me a long list of all addresses I have previously used for transactions. Am I correct in assuming that using any of these addresses (and only that one) in action number 6 will give me the private key I need to have a paper wallet (and reach my goal of what I want to achieve (mentioned at the top of this text) ? Or do I need to repeat action 6 for every Bitcoin address I have received Bitcoins to (even if all Bitcoins are in the same Bitcoin-QT wallet) ?
You will need to use dumpprivkey for every single address that you have ever used. That command only returns the private key for one address, so it does not apply to any other address in your wallet. If you are using a wallet made in Bitcoin Core 0.13.0, you can use dumpwallet and open the output file and get the master private key. Since Bitcoin Core 0.13.0 uses deterministic wallets, all you will need is the master private key. B.
What is the corresponding actions that I need to take to "start over" if my computer and all USB-backups are destroyed? This is my guess:
- Download and install Bitcoin-QT to a new computer
- Action 1-5 above
- importprivkey [my private key from my paper wallet] (any parameters?)
- Anything else?
For importprivkey, you will want to do importprivkey <key> "" false. This will import your key into the default account (well hopefully accounting will be removed by the time you import so this won't matter) and it will not rescan. The very last key you import you will want to set that false to true so that it rescans the blockchain. C.
Someone wrote that if I do a "backup of wallet to paper" procedure of my Bitcoin-QT wallet (action 1-7 above) the paper wallet becomes useless if any transactions are sent/received from my Bitcoin-QT wallet? How can that be?
Even if I continue send and receive transactions from/to my Bitcoin-QT wallet should not the paper wallet work just as fine if I need to start over (as described in question "B" above)?
It depends. If you are using a wallet created in Bitcoin Core 0.13.0+, with the master private key, it doesn't matter. You can still send and receive. However, if you use a wallet created in an older version, it does. This is because when you send and receive you are constantly generating new addresses. If you receive Bitcoin, you should be giving the sender a new address. If you are sending, you will produce change which will go to a new address. These new addresses is randomly generated so you won't have a backup of them. |
|
|
|
|
Bitcoin.org has relisted Armory on the wallets page. Bitcoin.com has told me they would but it doesn't appear to be up.
|
|
|
|
Btw, what means the percentage in Post Quality section ?
It's the ratio of good posts (posts with at least 75 chars) to bad posts. And maybe you could add the average number of char per post would be nice  That's actually a good idea. I think I might do that. |
|
|
|
|
Look in meta. The stickied thread titles are self-explanatory.
|
|
|
|
I've banned the user for now. For started, it would also help if you'd add a date in your signed message.
Thank you. I will do that in future. Here is the message with a date. -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
My account has been hacked due to the recent dump again whilst I was away.
Please mark the account CrackedLogic with RED FEEDBACK until I retrieve. I'm apologize for any users that have been scammed or deceived my "myself".
Please also let users on the trust list to mark the account, any help would be appreciated.
https://bitcointalk.org/index.php?action=profile;u=168114
If any of the admins could contact me to assist or notify me if recovery is possible it would be much appreciated.
Dated : 9/10/2016
-----BEGIN PGP SIGNATURE-----
Version: Keybase OpenPGP v2.0.56
Comment: https://keybase.io/crypto
wsBcBAABCgAGBQJX082/AAoJEKgwaK3mmmFMsnoH/ijhNfKpZKIypXNcrStoiMXA
+EdMl5/tZ4pUQ0CE49dnMNLaG/gj0zk0zy4U7zuwsYoJlzQ+dMRKD7gP3ISucAXM
a8fW41BGlFkIR3blZmIOfpLdHIn+z41PBWy7eF222Q1jLbvz1dFaiNR45mdS3THI
MybxzZ6KowhzcdX1FiNLW70joYKecA3egnnp/D67AmgkBDPXwvzjasDdUSgDrG5n
835PZJKQGkB/K063we+G2UqmvN+HS2K4FcXwK/B4HgAZOcGkcXx9qglpXXF7Brus
eVJwKZwTedWIhjc0NfRnNHQRli830Vf5chlh+gz9qF2kZf26cdjYA4Fxi0k5WCs=
=lTRB
-----END PGP SIGNATURE-----
Quoted and verified to key fingreprint 7545 D232 6E4A AC8E BAE1 8BF7 76CF 0ECE C396 44F5. Same as the one posted at https://bitcointalk.org/index.php?topic=1159946.msg13628573#msg13628573Would it be possible for another breach happening without the mods or the staff knowing? There is a few threads with users claiming that their accounts are hacked. The DDOS plus the hacks could not be all a coincidence. What do you all suspect?
I suspect that you are spamming in order to pad your post count. It is highly unlikely that a breach would occur without anyone noticing. |
|
|
|
Not sure if Cyrus has been doing it or not.
Theymos was the one who changed my name (but I did PM both of them). Unless you have reported a large number of posts, have contributed to the moderation in some other way, have invested a significant amount of your time in helping the Bitcoin community in one way or another, or have an extensive trading history, or run some kind of Bitcoin related business, the chances of getting your username changed is basically zero.
That's pretty accurate. Just thinking about it, all of the members whose names have changed were all hero or legendary, had high trust, were pretty active, and were well known on this forum. And I think most of them were on the list of "most accurate reports made" that Theymos published a while back. |
|
|
|
|
Import the PGP key into a client like GPG. Then view the key details. It will tell you the Fingerprint, the ids, the name, the email, and any comments. You should of course verify that the details of that key are indeed correct since there isn't anything like a central server that guarantees that. Anyone could set any name or email that they want in their own PGP key.
|
|
|
|
Those datas are from one year old hack, so if you haven't opened account before than nothing to worry about. And even possibility of anyone gonna know your real password out of that sha256 encrypted passwords is really low. However changing password if you are in list of those hack accounts is always advised.
So this is not a second one? I heard there was one last year and then there are ddos attack just two days ago and yesterday. So I thought this was a new set of mined data from this new hack job during those attacks. Thats what im thinking too that Database is new and on the latest hacking of bitcointalk website. I do experience website down for how many hours which is unusual since i didnt experience in the past and luckily i read this topic regarding of DDos of bitcointalk and database has been for sale on dark web which is somehow alarming for us users here in this forum. A DDoS attack cannot recover any information from a website. It does exactly what the name of the attack implies, it Denies Service. No data is taken from the site. The database for sale is from the only major hack of bitcointalk which happened in May 2015. |
|
|
|
|
No, not possible. An address isn't even an actual object in the blockchain. It is just a visual representation of the RIPEMD160 of the SHA256 of a public key. There is no other information in an address.
|
|
|
|
try http://gobittest.appspot.com/Address. Just enter the hash160 in step 3. If you want automation, try writing a script. There are many bitcoin libraries available that you can use. |
|
|
|
It's a dang long file!!
Copy and paste it into a new paste at http://pastebin.com/. If it's too long (which it probably is), get the most recent stuff. Try to get the beginning of a run of bitcoind, it should start with a bunch of blank lines and then the bitcoind version. And I simply use bitcoind to start the server
So your command is just ? If it is, that's interesting. It shouldn't be doing this. What's in your bitcoin.conf file? |
|
|
|
I've had to trim the file to get under the 512K limit for guest users but there a lot either side of the offending transaction time. http://pastebin.com/hkMVzj0tFor some reason your Armory has not been in sync. It is stuck at block 425773. To fix this, I think you need to rebuild and rescan the databases. Go the Help > Rebuild and Rescan Databases. Click yes then restart Armory. FFI. I have been leaving the Bitcoin core GUI running constantly to keep the db utd and provide a full network node, then shutting it down before periodically loading Armory to check for incoming payments and/or send payments (I'm nervous about leaving a wallet with upwards of 50 BTC sitting online all the time). On occasion I have forgotten to close the BTC GUI before loading Armory and thus been prompted to close it first. Also, I have suffered the odd 'unexpected closure' of the BTC GUI which remain unsolved. When that has happened it has left bitcoind running and I've had to shut it down with the OS terminal before starting Armory again.
If you're doing that, might as well just turn off the auto-managed bitcoind. Go to File > Settings and uncheck "Let armory run Bitcoin-core in the background". Then restart Armory. This will allow you to keep Bitcoin Core running while Armory is running. However, in order for Armory to work, you will need to start Bitcoin Core by yourself. If you are using a custom datadir for either Armory or Bitcoin Core, you will need to set command line options, --datadir=<path> for Armory's and --satoshi-datadir=<path> for Bitcoin Core. |
|
|
|
Yeah looks like it's running testnet
WTF HOLY SHIT!!!!!!why the fuck is it running testnet?
Can somebody help me!!!!! Please lol
What command are you using to start it? Can you please post the debug.log file? debug.log This is it. Is there a testnet3 folder in your data directory (there should). Can you get the log from there? Also, what is your startup command? |
|
|
|
Yeah looks like it's running testnet
WTF HOLY SHIT!!!!!!why the fuck is it running testnet?
Can somebody help me!!!!! Please lol
What command are you using to start it? Can you please post the debug.log file? |
|
|
|
So the raw transaction API has to reference the local wallet? You can't just put arbitrary data in that and expect it to work? I'm thinking of a hypothetical third party wallet that keeps track of it's own bitcoin keys, and then tells the bitcoind server to broadcast a raw transaction involving them.
Yep, that will work perfectly fine. The raw transaction apis allow you to specify everything you need to create, sign, and broadcast a transaction. It does not require the use of the wallet. With signing, you can specify the private key and the referenced outputs. If you enable the txindex, you don't need to specify the referenced outputs. I don't know the technical details of the transaction operations, but Armory (which maintains it's own private keys) uses the Bitcoin client (bitcoind or Core) to broadcast transactions and for the block chain data as well.
Armory doesn't use the RPCs. It actually connects to Bitcoin Core through the p2p network in order to broadcast the transactions. |
|
|
|
Are you using testnet? IIRC testnet is somewhere in that region. Edit-1:I have re-installed bitcoind multiple time on this machine,so does the block count includes the blocks from previous installation(maybe it coudn't verify those blocks and started a fresh installation).BTW,I am a noobie at these things  Reinstalling isn't going to help. The data is not stored in the installation directory. It is stored in the data directory, which depends on your OS. So, yes, the blockchain will persist between installs, that's what allows you to upgrade without losing everything. |
|
|
|
can I also request theymos and ask him to change my name? is it possible to everyone?
You can ask, but he may not do it for you. I'm sure that he only does it for a specific set of people, those who are high ranking, active, trustworthy, and post with high quality. |
|
|
|
Can you tell if it possible to sign raw transaction with mycelium / electrum . Most people are not using bitcoin core
You can sign transactions with Electrum, but I don't think you can do it with Mycelium. You have to use the python console provided by Electrum in order to sign. |
|
|
|
|
Show Posts
