Bitcoin Forum
May 12, 2024, 11:31:36 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 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 ... 233 »
981  Bitcoin / Armory / Re: 0.96.4 RC1 on: November 28, 2017, 01:08:54 AM
I have failed to reproduce the issue on my own. This has something to do with the state of your wallets. I'm going to need more data to figure out what's going. For starters, delete the .lmdb files in your datadir. They will reconstructed on the next run. See if that helps with the C++ signer.
982  Bitcoin / Armory / Re: 0.96.4 RC1 on: November 28, 2017, 12:02:16 AM
I'll try to reproduce on my end and report back here.
983  Bitcoin / Armory / Re: Core and Armory issues, need help on: November 27, 2017, 05:30:10 PM
I gave you directions, follow them.
984  Bitcoin / Armory / Re: 0.96.4 RC1 on: November 27, 2017, 02:04:56 PM
It looks like the Python signer is failing to populate the pubkey list of the unsigned tx object when it comes to imports. I'll investigate. For now, set yourself in expert user mode and try to manually pick the C++ signer at spend time, see if that fixes your issue.
985  Bitcoin / Armory / Re: 0.96.4 RC1 on: November 27, 2017, 03:31:13 AM
What's vanity about it? Did you import a private key?

Edit:

Did you update your signer? Are you using mismatched versions between signer and online?
986  Bitcoin / Armory / Re: Armory 0.96.3 released on: November 27, 2017, 03:21:39 AM
Yeah you want .2 or RC1
987  Bitcoin / Armory / Re: Armory 0.96.3 released on: November 27, 2017, 03:07:08 AM
You really want to use the RC for 0.96.4. As for 0.96.3 you can operate it but you have to pick the signer manually, as the default signer detection is botched.
988  Bitcoin / Armory / Re: Armory 0.96.3 released on: November 27, 2017, 01:29:44 AM
What version are you using? 0.96.3 has some signer issues.
989  Bitcoin / Armory / Re: Armory 0.96 is out on: November 27, 2017, 12:12:43 AM
Quote
Well, my tx didn't need bumping in the end.  But Armory (0.96.3) seems can't detect its own txs; I think I'm going to run out of outputs soon

I fixed all of the known RBF issues just an hour ago. The fixes are in the testing branch if you'd like to try them out, otherwise I'll put out a new RC once I have the BTG signer done.

Quote
Re-importing the wallet didn't help; I was hoping there was a way to invoke rescanning?

That won't trigger rescans anymore, as the DB keeps track of all addresses it sees now. You can flag the DB for a rescan from the help menu. Any rescan or rebuild action won't carry over the ZC state, so you'll lose the entries in the ledger.

Quote
And trying to do a Wallet Consistency check gave a backtrace and an empty

I'll look into that.
990  Bitcoin / Armory / Re: Armory 0.96.3 released on: November 26, 2017, 10:37:25 PM
It's not detecting your node.
991  Bitcoin / Armory / Re: Fee error message + "send!" action doesn't work on: November 25, 2017, 10:58:01 PM
Deleting the DB just makes double sure you actually did a rebuild & rescan.
992  Bitcoin / Armory / Re: Armory on the command line? on: November 25, 2017, 10:29:34 PM
python armoryd.py
993  Bitcoin / Armory / Re: Cannot view or print Fragmented backups on: November 25, 2017, 03:24:24 PM
Thanks - that helped, found the new version here: https://btcarmory.com/

The 0.96.3 version is not available for download via https://www.bitcoinarmory.com/download/ though

btcarmory.com is the community run site. bitcoinarmory.com is the old maintainers page.
994  Bitcoin / Armory / Re: Fee error message + "send!" action doesn't work on: November 25, 2017, 03:19:04 PM
Delete your Armory db folder and let it build from scratch.
995  Bitcoin / Armory / Re: Is there a good "recipie" for spending from a P2SH-P2PK address in bitcoin-qt? on: November 25, 2017, 03:17:58 PM
Quote
Is there a way to get Armory to export the private keys for spent transactions?

When you export private keys you get the whole list, whether they hold coins or not.

Quote
The second question is that if there are risks associated with doing that.  I guess it would mean that loss of the chain code would mean all future Bitcoins addresses for that wallet are at risk?

You would expose the entire private chain, just like a BIP32 wallet. The proper approach is this: if you've exposed a single private key, consider the wallet compromised and move all of its holdings to a fresh wallet.
996  Bitcoin / Armory / Re: Cannot view or print Fragmented backups on: November 25, 2017, 12:35:15 PM
Update
997  Bitcoin / Armory / Re: Fee error message + "send!" action doesn't work on: November 25, 2017, 11:42:23 AM
post armorylog.txt
998  Bitcoin / Armory / Re: Armory on the command line? on: November 25, 2017, 11:04:27 AM
There's a JSON-RPC interface for Armory that you can find here:

https://github.com/goatpig/armoryd

That's as close as it's gonna get to a terminal interface.
999  Bitcoin / Armory / Re: setSatoshiDir: Directory does not exist on: November 24, 2017, 10:38:10 PM
What top block is Armory showing?
1000  Bitcoin / Armory / Re: Is there a good "recipie" for spending from a P2SH-P2PK address in bitcoin-qt? on: November 24, 2017, 05:32:06 PM
I guess there will be several 100 or 1000 forks in the future, no way to support them all in armory without getting a dedicated dev team just dealing with forks/airdrops/splits.

Depends on the valuation, those idiots may just be financing development at this rate =D
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 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 ... 233 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!