Before I purchased bitcoin with Bit Trade they suggested (among other wallet providers) I use Armory. So, I did. Then, after a wallet was created I gave it to Bit trade for them to deposit my bitcoins there. Everything went well with Poli payment and my money ended on the bank account of someone called Digital Blue Solut. That was all we did. However, when I clicked Bitcoin Armory Management after the transaction was done, there was no money or bitcoins in there. At no time did I have any access or control of my money. It was like going into the air. Later on, I contacted Bit Trade to ask them why I didn't have any control of my investment (sell, buy, keep it, cash it, deposit profit to my bank account) nothing. They sent me Blockchain page showing my transaction in there. And my saga began there.
Two other wallets I created later on (actually Armory did that) to see how it works. I don't see why all this drama has unfolded with armory and Bit Trade.
You said, "Have you actually sent bitcoin from Bit Trade to your Armory wallet? As it stands, you are telling me that you have 2 wallets in Armory and haven't used or sent any bitcoin to either of them."
I didn't send anything, Bit Trade did that, with the wallet I provided them with. One that, for whatever reason, didn't end up on the Bitcoin Armory Management.
Furthermore, Why is my public wallet (used by bit trade to make the transaction) inside of Armory "all wallets" window but no access to it? Why don't I have any access to it? Why isn't my passphrase accepted by Armory? How am I going to recover my money?
What? |
|
|
|
|
It's not a matter of filesystem so much as cost of flushing. The DB looks for data on disk after it receives notification for a new block from the node. The node may not have been done flushing the data on disk by the time it has pushed the block over the P2P.
|
|
|
|
In other words, are the wallets, which created and managed by Armory, have any kind of connection between each other?
No. A wallet is created from a random seed. The randomness is gathered from your system, key strokes, mouse movements, a hash of your temporary user folder as well as optional manual entropy (the deck of cards GUI). There is no deterministic, reproducible relationship between random seeds. Addresses within a wallet are derived from the wallet's seed. They hold a mathematical relationship, which under certain circumstances, can reveal either the chain further down the leaked values, or all the way up to the seed. Generally, if you've exposed one private key publicly, assume your wallet is compromised and move your founds out of it. |
|
|
|
|
1) Don't downgrade. Upgrade.
2) G:\Blockchain. This folder either does not exists, or you have not given your user account the privileges to read/write in it.
|
|
|
|
The risk is low but possible.
It's not just "possible", it's very real. Worse than the lack of security is the illusion of security. Just how long do you think average users are going to keep funds on a given wallet? I expect they'll perpetuate the same wallet for decades as long as they believe it's secure, which it won't be as they foolishly expose private keys over time. |
|
|
|
HDD for core blockchain and armory db.
That's your culprit. |
|
|
|
|
Post the full armorylog.txt
|
|
|
|
|
1) Update Armory
2) Download Bitcoin Core and let it sync the blockchain (gonna take over a week looking at your machine)
3) You can now start Armory
|
|
|
|
|
In Armory, go to File -> "Export Log File". Post the resulting file. Use pastebin.com
|
|
|
|
|
1) Delete your databases folder: C:\Users\benma\AppData\Roaming\Armory\databases.
2) Update to RC3, check the stickies.
3) Start Armory. If it fails again, post the fresh logs.
|
|
|
|
Make sure the node is off while the DB is catching up. Once the DB is ready, start the node.
wait...what? The DB builds off of on disk data. If you have a low RAM system, letting the DB build the initial dataset before turning on the node (which eats ~3GB RAM) is a good work around. You can then start the node to catch up the last 100 blocks or so. |
|
|
|
|
I'm like... busy with other stuff... also I'm lazy! Soon (tm).
|
|
|
|
You can download the chain and build the DB on your main machine, then take that to the laptop, if you know what you're doing with the pathing. Read up on it in here: https://btcarmory.com/docs/pathing |
|
|
|
1) Delete your DB folder 2) Create a file named armoryqt.conf in your Armory datadir. Put that in it: 3) Make sure auto bitcoind is turned off in File -> Settings (first checkbox) 4) Start Armory without your node running. It will build the DB. 5) Once the DB is ready, shut down Armory, start your node, then start Armory again. If you're having trouble, post your logs again. |
|
|
|
Either sync the DB without the node running, or setup your bitcoin.conf proper: server=1
addnode=127.0.0.1
|
|
|
|
|
You need to post fresh logs with each iteration. Saying "it does not work" will not yield more clues than the first time around.
|
|
|
|
|
Make sure the node is off while the DB is catching up. Once the DB is ready, start the node.
|
|
|
|
|
Show Posts
