Bitcoin Forum
December 03, 2016, 10:10:13 PM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 [83] 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 ... 232 »
  Print  
Author Topic: Armory - Discussion Thread  (Read 481572 times)
etotheipi
Legendary
*
Offline Offline

Activity: 1428


Core Armory Developer


View Profile WWW
December 19, 2012, 01:12:04 PM
 #1641

On the topic of testing... anyone currently using it?  Any problems with it?  It's mostly small updates, so I don't expect a lot to go wrong with it.  But I still need some feedback to know for sure.

I would like to test dev releases.
I am a bit vary about using the dev branch of a beta software on funds, though..
What would you, generally, suggest as a good way to handle this?
Of course I have external backups of the wallet files.

Ente

I would only be concerned if I make updates to the wallet code, thus risking the possibility of making errors in computing addresses, etc.  But the wallet code hasn't been touched in months (except for some tweaks to the keypool). 

When I make the new wallet, I expect people will want to test on testnet first, or with smaller amounts of coins.  For these types of releases, though, the worst thing that will happen is that pressing some buttons will throw errors strange errors, or maybe even crash Armory.  If that happens, please send me the log file.  But I wouldn't worry about losing coins...

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
1480803013
Hero Member
*
Offline Offline

Posts: 1480803013

View Profile Personal Message (Offline)

Ignore
1480803013
Reply with quote  #2

1480803013
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1480803013
Hero Member
*
Offline Offline

Posts: 1480803013

View Profile Personal Message (Offline)

Ignore
1480803013
Reply with quote  #2

1480803013
Report to moderator
1480803013
Hero Member
*
Offline Offline

Posts: 1480803013

View Profile Personal Message (Offline)

Ignore
1480803013
Reply with quote  #2

1480803013
Report to moderator
1480803013
Hero Member
*
Offline Offline

Posts: 1480803013

View Profile Personal Message (Offline)

Ignore
1480803013
Reply with quote  #2

1480803013
Report to moderator
Ente
Legendary
*
Offline Offline

Activity: 1834



View Profile
December 19, 2012, 05:11:05 PM
 #1642

Thanks for the info!
I tried to install the dev version with
Quote
sudo git checkout remotes/origin/dev

Starting Armory fails with this now:
Quote
python /opt/BitcoinArmory/ArmoryQt.py &
[1] 15125
user@machine:/opt/BitcoinArmory$ ********************************************************************************
Loading Armory Engine:
   Armory Version:       0.82.5
   PyBtcWallet  Version: 1.35
Detected Operating system: Linux
   User home-directory   : /home/user
   Satoshi BTC directory : /home/user/.bitcoin/
   Armory home dir       : /home/user/.armory/
(ERROR) Traceback (most recent call last):
  File "/opt/BitcoinArmory/ArmoryQt.py", line 2603, in <module>
    form = ArmoryMainWindow()
  File "/opt/BitcoinArmory/ArmoryQt.py", line 349, in __init__
    self.loadBlockchain()
  File "/opt/BitcoinArmory/ArmoryQt.py", line 1232, in loadBlockchain
    BDM_LoadBlockchainFile()
  File "/opt/BitcoinArmory/armoryengine.py", line 1153, in BDM_LoadBlockchainFile
    return TheBDM.parseEntireBlockchain(blkdir)
  File "/opt/BitcoinArmory/CppBlockUtils.py", line 1229, in parseEntireBlockchain
    def parseEntireBlockchain(self, *args): return _CppBlockUtils.BlockDataManager_FileRefs_parseEntireBlockchain(self, *args)
NotImplementedError: Wrong number of arguments for overloaded function 'BlockDataManager_FileRefs_parseEntireBlockchain'.
  Possible C/C++ prototypes are:
    parseEntireBlockchain(BlockDataManager_FileRefs *,uint32_t)
    parseEntireBlockchain(BlockDataManager_FileRefs *)


