Bitcoin Forum
March 19, 2024, 11:05:31 AM *
News: Latest Bitcoin Core release: 26.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 ... 232 »
421  Bitcoin / Armory / Re: armory (0.96.5) is only offline on my PC on: October 17, 2019, 02:55:20 PM
Quote
2019-10-16 10:51:29 (INFO) -- ArmoryUtils.pyc:1285 - Invoked: D:\Armory\new\home\dir\Armory\ArmoryQt.exe

Armory wasn't invoked with any of your command line arguments. I don't know why you're putting spaces everywhere, that will definitely break paths.

Quote
--datadir = <D>: \ <D: \ Armory \ new \ home \ dir \ Armory> - satoshi-datadir = <D>: \ <D: \ blocks>

This stuff is just insanity. Give me the path for your Armory Data and Bitcoin Core data, I'll tell you how to setup.
422  Bitcoin / Armory / Re: Problems installing Armory on Windows 10 on: October 09, 2019, 09:24:57 AM
ASCII is basically the western alphabet encoding. If you are using "exotic" characters such as Arabic, Chinese, Hebrew and the like, they cannot be encoded with the ASCII standard, you'd have to use UTF to represent them.

The folders you referred to are for the binary installation. The "install" I am talking about is the where on your system the Armory wallet and settings are saved. This is a different folder from the one that holds the binaries.

On Windows, it defaults to:

Code:
C:\Users\*username*\AppData\Roaming\Armory

Where *username* is the name you have given to your user account during the Windows install. If this name uses non ASCII characters, Armory will fail to run.

You need to first confirm this is the issue, then set your Armory user folder to an ASCII only path. For that, you need to create a shortcut of ArmoryQt.exe and add "--datadir=*custompath*" in the target box, where *custompath* is whatever folder you choose.

You can search the web for "ASCII table" for the list of acceptable characters for the custom path.
423  Bitcoin / Armory / Re: Problems installing Armory on Windows 10 on: October 07, 2019, 09:47:52 AM
Do not install Armory in a folder that has non ASCII characters.
424  Bitcoin / Armory / Re: Not enough UTXO's will result in loss of privacy. on: September 13, 2019, 08:21:43 PM
Armory is warning that it has to unrelated UTXOs together to meet the value of your desired payment. This erodes your privacy because if you move forward with this transaction, all these UTXOs will now be related.

There is no risk of coin loss, just privacy loss. Financial privacy is significant however, don't damage if you don't need to.

What you can to go around the issue is manually select UTXOs you know are fine to mix/use for that particular payment.
425  Bitcoin / Armory / Re: PPA vs. DEB install. Which is better for Armory & Bitcoin Core? on: September 09, 2019, 05:48:46 AM
Quote
But once I was in solely in charge of keeping my own money safe, my attitude quickly changed

Then he went full Kubernets. Never go full Kubernets!
426  Bitcoin / Armory / Re: Armory 0.96.5 on: September 03, 2019, 04:41:54 AM
Quote
computer science solved this problem 40-50 years ago: the static binary (bitcoin itself is a static binary, all needed libraries by bitcoind/bitcoin-qt are packaged into the executable file)

To be fair, the only stuff Armory doesn't link to statically beside the C lib is Qt.
427  Bitcoin / Armory / Re: ARMORY,"UNRECOGNIZED",What should I do? on: September 02, 2019, 12:17:14 AM
Update to 0.96.5 and try again.
428  Bitcoin / Armory / Re: ARMORY,"UNRECOGNIZED",What should I do? on: September 01, 2019, 03:00:33 AM
What makes you think that the transaction format from OmniWallet is supported in Armory?

They try to support it. None of our devs are involved though.

Quote
What should I do with this kind of problem?

What version of Armory are you using?
429  Bitcoin / Armory / Re: Using coldcard With Armory Lockbox on: August 28, 2019, 12:06:55 PM
Armory doesn't support BIP44 atm, that's in for the next version. So you'd have to input the public keys manually, Armory won't be able to generate these for you from your seed. If you want so sign those coins out of multisig script with Armory, you will have to import the underlying private keys too.

After that, you have to pick your MS script type. I suggest you pick the P2WPSH.

At any rate, addresses in your case are not useful, you need the straight up public keys. You cannot create a multisig script from addresses, as you cannot yield public keys from addresses.
430  Bitcoin / Armory / Re: Armory Doesn't build Databases or scan transaction History. on: August 24, 2019, 10:41:12 PM
In /home/jacob/.armory/, create a file named armorydb.conf. In there add this one line and save:

