I have absolutely no idea. So there's no way to dump the private key like on core-qt?
There is, but you will still need your password just like in bitcoin core. |
|
|
|
it works! it's the right file. now what?
Do you see the correct balance? If you do, then you can spend the Bitcoin normally. |
|
|
|
Why is it taking so long to sync?  Your internet speed and the internet speed of the node that Bitcoin core happens to choose as its download peer is a large factor of the speed. Also part of it is the speed of your CPU and how much RAM you have in order to quickly process the data that you receive. |
|
|
|
|
You need to be online in order to create a transaction. I suppose you could try to use Bitcoin Core's createrawtransaction rpc command to create the raw transaction and then have Armory sign it while it is offline then broadcast the transaction again through BitcoinCore.
|
|
|
|
If I understand well, the private key is the same in livenet and tesnet:
the private key is just a ramdom number and the WIF format will
also be the same.
No. The WIF format will be different to indicate which network that private key is meant for. For testnet it will start with 'c' or '9'. On the mainnet it will start with '5', 'K' or 'L' Then we calculate the <pubkey> by adding points on a elliptic curve,
so the pubkey is a pair of coordinates (x,y). Then we write the pubkey
like "04 x y" OR "02 x" (if y is positive) OR "03 x" (if y is negative).
It is only when we create the base-58 pubkey that we use a different
format so the pubkeys looks different in testnet and livenet.
Yes. Only after doing base58CheckEncoding to create the WIF format will the private key (encoded as WIF) and public key (encoded as an address) appear different. |
|
|
|
OK but here is a simple example: bitcore = require('bitcore');
bitcore.Networks.defaultNetwork = 'testnet';
var privateKey = new bitcore.PrivateKey();
console.log('privateKey: ' + privateKey);
var exported = privateKey.toWIF();
console.log('privateKey toWIF: ' + exported);and the output is: privateKey: 13421db757900dae2ecd471b2cca0d950f8ca47fd867e3c44dadd64f57194252
privateKey toWIF: 1eSGCW9EJ8pUZ6QEpa3385at83n3hdXrJ57VpmmFQRSv3JcMVHW Something is definitely wrong with your install of Bitcore. It is not producing the proper WIF key. Again, it should start with a 'c' or '9'. In most cases, it should be a 'c' |
|
|
|
here is what i have in the armorycpplog.txt
Log file opened at 1447964950: C:\Users\tvl\AppData\Roaming\Armory\armorycpplog.txt
-INFO - 1447964974: (..\BlockUtils.cpp:918) blkfile dir: C:\Users\tvl\AppData\Roaming\Bitcoin\blocks
-INFO - 1447964974: (..\BlockUtils.cpp:919) lmdb dir: C:\Users\tvl\AppData\Roaming\Armory\databases
-INFO - 1447964974: (..\lmdb_wrapper.cpp:478) Opening databases...
-INFO - 1447964974: (..\BlockUtils.cpp:1250) Executing: doInitialSyncOnLoad
-INFO - 1447964974: (..\BlockUtils.cpp:1321) Total number of blk*.dat files: 377
-INFO - 1447964974: (..\BlockUtils.cpp:1322) Total blockchain bytes: 50,514,630,389
-INFO - 1447964974: (..\BlockUtils.cpp:1695) Reading headers from db
-WARN - 1447964974: (..\lmdb_wrapper.cpp:1478) No headers in DB yet!
-INFO - 1447964974: (..\BlockUtils.cpp:1721) Found 1 headers in db
-DEBUG - 1447964974: (..\Blockchain.cpp:211) Organizing chain w/ rebuild
-WARN - 1447964974: (..\BlockUtils.cpp:1351) --- Fetching SSH summaries for 112 registered addresses
-INFO - 1447964974: (..\BlockUtils.cpp:1364) Left off at file 0, offset 0
-INFO - 1447964974: (..\BlockUtils.cpp:1367) Reading headers and building chain...
-INFO - 1447964974: (..\BlockUtils.cpp:1368) Starting at block file 0 offset 0
-INFO - 1447964974: (..\BlockUtils.cpp:1370) Block height 0
-ERROR - 1447964975: (..\BlockUtils.cpp:639) Next block header found at offset 67344418
-DEBUG - 1447964976: (..\Blockchain.cpp:211) Organizing chain w/ rebuild
As you can see here, Armory is rebuilding its blockchain database from 0. That will take a long time. Also, did you restart Armory when you did this since the timestamp (those big numbers are unix timestamps) are for a few minutes ago. |
|
|
|
I have still not heard anything from the campaign manager, wanxinxi.
Please message me the total amount of constructive, unpaid posts you've made as well as a payment address.
Your payment rate will be calculated using the following. ((0.40BTC / ((total posts by hero*.0008) + (total posts by senior*.0007) + (total posts by full*.0005))
Thank you
Can't you just check the spreadsheet for the posts made from the 31st to the 6th? The spreadsheet has the correct post count, but the problem is that the rates changed midway through that week so the actual payment calculation is quite annoying to do. Edit: Here are my post counts. Starting: 3194 Ending: 3237 Posts made: 43 Owed: 0.0516 BTC (I resigned and made no new posts at the new rate) Address: 16mT7jrpkjnJBD7a3TM2awyxHub58H6r6Z |
|
|
|
lst line says 5:17 (INFO) -- Networking.pyc:350 - Handshake finished, connection open!but armory status is still organizing blockchaini start to be worry for my btc now  Check both of them, armorycpplog.txt and armorylog.txt. I think the important info you want is in armorycpplog.txt |
|
|
|
This whole thing doesn't add up. LTC works, BTC and Doge do not get above 8 connections.
Why do you care so much? 8 Connections means that you probably have 8 outgoing connections which is the maximum number of outgoing connections you can have. If people don't connect to your node, then you won't have any incoming connections. I myself, with Bitcoin Core, rarely have more than 8 connections even though I have upnp enabled and have port forwarding enabled. You might want to read the WHOLE threat and you might understand. I do understand. You think that not having more than 8 connections will make the syncing slow. BUT Bitcoin Core syncs through ONLY ONE NODE. It doesn't matter how many connections you have. Bitcoin Core will CHOOSE ONE OF THEM and do ALL of the initial syncing through that node. It doesn't matter how many you are connected to, ONLY ONE is used for the initial sync. After that, then it will receive blocks as its nodes relay them. |
|
|
|
Where did you get the private keys? It has been generated by bitcore (node.js), for testnet. var privateKey = new bitcore.PrivateKey(); the key has 64 char the WIF format is 14xCi3eQ3AJvk...xyEQRooQNv1GGQSb and has 52 char No, WIF format is 51-52 chars and should start with '9' or 'c'. The private key you have is the raw hex code. According to the docs at https://bitcore.io/api/lib/private-key you will need to use the toWIF() function in order to get the WIF key which you need. You cannot use the raw hex key. |
|
|
|
its been like 5 hours now,
and nothing changed,
how can i check that armory is really doing something ?.
thx
If you go to the armory data directory, you can tail the log files and see what armory is doing. |
|
|
|
|
What do you mean that it is stuck? The transaction has already been confirmed.
|
|
|
|
He said in an earlier post that he wasn't paying that week's because the amounts in the spreadsheet was wrong. I think you should check those again and fix the numbers so that he will pay it. I don't think this is a matter of Wangxinxi not wanting to pay but rather not paying because of accounting error. |
|
|
|
This whole thing doesn't add up. LTC works, BTC and Doge do not get above 8 connections.
Why do you care so much? 8 Connections means that you probably have 8 outgoing connections which is the maximum number of outgoing connections you can have. If people don't connect to your node, then you won't have any incoming connections. I myself, with Bitcoin Core, rarely have more than 8 connections even though I have upnp enabled and have port forwarding enabled. |
|
|
|
|
Your private key is incorrect. It should be start with a '9' or a 'c' and be 51-52 characters long. Where did you get the private keys?
|
|
|
|
Is there a specific way to open that file? I'm just trying open with... and electrum and it's not opening anything
I don't have a clue of what the password may be, probably something random I came up at the time but it ends up I started using electrum to receive some coins after my qt broke and didn't realize this about password until I tried to spend my first coins. So, without password and seed does it mean I lost my coins?
Open electrum and go to File > Open wallet (something like that) and then select that wallet file and it should open it. |
|
|
|
|
What is a public bitcoin server? I've never heard of one before since Bitcoin doesn't use public servers, or connects to other peers.
Why do you need 40Gb? Well you don't, if you don't want security. The point of having the whole blockchain is to have security so that you don't need to trust anyone else to provide you the right data. You need it to independently verify everything.
As for the rest, about the databases and shutting down, it takes a while because the entire bitcoin blockchain needs to be scanned to build the databases. It only takes a while the first time. Shutting down needs to wait for bitcoin core to close properly do they it does not screw up the blockchain databases.
|
|
|
|
You are missing everything. Bitcoins work on a different security algorithm, simply modifying transactions and sending bitcoins to your address will never happen.
Wallet providers are not idiots, they use multi layered security and these methods won't work for it. I don't know the actual method, as I'm not interested in doing hacking. But, whatever it is.. It is complicated.
It is not just the wallet, it is built into the bitcoin protocol itself. |
|
|
|
|
Show Posts