Traceback (most recent call last):
  File "/opt/BitcoinArmory/ArmoryQt.py", line 2603, in <module>
    form = ArmoryMainWindow()
  File "/opt/BitcoinArmory/ArmoryQt.py", line 349, in __init__
    self.loadBlockchain()
  File "/opt/BitcoinArmory/ArmoryQt.py", line 1232, in loadBlockchain
    BDM_LoadBlockchainFile()
  File "/opt/BitcoinArmory/armoryengine.py", line 1153, in BDM_LoadBlockchainFile
    return TheBDM.parseEntireBlockchain(blkdir)
  File "/opt/BitcoinArmory/CppBlockUtils.py", line 1229, in parseEntireBlockchain
    def parseEntireBlockchain(self, *args): return _CppBlockUtils.BlockDataManager_FileRefs_parseEntireBlockchain(self, *args)
NotImplementedError: Wrong number of arguments for overloaded function 'BlockDataManager_FileRefs_parseEntireBlockchain'.
  Possible C/C++ prototypes are:
    parseEntireBlockchain(BlockDataManager_FileRefs *,uint32_t)
    parseEntireBlockchain(BlockDataManager_FileRefs *)


[1]+  Exit 1                  python /opt/BitcoinArmory/ArmoryQt.py

So, am I an effective bugfinder already? :-P

Ente
etotheipi
Legendary
*
Offline Offline

Activity: 1428


Core Armory Developer


View Profile WWW
December 19, 2012, 05:22:41 PM
 #1643

Ente

Actually, I think you just need to recompile.  Just type "make".  And you shouldn't do a checkout on the remotes/origin directly.   Just "git checkout dev" then do a "git pull origin dev".

Otherwise,  that's the right spirit!  Just compile it first,  *then* look for bugs :-)

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
K1773R
Legendary
*
Offline Offline

Activity: 1526


/dev/null


View Profile
December 19, 2012, 05:23:59 PM
 #1644

Ente

Actually, I think you just need to recompile.  Just type "make".  And you shouldn't do a checkout on the remotes/origin directly.   Just "git checkout dev" then do a "git pull origin dev".

Otherwise,  that's the right spirit!  Just compile it first,  *then* look for bugs :-)
dont forget the make clean Wink

[GPG Public Key]  [Devcoin Builds]  [BBQCoin Builds]  [Multichain Blockexplorer]  [Multichain Blockexplorer - PoS Coins]  [Ufasoft Miner Linux Builds]
BTC/DVC/TRC/FRC: 1K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y ANC/XPM AK1773RTmRKtvbKBCrUu95UQg5iegrqyeA NMC: NK1773Rzv8b4ugmCgX789PbjewA9fL9Dy1 LTC: LKi773RBuPepQH8E6Zb1ponoCvgbU7hHmd EMC: EK1773RxUes1HX1YAGMZ1xVYBBRUCqfDoF BQC: bK1773R1APJz4yTgRkmdKQhjhiMyQpJgfN
Ente
Legendary
*
Offline Offline

Activity: 1834



View Profile
December 19, 2012, 05:54:47 PM
 #1645

Ente

Actually, I think you just need to recompile.  Just type "make".  And you shouldn't do a checkout on the remotes/origin directly.   Just "git checkout dev" then do a "git pull origin dev".

Otherwise,  that's the right spirit!  Just compile it first,  *then* look for bugs :-)

dont forget the make clean Wink

Whoops!
Thank you, you two! Running on dev now! :-)

Ente
chrisrico
Hero Member
*****
Offline Offline

Activity: 496


View Profile
December 19, 2012, 10:05:20 PM
 #1646

There doesn't seem to be anything interesting in Armory's log (even with --debug), but when I first start it up I get these notifications in Bitcoin's debug.log...

Code:
accepted connection 127.0.0.1:57797
accepted connection 127.0.0.1:57798
disconnecting node 127.0.0.1:57797
disconnecting node 127.0.0.1:57798
accepted connection 127.0.0.1:57799
disconnecting node 127.0.0.1:57799
accepted connection 127.0.0.1:57801
accepted connection 127.0.0.1:57802
disconnecting node 127.0.0.1:57802
disconnecting node 127.0.0.1:57801
Ploo
Full Member
***
Offline Offline

Activity: 125


View Profile
December 20, 2012, 12:25:34 PM
 #1647

Is there anywhere I can read about the wallet specification without delving into armory source?
etotheipi
Legendary
*
Offline Offline

Activity: 1428


Core Armory Developer


View Profile WWW
December 20, 2012, 02:52:57 PM
 #1648

Is there anywhere I can read about the wallet specification without delving into armory source?