Code:
satoshi-datadir=/media/jacob/.bitcoin/Bitcoin/blocks

Try again and let me know.
431  Bitcoin / Armory / Re: Armory Doesn't build Databases or scan transaction History. on: August 23, 2019, 08:36:31 PM
Quote
2019-08-23 18:34:41 (INFO) -- ArmoryUtils.py:689 - Executing popen: ['/usr/local/bin/bitcoind', '-datadir=/media/jacob/.bitcoin/blocks']

Doesn't look like you told Armory where to look for your custom Bitcoin data folder.

In Files > Settings, second second section from the top, set your custom folder and try again. Make sure there are no zombie instances of ArmoryDB first.
432  Bitcoin / Armory / Re: Armory 0.96.5 on: August 16, 2019, 01:40:31 PM
Changes are taking place in the dev branch. A lot has changed and there's still a lot I want to add in there. The work is split with helping another project. Most of the progess with that project is shared with Armory and the code ends up in the Armory repo eventually.

The main bottleneck atm is moving from SWIG to another C++ to Python framework to allow for a shift to Py3 & Qt5. Also need to go over GUI for the new wallets. Mostly, the GUI needs to represent BIP32 wallet branches.
433  Bitcoin / Armory / Re: Armory 0.96.5 on: August 08, 2019, 02:24:07 PM
Any possibility of Armory being released as an appimage?

I dont know what that is =/
434  Bitcoin / Armory / Re: Illegal instruction (core dumped) on: August 01, 2019, 12:29:22 PM
Definitely try the noasm builds.
435  Bitcoin / Armory / Re: Armory 0.96.5 on: July 22, 2019, 04:20:26 PM
It gets reported in the log files.
436  Bitcoin / Armory / Re: Tried everything I could find here, Armory still unhappy with Building Databases on: July 08, 2019, 02:26:00 PM
1) Delete the content of this folder:

Code:
C:\Users\aorob\AppData\Roaming\Armory\databases

2) Make sure no instance of ArmoryDB is running.

3) Start Armory.
437  Bitcoin / Armory / Re: Tried everything I could find here, Armory still unhappy with Building Databases on: July 02, 2019, 10:15:44 AM
Core is failing to start in the first place. Please run Bitcoin-Qt manually and report.
438  Bitcoin / Armory / Re: lost, unspendable UXTOs, FUD or no? relevant to Armory? on: June 26, 2019, 11:38:18 PM
BIP32 is in there. My main concern atm is migrating away from SWIG to cppyy (for py3 and eventually qt5 support). Then I need to get the new features in the GUI, and only then can I look at HW wallet integration. However I'm not doing that stuff alone, there are people offering to help and/or currently helping with the process. I have given up on ETAs a long time ago, I never hold them. I'm really hopeful to deliver a lot of stuff this year, the universe willing.
439  Bitcoin / Armory / Re: lost, unspendable UXTOs, FUD or no? relevant to Armory? on: June 26, 2019, 08:05:40 PM
There are no unspendable address types in the context of SegWit, quite the opposite actually: SegWit scripts are anyone-can-spend prior to fork activation. This is irrelevant on the Bitcoin chain, but on BCH (and whatever fork that does not have SW), mistakenly sending coins to a SegWit script will lose you the money (to a miner most likely).

The most realistic way to blackhole coins is to send them to a script hash that has no known preimage. You could also construct scripts that can't be spent from at all (always interpret to false), but in both cases this is not related to SegWit and is rather an issue of bad wallet implementation.

I guess there could be a semi easy way for a wallet dev to bork SegWit script generation in code, but he'd catch it right away on the testnet.

Another potential way to mess up is to swap script types around. A buggy wallet could grab the public key hash from a P2WPKH payment address and construct a P2PKH output script instead, which may result in the receiving wallet to never see the payment. The coins are still redeemable, but in this case the recipient will most likely fail to see it on chain, since he isn't looking for that script type in the first place.

None of these potential snafus are stuff you can achieve through a wallet GUI. Basically, the only way to mess up this bad is to craft your own tx manually.
440  Bitcoin / Armory / Re: Fresh install of Armory Fails to spawn DB! on: June 24, 2019, 06:05:46 AM
Try the noasm .deb
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 ... 232 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!