Bitcoin Forum
July 24, 2024, 11:26:54 PM *
News: Help 1Dq create 15th anniversary forum artwork.
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 [3] 4 5 6 »
41  Bitcoin / Armory / Re: OS X Minor Bugs & Questions/Requests on: March 04, 2015, 11:18:19 PM
The idea for bitcoind is when bitcoind cannot be found on OS X, notify the user to place it in /usr/bin if they can, and perhaps a checkbox to turn that dialog off if they want to manage it themselves. Perhaps the download could be hosted on the same site that Armory is downloaded from in the secure downloader.
42  Bitcoin / Armory / OS X Minor Bugs & Questions/Requests on: March 04, 2015, 08:42:32 PM
I haven't really been paying attention to this, but now it's begun to bug me. When I do something in Armory, such as sign a TX, the progress bar is just a plain progress bar. It doesn't really inform the user of exactly what it's doing. This only happens in OS X as far as I know.

Another thing that's started to bug me is that some actions on OS X have a short delay after they have been performed, such as changing wallet or address labels. The label change doesn't show until after about 3-5 seconds or until I perform the action again. I'm not sure if this happens on other systems.

Finally, A small bug with the TX comment when donating to Armory developers (thank you guys) it displays the usual comment, but with the amount in parentheses, followed by a semicolon. Ex: "Donation to Armory developers. Thank you for your generosity! (0.05);"

I have some questions too:

1. When will Armory support bitcoind management on OS X? I've got an idea on how to implement this, if you'd like to hear it.
2. Would a regular user be able to contribute to Armory development (like Bitcoin-Qt), or is this limited to the current developers?
3. Will Armory support multiple cryptocurrencies in the future?

Is it possible to implement the ability to manually edit addresses in the address book?
43  Bitcoin / Armory / Re: Configure encryption level upon re-encrypting wallet? on: March 04, 2015, 08:22:16 PM
Oh yes this is a question I've meant to ask for a while, why can wallet encryption settings not be changed by simply re-encrypting the wallet?
44  Bitcoin / Armory / Re: HW1 Wallet Support? on: March 02, 2015, 08:17:58 PM
Will support for HW1 be eventually added in the near future?
45  Bitcoin / Armory / Re: HW1 Wallet Support? on: March 02, 2015, 07:44:09 PM
Specifically I am asking about the HW1 wallet, nice to know about Trezor though
46  Bitcoin / Armory / HW1 Wallet Support? on: March 02, 2015, 01:10:43 PM
Does Armory support HW1 wallet or Trezor? If not I'd send some BTC over to the developers to start working on it, they've got APIs for Python and C. If Armory supports these, how would it be set up? If Armory does not support this I could use it with Electrum until support is added
47  Bitcoin / Armory / Re: Armory 0.93 testing release! (with 0.05 BTC bug bounty) on: March 01, 2015, 09:23:19 PM
Bug: I cannot sort transactions or wallets by clicking the top bar, but I can sort lockboxes just fine
48  Bitcoin / Armory / Re: Armory 0.93 testing release! (with 0.05 BTC bug bounty) on: February 28, 2015, 10:41:11 PM
I found another bug: When signing any multisig/simulfunding transaction that will not be broadcast yet, attempting to close the window by pressing X has no effect. Can a Done button be added to these?
49  Bitcoin / Armory / Re: Armory 0.93 testing release! (with 0.05 BTC bug bounty) on: February 25, 2015, 01:25:14 AM
I don't know if this has already been brought to developers' attention, but here:

When signing a tx (from simulfunding, or any unsigned tx really), occasionally it fails and returns this lovely message in the log:
Code:
2015-02-24 15:27 (ERROR) -- Traceback (most recent call last):
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ui/MultiSigDialogs.py", line 2716, in doSign
    self.doSignForInput(idstring, nIdx)
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ui/MultiSigDialogs.py", line 2936, in doSignForInput
    ustxi.createAndInsertSignature(pytx, addrObj.binPrivKey32_Plain)
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/Transaction.py", line 1275, in createAndInsertSignature
    derSig = self.createTxSignature(pytx, sbdPrivKey, hashcode, DetSign)
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/Transaction.py", line 1235, in createTxSignature
    raise SignatureError('No PubKey that matches this privKey')
SignatureError: No PubKey that matches this privKey
This doesn't happen often but I thought I'd report it anyway
50  Bitcoin / Armory / Re: Armory 0.93 testing release! (with 0.05 BTC bug bounty) on: February 23, 2015, 08:32:06 PM
I have a question based on the new DB size, when using supernode will the DB still be as large as it is now?
51  Bitcoin / Armory / Re: Armory 0.93 testing release! (with 0.05 BTC bug bounty) on: February 21, 2015, 05:32:41 PM
snip

I've got one last thing that keeps bothering me, yes it's the transaction details window still not showing inputs correctly, other than that I can't find anything else.

