Don't be sorry when you are giving good advice.
What the heck is the test net? lol
I code JSON and all that on the live blockchain.
There is a separate bitcoin network exclusively for testing. The coins are easily gotten from testnet faucets and they are worthless so that if you screw something up like you did here, nothing of value is actually lost. What do you mean there are no timestamps on transactions?
Yes, there are timestamps on transactions.
Look at blockchain.info They have dates, and times. Even the value at the time of trnsaction is logged.
Transactions do not have time stamps. There is no field in a transaction for a time stamp. They are not necessary. The timestamps you see in blockchain.info are the timestamps that their node first saw your transaction. This can be completely inaccurate. What is it with people "registering their child's birth on the block chain" How do you add messages into the block chain?
There are a lot of ways to put data in the blockchain Some people use OP_RETURN. Others create special addresses and the data is stored as hex. |
|
|
|
I am resigning the campaign, effective today. Adding arbitrary requirements just to withdraw from a sig campaign is a little too much for trivial amounts of btc.
Thanks for everything, I guess latest "payment" you can keep.
I think that the withdraw issue was only with knowhow since he got some bonus that requires playing to withdraw. I received my withdraw fine and everything went through ok. |
|
|
|
my password is probably very weak, probably a word followed by numbers. Is there any way I could brute force this with software or is it a highly technical job?
There is software that can help you. Shorena linked one above. Just do a google search and you should be able to find some tools that can help. Just be careful since some of them might be viruses. |
|
|
|
I was just testing at the time, I was pretty sure I would never use the program so I probably just looked at some random thing, added 123 in the end and that was it but it's impossible to know.. I mean I can try a bunch of things but so far I've got nothing. Don't they have protection from brute force anyway?
In the sense that if you have absolutely know idea what to look for, then it will pretty much be impossible. Although weak passwords are of course still vulnerable. The unlocking mechanism and hash could also take time and that will slow down brute force attacks. If I don't remember the password does that mean I can't recover the coins?
Yeah, pretty much. |
|
|
|
I have been up and down and in and out of the bitcoin codebase and have pondered many, many design characteristics of bitcoin, some seem absolutely unreasonable on first thought, especially given how easy they would be to change with a few lines of code. However, for each, after much thought and reasoning, I have realized the subtle brilliance of some of these seeming mistakes.
From my experiences, I am confident that the presence of empty blocks is a design feature that was considered and their presence is desirable. That we haven't figured out the logic behind their existence does not mean that they are a bad thing, it just means that we haven't thought hard enough about why they strengthen the protocol.
I haven't thought about this issue, so I can't give a good reason why they are permitted.
Because without empty blocks, times when there are no transactions (like in the beginning of Bitcoin) requires empty blocks. Otherwise the network could never grow and it would never have worked. The code that allows them must stay in in case of situations that may arise due to people not spending for some reason. It allows mining to continue at such times. |
|
|
|
yes
i added exclusions already
anu more ideas ?
Have you tried submitting a bug report to Armory? |
|
|
|
|
Do you have something like an antivirus that could be accessing the databases while armory is trying to reindex? Antivirus software have been known to corrupt those files causing these kinds of errors. If you do have one enabled, disable it or add armory data directory to the exceptions.
|
|
|
|
Confirmed, rating removed, thanks for the mail. I also confirm this. |
|
|
|
i edit the previous message with log, it was off by a lot core was something like 333000 armory was 222000 (not actual nbr). and my wallet was empty  It looks like it is still organizing the blockchain. Your wallet is empty because it's databases aren't fully synced yet. |
|
|
|
this morning armory was OK
but blocks were off the chart
there was a diffence with blocks between bitcoin core and armory
armory was waaaay off .
How can i fix that ?
note that afer restart armory is still organizing blockchain.
How far off? What did you see? |
|
|
|
|
Maybe you should update your software, I think that's your fix. You are using an old beta software, of course it will be slow. Many optimization and improvement changes have been made to armory and bitcoin core. The latest versions are 0.93.3 for armory and 0.11.2 for bitcoin core.
The master private key cannot be imported into another wallet since it uses a different format. You can export the other private keys that have your bitcoin and import those to another wallet though.
|
|
|
|
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. |
|
|
|
|
Show Posts