Indeed!  It's on the webpage:  http://bitcoinarmory.com/index.php/armory-wallet-files

However, I'm working on a new wallet format now, so that will be changing pretty substantially in the near future, but there's also a lot of work left to be done (so maybe not near-near future...)

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
Winterfrost
Full Member
***
Offline Offline

Activity: 149


GPG 0FC76C1241E39BF6


View Profile
December 20, 2012, 08:26:55 PM
 #1649

I've been trying to use Armory on netbook (EeePC 1005HAB), and I've run into a couple problems:
 1. When I start Armory in online-mode, it hangs at scanning the blockchain. The program says "Connected (0 blocks)" and endlessly scans. I've let it run overnight to no avail.
 2. Armory randomly drops the connection to bitcoin-qt and reconnects a second later. This tends to happen a number of times consecutively.

You mentioned that Armory is fairly RAM intensive - could this be the cause? It's running Windows 7 32-bit and Armory 0.86.2-beta.

Thanks,
--winter

1winteru2GkEyqLGK95WVCHwBBpGRJXW1
etotheipi
Legendary
*
Offline Offline

Activity: 1428


Core Armory Developer


View Profile WWW
December 20, 2012, 08:32:18 PM
 #1650

I've been trying to use Armory on netbook (EeePC 1005HAB), and I've run into a couple problems:
 1. When I start Armory in online-mode, it hangs at scanning the blockchain. The program says "Connected (0 blocks)" and endlessly scans. I've let it run overnight to no avail.
 2. Armory randomly drops the connection to bitcoin-qt and reconnects a second later. This tends to happen a number of times consecutively.

You mentioned that Armory is fairly RAM intensive - could this be the cause? It's running Windows 7 32-bit and Armory 0.86.2-beta.

Thanks,
--winter

If you have 2GB or less, I'm guessing Armory won't work very well (perhaps like what you said).  Before SatoshiDice came along, it was fine, but even just indexing pointers to data on disk is over 1 GB now.  I started upgrading Armory to switch to disk-based indexing (which really needed to be done eventually, but I didn't realize it was going to be so soon!), but it's turning out to be a pretty substantial upgrade for Armory.  It will happen in the next month or two, though ...

The bitcoin-qt disconnect-reconnect cycle is a side effect of your system thrashing.  It can happen when bitcoin-qt isn't fully sync'ed with the network yet and Armory is struggling to keep up with the blocks, or when you don't have enough RAM to build the blockchain index. 

I wish I had better news for you...

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
K1773R
Legendary
*
Offline Offline

Activity: 1526


/dev/null


View Profile
December 20, 2012, 08:42:41 PM
 #1651

I've been trying to use Armory on netbook (EeePC 1005HAB), and I've run into a couple problems:
 1. When I start Armory in online-mode, it hangs at scanning the blockchain. The program says "Connected (0 blocks)" and endlessly scans. I've let it run overnight to no avail.
 2. Armory randomly drops the connection to bitcoin-qt and reconnects a second later. This tends to happen a number of times consecutively.

You mentioned that Armory is fairly RAM intensive - could this be the cause? It's running Windows 7 32-bit and Armory 0.86.2-beta.

Thanks,
--winter

If you have 2GB or less, I'm guessing Armory won't work very well (perhaps like what you said).  Before SatoshiDice came along, it was fine, but even just indexing pointers to data on disk is over 1 GB now.  I started upgrading Armory to switch to disk-based indexing (which really needed to be done eventually, but I didn't realize it was going to be so soon!), but it's turning out to be a pretty substantial upgrade for Armory.  It will happen in the next month or two, though ...

The bitcoin-qt disconnect-reconnect cycle is a side effect of your system thrashing.  It can happen when bitcoin-qt isn't fully sync'ed with the network yet and Armory is struggling to keep up with the blocks, or when you don't have enough RAM to build the blockchain index.  

I wish I had better news for you...
there is a workaround (still a bit slow armory but a working one).
install linux with a big swap (atleast 4GB, best 8GB)
set swapiness (google) to 100
run armory and enjoy Wink

[GPG Public Key]  [Devcoin Builds]  [BBQCoin Builds]  [Multichain Blockexplorer]  [Multichain Blockexplorer - PoS Coins]  [Ufasoft Miner Linux Builds]
BTC/DVC/TRC/FRC: 1K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y ANC/XPM AK1773RTmRKtvbKBCrUu95UQg5iegrqyeA NMC: NK1773Rzv8b4ugmCgX789PbjewA9fL9Dy1 LTC: LKi773RBuPepQH8E6Zb1ponoCvgbU7hHmd EMC: EK1773RxUes1HX1YAGMZ1xVYBBRUCqfDoF BQC: bK1773R1APJz4yTgRkmdKQhjhiMyQpJgfN
Winterfrost
Full Member
***
Offline Offline

Activity: 149


GPG 0FC76C1241E39BF6


View Profile
December 20, 2012, 09:29:50 PM
 #1652


If you have 2GB or less, I'm guessing Armory won't work very well (perhaps like what you said).  Before SatoshiDice came along, it was fine, but even just indexing pointers to data on disk is over 1 GB now.  I started upgrading Armory to switch to disk-based indexing (which really needed to be done eventually, but I didn't realize it was going to be so soon!), but it's turning out to be a pretty substantial upgrade for Armory.  It will happen in the next month or two, though ...

The bitcoin-qt disconnect-reconnect cycle is a side effect of your system thrashing.  It can happen when bitcoin-qt isn't fully sync'ed with the network yet and Armory is struggling to keep up with the blocks, or when you don't have enough RAM to build the blockchain index. 

I wish I had better news for you...

That's what I figured, but I thought it was worth checking. I'll just re-purpose another machine until you finish the upgrade.

Thanks again.

1winteru2GkEyqLGK95WVCHwBBpGRJXW1
etotheipi
Legendary
*
Offline Offline

Activity: 1428


Core Armory Developer


View Profile WWW
December 21, 2012, 05:29:18 AM
 #1653

Well, what a pain in the @$$.  Github has decided they no longer support uploading files.  I was paying an exorbitant amount to them for a premium acct just to have that feature.  Oh well.  Onto Amazon S3...

I'm fairly comfortable with the 0.86.2 as-is, so I basically just moved the existing installers over to my offline system for signing, and then brought them back for an official release.  I just uploaded them to my new Amazon S3 account.  Let's find out if it works:

https://s3.amazonaws.com/BitcoinArmoryReleases/0.86.2-beta/armory_0.86.2-beta_win64.msi
https://s3.amazonaws.com/BitcoinArmoryReleases/0.86.2-beta/armory_0.86.2-beta_windows_all.msi
https://s3.amazonaws.com/BitcoinArmoryReleases/0.86.2-beta/armory_0.86.2_amd64.deb
https://s3.amazonaws.com/BitcoinArmoryReleases/0.86.2-beta/armory_0.86.2_i386.deb

And, I saw no reason not to switch to using SHA256 for hashing the installers into a signed release file, so that's what I did.  If you were previously downloading the .asc file and checking the hashes with "md5sum *.deb *.msi", just change that to "sha256sum *.deb *.msi". 

Once I hear back from people that the downloads work, I will update the website and the merge it into master (and tag and sign the repo).

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
cypherdoc
Legendary
*
Offline Offline

Activity: 1764



View Profile
December 22, 2012, 08:51:49 PM
 #1654

great work.
prezbo
Sr. Member
****
Offline Offline

Activity: 422


View Profile
December 22, 2012, 09:18:07 PM
 #1655

I ran the new version, it said that armory is online but none of the transactions appeared.

Might be because I created a new wallet while it was synching, and got a bunch of these errors:
Code:
TypeError: Non-hexadecimal digit found
2012-12-22 22:15 (INFO) -- ArmoryQt.py:3199 - Dashboard switched to fully-online mode
2012-12-22 22:15 (INFO) -- ArmoryQt.py:1632 - Syncing wallet: 32h6U5vjR
2012-12-22 22:15 (ERROR) -- ArmoryQt.py:3442 - Error in heartbeat function
Traceback (most recent call last):
  File "ArmoryQt.py", line 3300, in Heartbeat
  File "ArmoryQt.py", line 1635, in finishLoadBlockchain
  File "armoryengine.pyc", line 6835, in detectHighestUsedIndex
  File "armoryengine.pyc", line 939, in int_to_binary
  File "armoryengine.pyc", line 917, in hex_to_binary
  File "encodings\hex_codec.pyc", line 42, in hex_decode

all these errors are only linked to the newly created wallet.

edit: tried it again, this time didn't do anything at all, the result is still the same, no transactions show up.
edit 2: permanently deleted the wallet in question and all transactions suddenly showed up.
etotheipi
Legendary
*
Offline Offline

Activity: 1428


Core Armory Developer


View Profile WWW
December 23, 2012, 12:34:18 AM
 #1656

I ran the new version, it said that armory is offline but none of the transactions appeared.

Might be because I created a new wallet while it was synching, and got a bunch of these errors:
Code:
TypeError: Non-hexadecimal digit found
2012-12-22 22:15 (INFO) -- ArmoryQt.py:3199 - Dashboard switched to fully-online mode
2012-12-22 22:15 (INFO) -- ArmoryQt.py:1632 - Syncing wallet: 32h6U5vjR
2012-12-22 22:15 (ERROR) -- ArmoryQt.py:3442 - Error in heartbeat function
Traceback (most recent call last):
  File "ArmoryQt.py", line 3300, in Heartbeat
  File "ArmoryQt.py", line 1635, in finishLoadBlockchain
  File "armoryengine.pyc", line 6835, in detectHighestUsedIndex
  File "armoryengine.pyc", line 939, in int_to_binary
  File "armoryengine.pyc", line 917, in hex_to_binary
  File "encodings\hex_codec.pyc", line 42, in hex_decode

all these errors are only linked to the newly created wallet.

edit: tried it again, this time didn't do anything at all, the result is still the same, no transactions show up.
edit 2: permanently deleted the wallet in question and all transactions suddenly showed up.

Crap!  As usual, what seemed like an arbitrarily small update to fix something small, resulted in breaking something subtle.  I can see how it is possible to have negative values for a number that is encoded as a positive number and would throw that error.  Fixed a bug, made another one.

I really need to start bug bounties or something.  This bug is really only triggered on new wallets, which would be a disaster for new users, but very few users on this thread are creating new wallets.  I think I'll start a 0.1 BTC/bug bounty, for a month.  If someone has ideas for how to run this in a sane way that won't result in lots of disputes, I'm all for it.  I think it could also be a good marketing ploy -- some users would probably start using Armory just to try to get bounties! 

Looks like I have to fix that bug, and recompile and re-sign everything.  Ugh!   But thanks, prezbo, you actually saved me a lot of heartache from new users having bad experiences!

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
prezbo
Sr. Member
****
Offline Offline

Activity: 422


View Profile
December 23, 2012, 12:57:07 AM
 #1657

I ran the new version, it said that armory is offline but none of the transactions appeared.

Might be because I created a new wallet while it was synching, and got a bunch of these errors:
Code:
TypeError: Non-hexadecimal digit found
2012-12-22 22:15 (INFO) -- ArmoryQt.py:3199 - Dashboard switched to fully-online mode
2012-12-22 22:15 (INFO) -- ArmoryQt.py:1632 - Syncing wallet: 32h6U5vjR
2012-12-22 22:15 (ERROR) -- ArmoryQt.py:3442 - Error in heartbeat function
Traceback (most recent call last):
  File "ArmoryQt.py", line 3300, in Heartbeat
  File "ArmoryQt.py", line 1635, in finishLoadBlockchain
  File "armoryengine.pyc", line 6835, in detectHighestUsedIndex
  File "armoryengine.pyc", line 939, in int_to_binary
  File "armoryengine.pyc", line 917, in hex_to_binary
  File "encodings\hex_codec.pyc", line 42, in hex_decode

all these errors are only linked to the newly created wallet.

edit: tried it again, this time didn't do anything at all, the result is still the same, no transactions show up.
edit 2: permanently deleted the wallet in question and all transactions suddenly showed up.

Crap!  As usual, what seemed like an arbitrarily small update to fix something small, resulted in breaking something subtle.  I can see how it is possible to have negative values for a number that is encoded as a positive number and would throw that error.  Fixed a bug, made another one.
As someone who used to have this same problem I totally get it. It helped me to purposely slow down my programming. Smiley

Quote
I really need to start bug bounties or something.  This bug is really only triggered on new wallets, which would be a disaster for new users, but very few users on this thread are creating new wallets.  I think I'll start a 0.1 BTC/bug bounty, for a month.  If someone has ideas for how to run this in a sane way that won't result in lots of disputes, I'm all for it.  I think it could also be a good marketing ploy -- some users would probably start using Armory just to try to get bounties!  
I always make a new wallet to check new functionality with, so you have this approach covered Smiley

Quote
Looks like I have to fix that bug, and recompile and re-sign everything.  Ugh!   But thanks, prezbo, you actually saved me a lot of heartache from new users having bad experiences!
Not a problem, that's why we are here.

I'm currently very busy (writing my master thesis), but have been looking for a way to contribute to the bitcoin comunity (with a degree in computer science and mathematics I think I might have something to give), and after that I'd be happy to help you with anything you might need (I guess code reviews never hurt). I don't think I've ever been as impressed with any piece of software as I am with armory.
etotheipi
Legendary
*
Offline Offline

Activity: 1428


Core Armory Developer


View Profile WWW
December 23, 2012, 03:20:41 AM
 #1658

I always make a new wallet to check new functionality with, so you have this approach covered Smiley

That is not a subtle bug at all!  I just tested creating a new wallet and it really fails!  I probably didn't notice it because it doesn't trigger if you create the wallet after the blockchain is loaded.  It only triggers if the wallet has never been used at the time the initial blockchain scan finishes.

I'm currently very busy (writing my master thesis), but have been looking for a way to contribute to the bitcoin comunity (with a degree in computer science and mathematics I think I might have something to give), and after that I'd be happy to help you with anything you might need (I guess code reviews never hurt). I don't think I've ever been as impressed with any piece of software as I am with armory.

Well, thanks!  And I'm always happy to have people help out.  Dig into the code, maybe even develop new features.  If you want to get involved, please email me and I'll give you little homework assignments that will get you acquainted with the code and might be useful, too! 



I just fixed the bug in my local copy of the github repo, but github is down for maintenance, so I can't sync any of my other virtual machines in order to compile the new version.  Gah!  As soon as it's back up, I'll be releasing it officially as 0.86.3-beta.

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
etotheipi
Legendary
*
Offline Offline

Activity: 1428


Core Armory Developer


View Profile WWW
December 23, 2012, 06:38:08 AM
 #1659

Please Sanity Check v0.86.3-beta!

I just posted a v0.86.3-beta to the new AmazonS3 "bucket."  The Get Armory! page now references the new download location, and I need to make sure everyone has access, and that there's no other stupid bugs that will require further fixes before I trigger version notifications.

I haven't merged it into master yet, because I don't want to trigger any notifications until I get this sanity check.  But I did create a signed tag and pushed it to github:  "v0.86.3-beta".  You can check that out right now and play with it.  ("git tag -v v0.86.3-beta" to verify the signature)



I want to start bug-bounties.  Something like 0.1 BTC per new bug you discover.  If you report a significant bug, and there's no one else has mentioned it since the last release, I'll send you 0.1 BTC.  Of course, this won't be so clean, because what is a "significant" bug?  What qualifies as a bug vs. a missing feature?  I don't want to be stingy about it, but I also don't want people to start expecting payment for pointing out missing punctuation in a warning box.... or maybe I should be paying for such tiny things...?

Please feel free to discuss how I might do execute this idea with the best efficiency.  I'm thinking I'll start by doing it for 2 weeks only, and with a maximum of 3 BTC paid out (30 bugs) in that two weeks.  That will limit my risk of unexpected abuses.  Also, I probably won't send out the 0.1 right away, unless someone requests it.  If the bug reports are coming in quickly, I will aggregate multiple payouts into one transaction.  I am considering posting it in the main discussion forum, but I might get too much attention.

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
prezbo
Sr. Member
****
Offline Offline

Activity: 422


View Profile
December 23, 2012, 09:51:16 AM
 #1660

Well, thanks!  And I'm always happy to have people help out.  Dig into the code, maybe even develop new features.  If you want to get involved, please email me and I'll give you little homework assignments that will get you acquainted with the code and might be useful, too!  

That sounds like a lot of fun, will let you know when I'm done.

I can confirm this bug is fixed.
Pages: « 1 ... 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 [83] 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 ... 232 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!