Topic: Armory 0.96.1 is out! (Read 6767 times)

Those are format specifiers. There will be strings that go in the place of those percentages that won't be translated. These strings are usually IDs and such, e.g. "Wallet: %1" may become "Wallet: xFjsjKSn"

Probably not the best place to post this but I didn't want to post a thread because other people have more important problems. I'm with the translations once again, I want to know what the percentages refers to? like 'Wallet: %1' or something similar, they shouldn't be deleted in any case?

Segwit defines two new output script types, Pay-to-witness-pubkey-hash (P2WPKH) and Pay-to-Witness-Script-Hash (P2WSH). When used as a normal output, those outputs are known as native segwit outputs. However those output scripts could be used as the redeemScript of a P2SH output. When that happens, they are known as P2SH nested segwit outputs.

What are nested addresses? What is the difference? Sorry, but I couldn't find anything about this on a quick search. Every day you learn something new about bitcoin

Those addresses are P2SH nested addresses. Armory will make those in the next version which will have those enabled.

I thought that I will send a SegWit transaction to an address that starts with 3.

You can't. Such addresses don't exist yet.

No, that is disabled because segwit is hardcoded to be disabled on mainnet for now. We will be releasing another version with segwit enabled soon.

Yes. That uses compressed keys and that is pretty much the only reason you would want to use it.

How do I generate P2WPKH address? I assume that the lack of an address makes the option P2SH-P2WPKH to be disabled when trying to send to a self address.

What is P2SH-P2K? Pay to public key?

Yes, you need to have Bitcoin Core installed and fully synced to properly use Armory.

Without Core, Armory has no block or transaction data to work with and no way to broadcast transactions to the network.

I downloaded this and I regret it now    Didn't realize that it had to run a full BTC node in order to be online.  So does the wallet actually have a BTC core running in the background.  I DID NOT download separately, but the way the dashboard represents itself makes it seem like it is syncing up.  It says offline but there is a notice saying "preparing database".  In the settings the directory for BTC is blank but again the program is vague in saying that Armory is 'managing' it if blank.  There is no indication that Armory cannot find the database.

Can someone tell me whether or not i have to separately download BTC?  thx


poorly designed UX imho

this happened for the second time now.

both times i was trying to send two total offline tx's, one after the other.  first works fine but second gets the RPC error.

i assume that once this failure occurs and the second tx was labelled as "Sent", it's no longer possible to broadcast that tx?  i tried unsuccessfully to broadcast it with the Broadcast Raw Transaction tool.

what's the easiest way to re-enable the RPC interface?

It would appear there's not enough funds left on your output to support a fee bump. You'll have to do this manually.

Hey goatpig, thanks for all your efforts. 0.96.1 has fixed many of the problems I had to get Armory running.

Now, there's two potential bugs I've found using the new version. The forst time I ran 0.96.1, all the addresses I've been using on an old wallet appeared on the "Unused Addresses", even though many of them had been used already. After sending a few txs, this seemed to be corrected.

The second point for which I'll provide a pastebin link, is I can't use the Bump Fee function.

Here's the armorylog pastebin link: https://pastebin.com/hxCKzedr

Again, thank you for all your work.

Enable your node RPC and restart the whole stack.

what do i need to do to remedy this.  never seen it before:

https://i.imgur.com/bD3SRiT.png

i'd just got done sending a different tx w/o any issues.  using 0.96.1 expert mode in Debian VM. 

edit:

the tx was marked as Sent.  i tried to copy raw tx and broadcast via the Broadcast Raw Tx tool w/o success.  blocks are up to date and a Armory/bitcoind restart didn't fix it.  so i redid the entire tx again, rebooted the entire VM and finally was able to broadcast the new tx.  i hope the old one doesn't show up later :0

Thanks and good to see that Armory is still being updated.

Is there an offline install bundle available for 0.96.1 on Ubuntu and if so where can it be found?

Thanks

Hello,

i have a problem to login into my wallet. I have printed all Login Information, Wallet Name, ID Root Key and Chain Code, but I can’t find the paper with the Login Information.

Please help me to login in my Account.

Jeff

  I too have been having this issue with 0.96.1 and 0.96.1.2 RC2. I have some further information regarding the problem, and my armory log, as well. First, I start with a new install of 0.96.1.2 RC2 with an empty ~/.armory directory. I import my online watching only wallet from a digital backup. Armory builds it's database, scans it, scans my wallet, etc. After all this, Armory starts up fine and everything works. Before I do anything, I shut Armory down and back up the entire ~/.armory directory. I start Armory back up, the coin control button/gui works and I use it to create an unsigned transaction. After I have finished creating the unsigned transaction is when the problem starts. Now, if I open the main "Send Bitcoins" menu, and then click the button for "Coin Control", armory becomes unresponsive. I can still move the "Send Bitcoins" window, and the main armory window, but nothing inside the windows will respond to anything, and they will not close/quit, so I have to kill armory-qt and ArmoryDB from the system monitor. After I kill them, if I start up Armory again, the main window and "Send Bitcoins" menu will work but it again freezes when clicking "Coin Control". At this point, however, I can broadcast my transaction after signing it offline, and it will broadcast and confirm. In order to use my wallet again, I shutdown Armory, delete the ~/.armory folder, and restore it from my backup I made before creating the transaction. Now if I start armory up again, it will pick up my new transaction after scanning for a few seconds, and display it with the rest of my transactions. I can now successfully open the coin control menu again. I have included a link to my log file which I uploaded to my github account. My log file contained some information about my transaction, so these parts, and any other parts I thought might be sensitive information, I replaced with X's.

Log file as shown in github interface:  https://github.com/UncleHunto/logs/blob/master/armory.frozen.gui.log.txt

Log file as raw text:  https://raw.githubusercontent.com/UncleHunto/logs/master/armory.frozen.gui.log.txt

You don't. You're on Linux, right? You just do the standard autogen.sh/configure/make procedure, which is for the C/C++ code.

How do I build from python?