I've explained in a previous post why this will have to wait 0.93.1

Oh, my apologies, I did not see that
52  Bitcoin / Armory / Re: Armory 0.93 testing release! (with 0.05 BTC bug bounty) on: February 21, 2015, 01:05:48 PM
I've got one last thing that keeps bothering me, yes it's the transaction details window still not showing inputs correctly, other than that I can't find anything else.
53  Bitcoin / Armory / Re: Armory 0.93 testing release! (with 0.05 BTC bug bounty) on: February 18, 2015, 09:51:50 PM
I have a small feature request, when importing privkey to wallet, can an option to not rescan the DB for transactions be added for expert users?
54  Bitcoin / Armory / Re: Armory 0.93 testing release! (with 0.05 BTC bug bounty) on: February 14, 2015, 03:57:20 PM
I get the same error when trying to use coin control.
55  Bitcoin / Armory / Re: Armory 0.93 testing release! (with 0.05 BTC bug bounty) on: February 08, 2015, 08:47:01 PM
Ok, also I have 1 question and 2 more 'bugs':

In Export Key Lists, sometimes the wallet doesn't unlock properly and only displays public keys, other times it doesn't show up until i close the wallet's properties. The Goto button in the lockbox transaction is also cut off.

My question regarding the public keys is that Export Key Lists doesn't show the public key used to create lockboxes. Can this be added?

Also, I have one small request. Can a Cancel button be added to the Send Bitcoins window so that I don't have to restart Armory every time I accidentally open it? (this is the second bug)
56  Bitcoin / Armory / Re: Armory 0.93 testing release! (with 0.05 BTC bug bounty) on: February 08, 2015, 06:27:18 PM
Bug: Sometimes when receiving or sending bitcoins, it displays the notification more than once (Mac)
57  Bitcoin / Armory / Re: Armory 0.93 testing release! (with 0.05 BTC bug bounty) on: February 07, 2015, 03:30:06 PM
I found a "bug" in the armorycpplog.txt file

Log file opened at 1423312806: /Users/admin/Library/Application Support/Armory/armorycpplog.txt

There is nothing else in the log after that, but Armory has been scanning DB for the past 45 minutes.
Normally it would say 'Finished applying blocks up to (blockheight)' or something like that every 2500 blocks I believe.

You're either not looking at the right folder or the backend is stuck on something.

Yea, turns out the backend was stuck, my mistake
58  Bitcoin / Armory / Re: Armory 0.93 testing release! (with 0.05 BTC bug bounty) on: February 07, 2015, 01:29:52 PM
I found a "bug" in the armorycpplog.txt file

Log file opened at 1423312806: /Users/admin/Library/Application Support/Armory/armorycpplog.txt

There is nothing else in the log after that, but Armory has been scanning DB for the past 45 minutes.
Normally it would say 'Finished applying blocks up to (blockheight)' or something like that every 2500 blocks I believe.
59  Bitcoin / Armory / Re: Armory 0.93 testing release! (with 0.05 BTC bug bounty) on: February 06, 2015, 08:24:04 PM
I have one more small request. Can the minimum required addresses for lockbox creation be lowered to 1? I've got a multisig address that i generated in vanitygen and I can't use it. I don't know how to create it through Bitcoin Qt either Sad

I'm not sure what you mean by 1. 1-of-1 multisig address? That would be a simple P2PKH. 1-of-N? You would still need the N addresses to either fund the multisig script or redeem the P2SH script. What you have is probably a P2SH address (starts with 3?). What are the underlying addresses? You would have to import their respective private keys to your wallets and create a lockbox from that.

The only bug I can find in .6 is when I click View Details after right clicking a TX, Armory still displays transaction inputs on all incoming transactions only as Non-Standard: 3J98t1WpEZ73CNmQviecrnyiWrnqRhWNLy when that is never the case. All outgoing transactions and any incoming transactions that have inputs from my wallets or lockboxes display normally, and it does this on my Ubuntu VM as well. This isn't a major issue but it does bother me a lot.

Addresses starting with 3 are P2SH. Does it do it on addresses starting with 1?

1. Yes, vanitygen script address
2. It does this on all incoming transactions, except for those which have inputs from my wallets/lockboxes.

Also Armory keeps saying in a dialog box 'The scanning process halted unexpectedly' or something like that. I tried rebuilding but it said that again. I'm on my 2nd rebuild and rescan.
60  Bitcoin / Armory / Re: Armory 0.93 testing release! (with 0.05 BTC bug bounty) on: February 06, 2015, 11:34:20 AM
I have one more small request. Can the minimum required addresses for lockbox creation be lowered to 1? I've got a multisig address that i generated in vanitygen and I can't use it. I don't know how to create it through Bitcoin Qt either Sad
Pages: « 1 2 [3] 4 5 6 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!