Topic: Armory - Discussion Thread - page 98. (Read 521829 times)
Congrats Alan! And take some time off to enjoy it
By the way, another article written about me (and Armory) yesterday
http://www.paymentssource.com/news/a-rocket-scientist-takes-on-bitcoin-security-3015575-1.html
Update for those that are waiting: it looks like I'm not going to get a lot done this week. Wedding preparation is, of course, pretty time-consuming. And then next week is the honeymoon -- and I think my soon-to-be-wife deserves an Armory-free honeymoon (and it would probably be good for me, too).
I'm going to try putting out an "alternate download" on the website, which will just 0.89.99.5. If I get some time in the evening, I might try to hunt down that startup bug. Or at least identify when it's happening and then close/restart. I just won't be able to get to the full release ironed out before I get back from the honeymoon.
http://www.paymentssource.com/news/a-rocket-scientist-takes-on-bitcoin-security-3015575-1.html
Update for those that are waiting: it looks like I'm not going to get a lot done this week. Wedding preparation is, of course, pretty time-consuming. And then next week is the honeymoon -- and I think my soon-to-be-wife deserves an Armory-free honeymoon (and it would probably be good for me, too).
I'm going to try putting out an "alternate download" on the website, which will just 0.89.99.5. If I get some time in the evening, I might try to hunt down that startup bug. Or at least identify when it's happening and then close/restart. I just won't be able to get to the full release ironed out before I get back from the honeymoon.
Shortly after I updated BTC-qt to 8.5.1, I had Armory (0.87.2) losing and reacquiring the connection with BTC-qt every second or so. Closed+reopened Armory a couple of times. No change. Idem with BTC-qt closed+reopened (Armory closed), again no change. Had to reboot the PC (W7 x64). Anyone else had this before?
It's probably not actually connecting and reconnecting. It doesn't seem to handle notifications correctly in W7 (at least). If you receive a payment, the same can happen, where it "flickers" repeatedly on the screen for 2-10 minutes. I'd guess it lost connection once, then started "flickering." This happens to me more often than not using same version on same OS.The strange thing is that it had never happened (to me) before. I can't really really try 0.88 as it just won't open.
But, this might be the problem:
"ArmoryQt.py:3603 - Another Armory instance just tried to open."
Why it would do that, I have no idea...
Shortly after I updated BTC-qt to 8.5.1, I had Armory (0.87.2) losing and reacquiring the connection with BTC-qt every second or so. Closed+reopened Armory a couple of times. No change. Idem with BTC-qt closed+reopened (Armory closed), again no change. Had to reboot the PC (W7 x64). Anyone else had this before?
It's probably not actually connecting and reconnecting. It doesn't seem to handle notifications correctly in W7 (at least). If you receive a payment, the same can happen, where it "flickers" repeatedly on the screen for 2-10 minutes. I'd guess it lost connection once, then started "flickering." This happens to me more often than not using same version on same OS.
Shortly after I updated BTC-qt to 8.5.1, I had Armory (0.87.2) losing and reacquiring the connection with BTC-qt every second or so. Closed+reopened Armory a couple of times. No change. Idem with BTC-qt closed+reopened (Armory closed), again no change. Had to reboot the PC (W7 x64). Anyone else had this before?
No, I can't see the transaction on blockchain.info as it is not in the blockchain.
Armory tells me the following (have restarted another time):
Block Number: Not in the blockchain yet
Transaction Time: 2013-Sep-27 12:21
Transaction Direction: Sent
Meanwhile Armory shows block 260418, so I'm connected and synchronized.
Blockchain.info shows the money resides still in my wallet while Armory remains in status 'send' with '0 confirmations' and 'Not in the blockchain yet' .
Just in case it may matter:
I had a lower transaction fee at first, but then was asked for 0,0005 by Armory which I agreed on, then the transaction was processed.
I'm not sure whether the network connection was interrupted during it has been sent, as I was connected via my mobile to the internet.
Is there any kind of command which re-propagates a transaction or reverts my deadlock somehow ??
Armory tells me the following (have restarted another time):
Block Number: Not in the blockchain yet
Transaction Time: 2013-Sep-27 12:21
Transaction Direction: Sent
Meanwhile Armory shows block 260418, so I'm connected and synchronized.
Blockchain.info shows the money resides still in my wallet while Armory remains in status 'send' with '0 confirmations' and 'Not in the blockchain yet' .
Just in case it may matter:
I had a lower transaction fee at first, but then was asked for 0,0005 by Armory which I agreed on, then the transaction was processed.
I'm not sure whether the network connection was interrupted during it has been sent, as I was connected via my mobile to the internet.
Is there any kind of command which re-propagates a transaction or reverts my deadlock somehow ??
Close Armory (and Bitcoin-Qt, if running it yourself). Delete mempool.bin from your Armory home directory, then restart Armory. The tx will be forgotten and you can try again.
No, I can't see the transaction on blockchain.info as it is not in the blockchain.
Armory tells me the following (have restarted another time):
Block Number: Not in the blockchain yet
Transaction Time: 2013-Sep-27 12:21
Transaction Direction: Sent
Meanwhile Armory shows block 260418, so I'm connected and synchronized.
Blockchain.info shows the money resides still in my wallet while Armory remains in status 'send' with '0 confirmations' and 'Not in the blockchain yet' .
Just in case it may matter:
I had a lower transaction fee at first, but then was asked for 0,0005 by Armory which I agreed on, then the transaction was processed.
I'm not sure whether the network connection was interrupted during it has been sent, as I was connected via my mobile to the internet.
Is there any kind of command which re-propagates a transaction or reverts my deadlock somehow ??
Armory tells me the following (have restarted another time):
Block Number: Not in the blockchain yet
Transaction Time: 2013-Sep-27 12:21
Transaction Direction: Sent
Meanwhile Armory shows block 260418, so I'm connected and synchronized.
Blockchain.info shows the money resides still in my wallet while Armory remains in status 'send' with '0 confirmations' and 'Not in the blockchain yet' .
Just in case it may matter:
I had a lower transaction fee at first, but then was asked for 0,0005 by Armory which I agreed on, then the transaction was processed.
I'm not sure whether the network connection was interrupted during it has been sent, as I was connected via my mobile to the internet.
Is there any kind of command which re-propagates a transaction or reverts my deadlock somehow ??
Please forgive me not reading all previous pages, in case this is a well known issue discussed before.
Yesterday's evening I send BTC with Armory, nevertheless it currently shows today 12:21GMT+2 as send date.
Armory several times restarted since yesterday.
Armory is connected to the bitcoin network and synchronized.
Current block is 260392, 12:50 GMT+2.
Transaction still has 0 confirmations and status 'Not in the blockchain yet'
Transaction fee is 0.0005BTC.
Any advice would be appreciated!
Can you see the transaction on blochchain.info? If so, the transaction has been transmitted correctly but may depend on unconfirmed inputs, have a huge size and too low fee, or something.Yesterday's evening I send BTC with Armory, nevertheless it currently shows today 12:21GMT+2 as send date.
Armory several times restarted since yesterday.
Armory is connected to the bitcoin network and synchronized.
Current block is 260392, 12:50 GMT+2.
Transaction still has 0 confirmations and status 'Not in the blockchain yet'
Transaction fee is 0.0005BTC.
Any advice would be appreciated!
If it is not on blockchain.info, then armory has not sent it (or bitcoind has not relayed it), and it will never confirm.
Please forgive me not reading all previous pages, in case this is a well known issue discussed before.
Yesterday's evening I send BTC with Armory, nevertheless it currently shows today 12:21GMT+2 as send date.
Armory several times restarted since yesterday.
Armory is connected to the bitcoin network and synchronized.
Current block is 260392, 12:50 GMT+2.
Transaction still has 0 confirmations and status 'Not in the blockchain yet'
Transaction fee is 0.0005BTC.
Any advice would be appreciated!
Yesterday's evening I send BTC with Armory, nevertheless it currently shows today 12:21GMT+2 as send date.
Armory several times restarted since yesterday.
Armory is connected to the bitcoin network and synchronized.
Current block is 260392, 12:50 GMT+2.
Transaction still has 0 confirmations and status 'Not in the blockchain yet'
Transaction fee is 0.0005BTC.
Any advice would be appreciated!
I appreciate the RAM reduction effort happiness (numbers look GREAT!), but the message signing thing is really bugging me ATM. The unencrypt/re-encrypt didn't work with BTC-qt 8.3 or 8.5, so I had to export my addresses to blockchain, which I would really like to avoid. Anything else that can be done?
A bounty was claimed with a new message signing algorithm to be integrated into Armory. It includes code to be backwards compatible with Bitcoin-Qt. But this current upgrade (RAM-reduction) was so significant, that I couldn't fit everything into it. I have enough to worry about. Once I officially release it it, I'll start tending to the other important-but-less-critical upgrades like unicode issues, message signing, tx size limits, etc.
OK, I thought you might say that (I wish there were a workaround to exporting keys). Godspeed with the update.
Currently I see two alternatives:
1) Use jackjack's code externally, messing with sourcecode and python: https://bitcointalksearch.org/topic/m.2113086. That's the code which will go into Armory too.
2) Brainwallet has two tools for that: http://brainwallet.org/#sign and http://brainwallet.org/#verify. Save those locally, reboot to a live-cd with no internetconnection, do the signing.
For both you have to export the privkeys. I didn't get 1) to work properly, and will do my signing with 2) later.
Ente
1/ I won't mess with
2/ looks like a good temporary measure, I'll have to fiddle with that.
That's an improvement, thanks for sharing!
I appreciate the RAM reduction effort happiness (numbers look GREAT!), but the message signing thing is really bugging me ATM. The unencrypt/re-encrypt didn't work with BTC-qt 8.3 or 8.5, so I had to export my addresses to blockchain, which I would really like to avoid. Anything else that can be done?
A bounty was claimed with a new message signing algorithm to be integrated into Armory. It includes code to be backwards compatible with Bitcoin-Qt. But this current upgrade (RAM-reduction) was so significant, that I couldn't fit everything into it. I have enough to worry about. Once I officially release it it, I'll start tending to the other important-but-less-critical upgrades like unicode issues, message signing, tx size limits, etc.
OK, I thought you might say that (I wish there were a workaround to exporting keys). Godspeed with the update.
Currently I see two alternatives:
1) Use jackjack's code externally, messing with sourcecode and python: https://bitcointalksearch.org/topic/m.2113086. That's the code which will go into Armory too.
2) Brainwallet has two tools for that: http://brainwallet.org/#sign and http://brainwallet.org/#verify. Save those locally, reboot to a live-cd with no internetconnection, do the signing.
For both you have to export the privkeys. I didn't get 1) to work properly, and will do my signing with 2) later.
Ente
Finished building armory with latest version of LevelDB on msvc11. There are code files and instruction files to pass on, as well as some implementation specifics to discuss, maybe we should proceed in private messages so as to not bloat this thread any further.
I appreciate the RAM reduction effort happiness (numbers look GREAT!), but the message signing thing is really bugging me ATM. The unencrypt/re-encrypt didn't work with BTC-qt 8.3 or 8.5, so I had to export my addresses to blockchain, which I would really like to avoid. Anything else that can be done?
A bounty was claimed with a new message signing algorithm to be integrated into Armory. It includes code to be backwards compatible with Bitcoin-Qt. But this current upgrade (RAM-reduction) was so significant, that I couldn't fit everything into it. I have enough to worry about. Once I officially release it it, I'll start tending to the other important-but-less-critical upgrades like unicode issues, message signing, tx size limits, etc.
OK, I thought you might say that (I wish there were a workaround to exporting keys). Godspeed with the update.
By the way: in case you didn't subscribe to the other thread: I finished the last major feature/bug. Armory now properly saves all its data between loads. On my system, managing Bitcoin-Qt/bitcoind myself, I can close and reopen Armory in 19 seconds! and 260 MB of RAM.
There still a lot of missing optimizations, but this is no doubt the most usable version yet. Please try it out!
https://bitcointalksearch.org/topic/ram-reduction-backup-center-testing-version-0899916-299684
There still a lot of missing optimizations, but this is no doubt the most usable version yet. Please try it out!
https://bitcointalksearch.org/topic/ram-reduction-backup-center-testing-version-0899916-299684
I appreciate the RAM reduction effort happiness (numbers look GREAT!), but the message signing thing is really bugging me ATM. The unencrypt/re-encrypt didn't work with BTC-qt 8.3 or 8.5, so I had to export my addresses to blockchain, which I would really like to avoid. Anything else that can be done?
A bounty was claimed with a new message signing algorithm to be integrated into Armory. It includes code to be backwards compatible with Bitcoin-Qt. But this current upgrade (RAM-reduction) was so significant, that I couldn't fit everything into it. I have enough to worry about. Once I officially release it it, I'll start tending to the other important-but-less-critical upgrades like unicode issues, message signing, tx size limits, etc.
Anything new on the message-signing front? Is it still un-encrypt/encrypt again? I thought jackjack was working on sth but couldn't find an update (or missed it).
@Alan: Congrats! Now that you're incorporated and funded, I can't wait for the LTC version of Armory!
@Alan: Congrats! Now that you're incorporated and funded, I can't wait for the LTC version of Armory!
bump.
I appreciate the RAM reduction effort happiness (numbers look GREAT!), but the message signing thing is really bugging me ATM. The unencrypt/re-encrypt didn't work with BTC-qt 8.3 or 8.5, so I had to export my addresses to blockchain, which I would really like to avoid. Anything else that can be done?
Thanks.
Couldn't you export your blocks directory under nfs / samba / sshfs / etc? Or are they too far apart?
Let's do this!
https://bitcointalksearch.org/topic/ram-reduction-backup-center-testing-version-0899916-299684
Please don't use it with large amounts of money yet. It's probably still chock full of bugs, but I've done quite a bit of internal testing and feel pretty good about the major features.
Besides fixing the rescan-on-every-load issue, the feature set is frozen. I'd like to fix what's in it, rather than add anything new. A whole bunch of less-critical things (unicode fixes, message signing, tx size limits), will go into the next version (and that next version will not take 3 months to release).
Please discuss bugs & general observations in that other thread, to not clutter this one!
https://bitcointalksearch.org/topic/ram-reduction-backup-center-testing-version-0899916-299684
Please don't use it with large amounts of money yet. It's probably still chock full of bugs, but I've done quite a bit of internal testing and feel pretty good about the major features.
Besides fixing the rescan-on-every-load issue, the feature set is frozen. I'd like to fix what's in it, rather than add anything new. A whole bunch of less-critical things (unicode fixes, message signing, tx size limits), will go into the next version (and that next version will not take 3 months to release
).Please discuss bugs & general observations in that other thread, to not clutter this one!
Can we run with a remote Bitcoin instance with this version, or maybe next version? I have a server which runs a persistent node and it would be great to only have one copy of the block chain (Armory's) on my main desktop.
Not yet. That will be 100x easier to implement now, but I wanted to minimize the interface changes on this update, since there was enough turbulence with the new database engine. So it still uses the local blk*.dat files like the 0.88.1 did (though it doesn't crash on blk*.dat file splits anymore!). But now that it won't start any operations until Bitcoin-Qt/bitcoind is sync'd, and it's maintaining it's own blockchain database, it should be straightforward to upgrade it. Especially, because I was careful to make sure that the operations did not depend on the contents/structure of the blk*.dat files in anyway -- it reads them once, and then 100% of ops after that is based on its own DB. It should even handle switching to a different set of blk*.dat files between loads, as it redetects the blocks every load (part of the headers-first implementation).
Also, I'm slightly concerned about any anti-DoS measures built into Bitcoin-Qt/bitcoind which might cause unexpected issues for the user. For instance, if I restart a few times, and constantly disconnect, reconnect, and download tons of data, over and over, it might just blacklist the Armory instance. I don't expect that to happen, but I always expect something silly to crop up and eat another week of my life
Let's do this!
https://bitcointalksearch.org/topic/ram-reduction-backup-center-testing-version-0899916-299684
Please don't use it with large amounts of money yet. It's probably still chock full of bugs, but I've done quite a bit of internal testing and feel pretty good about the major features.
Besides fixing the rescan-on-every-load issue, the feature set is frozen. I'd like to fix what's in it, rather than add anything new. A whole bunch of less-critical things (unicode fixes, message signing, tx size limits), will go into the next version (and that next version will not take 3 months to release).
Please discuss bugs & general observations in that other thread, to not clutter this one!
https://bitcointalksearch.org/topic/ram-reduction-backup-center-testing-version-0899916-299684
Please don't use it with large amounts of money yet. It's probably still chock full of bugs, but I've done quite a bit of internal testing and feel pretty good about the major features.
Besides fixing the rescan-on-every-load issue, the feature set is frozen. I'd like to fix what's in it, rather than add anything new. A whole bunch of less-critical things (unicode fixes, message signing, tx size limits), will go into the next version (and that next version will not take 3 months to release
).Please discuss bugs & general observations in that other thread, to not clutter this one!
Can we run with a remote Bitcoin instance with this version, or maybe next version? I have a server which runs a persistent node and it would be great to only have one copy of the block chain (Armory's) on my main desktop.
Let's do this!
https://bitcointalksearch.org/topic/ram-reduction-backup-center-testing-version-0899916-299684
Please don't use it with large amounts of money yet. It's probably still chock full of bugs, but I've done quite a bit of internal testing and feel pretty good about the major features.
Besides fixing the rescan-on-every-load issue, the feature set is frozen. I'd like to fix what's in it, rather than add anything new. A whole bunch of less-critical things (unicode fixes, message signing, tx size limits), will go into the next version (and that next version will not take 3 months to release).
Please discuss bugs & general observations in that other thread, to not clutter this one!
https://bitcointalksearch.org/topic/ram-reduction-backup-center-testing-version-0899916-299684
Please don't use it with large amounts of money yet. It's probably still chock full of bugs, but I've done quite a bit of internal testing and feel pretty good about the major features.
Besides fixing the rescan-on-every-load issue, the feature set is frozen. I'd like to fix what's in it, rather than add anything new. A whole bunch of less-critical things (unicode fixes, message signing, tx size limits), will go into the next version (and that next version will not take 3 months to release
).Please discuss bugs & general observations in that other thread, to not clutter this one!
Jump to: