Did you install the dependencies? sudo apt-get install git-core build-essential pyqt4-dev-tools swig libqtcore4 libqt4-dev python-qt4 python-dev python-twisted python-psutil automake autotools-dev libtool
|
|
|
|
|
Start ArmoryDB.exe from the command line, what do you get? If it starts up fine, then run ArmoryQt.
|
|
|
|
|
try satoshi-datadir="o:\btc-core\blocks"
|
|
|
|
|
Why is your user name admin to begin with? The point of the user folder is for the account to have read/write path for processes to maintain the files they need.
From the looks of it, your blockchain data is either not accessible or you don't have any.
I can't really give you instructions until I know what user you are logging in as.
|
|
|
|
|
You can run as admin but that's not recommended. Armory needs write access to the files and folders in your datadir besides the .conf files.
|
|
|
|
2019-01-03 03:00:19 (ERROR) -- BDM.pyc:197 - DB error: C:\Users\Admin\AppData\Roaming/Bitcoin/blocks is not a valid path
Your user name is "Admin"? Chances are this is a permission issue, i.e. Armory cannot access this folder. |
|
|
|
|
Gonna need to see your logs then.
|
|
|
|
I have couple of questions, please clarify my doubt on it. 1. In Bitcoin core we used to call bitcoin-cli getwalletinfo through command line, and through json rpc curl request curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getwalletinfo", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/. Do we have same thing in Armory, if let me know some example of it. With armoryd, all calls assume the context that a current wallet is selected. To get data from other wallets, you need to select the relevant one. The first wallet armoryd loads is set as the default one. There's a somewhat large armoryd example you can find here: https://github.com/goatpig/BitcoinArmory/blob/master/webshop/server.pyUnfortunately I don't know how much of it still works, as it was written in 2014. 2. Can we have armory.conf file just like bitcoin.conf to have json rpc username and password in .armory/ folder
It would be armoryd.conf |
|
|
|
what is command to run ArmoryDB?
./ArmoryDB also by running this, i don't need to run python ArmoryQt.py
No. |
|
|
|
|
Yeah that's not gonna work because the client randomizes the DB port when it automates it. Just run ArmoryDB on its own then armoryd.
|
|
|
|
|
This log shows the DB running fine. What issues are you experiencing?
|
|
|
|
Another point release with some bug fixes and the ability to spend to bech32 addresses. Most likely the last update before 0.97, sometimes for Q2 2019. Changelog== Added ==
- You can now set the database path from the Settings menu.
- You can now spend to bech32 addresses.
- Added support for satoshi-port CLI argument in ArmoryDB.
- Break backwards compatibility for unsigned transactions carrying bech32 outputs.
Older versions cannot make sense of bech32 addresses, therefor they shouldn't
be able to sign the tx at all.
== Fixes ==
- Improved bitcoind path detection.
- Properly carry thread-count and ram-usage command line arguments from client to automated db process.
- Custom paths set in the GUI will now properly overrule custom paths from armoryqt.conf.
- Fixed spending from lockboxes.
- Fixed deleting lockboxes.
- Fixed Simulfund promisory note creation and signing.
- Fixed preview dialog for unconfirmed transactions.
- Fixed previewing unsigned transactions in offline mode.
- Properly detect output script type when filtering UTXOs.
- Use relevant config files with testnet/regtest modes.
- Properly display bech32 address strings in transaction system tray notification.
- Fix signing transactions with OP_RETURN outputs.
- Fix passing satoshi-port argument through ArmoryQt to auto-managed ArmoryDB.
- Fixed SecurePrint decryption on Windows.
- Recent updates to the MSVC compiler resulted in invalid decryption of AES-CBC packets. This issue only
affects the decryption of SecurePrint encrypted backups. Encryption still operates as expected, no
SecurePrint backups created with the incriminated builds are faulty. Wallets are not concerned, as they
use AES-CFB.
The solution was to turn off all optimizations in MSVC when buidling CryptoPP. This may impact DB boostrapping
performance.
This issue affects all Windows builds of 0.96.4.
== Misc ==
- Use blockstream.info instead of blockchain.info as the external block explorer link.
Binarieshttps://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.5Happy holidays! |
|
|
|
|
It's easiest to use a wallet that looks like your dad/uncle/grand mother would be able to use rather than expect they will figure their way out of an Armory install. You could consider phone wallets too, as long as you can generate paper backup out of them.
|
|
|
|
|
Is ArmoryDB running? Can you post dbLog.txt?
|
|
|
|
|
Is there a file named .cookie_ in your Armory datadir (where the wallets and .conf are)? If so, delete it.
|
|
|
|
1) Make sure you are using the right version of Armory. armoryd as found in the repo ( https://github.com/goatpig/armoryd) is meant to be paired with Armory as found in the master branch of the BitcoinArmory repo ( https://github.com/goatpig/BitcoinArmory) 2) Start your Bitcoin node. 3) Start ArmoryDB. This is the blockchain processing service that interfaces between the Bitcoin network (your node) and clients (ArmoryQt/armoryd). ArmoryQt automates the node and db for you, but armoryd does not, as it expects you are savvy enough to manage the software stack yourself. 4) At this point you should be able to run armoryd (python armoryd.py) |
|
|
|
|
1) Pick the wallet software you expect the gift recipients are most likely to use (assess user experience vs security).
2) Make sure the software can natively create paper backups. The kind that comes with the instructions to restore funds from the backup written all over it.
3) Create a wallet with that software, send coins to, back it up to paper and gift that.
Alternatively there are services out there that sell some variations of physical wallets (posters/cards/bank notes look-alike with a private key hidden on it). Some of these come unfunded so that you can put whatever amount you want in them.
These are more "gift like" but don't come with the same security as creating the wallet backup yourself, nor do they have dedicated instructions on how to claim the coins with the software of your choice.
|
|
|
|
|
armoryd is a separate repo, I'll look into that after this release.
|
|
|
|
|
There are some minor pieces of code in place to try and improve privacy, and I have more ideas for that, but the crux of the argument is the full node vs remote service model.
A typical wallet is just a GUI with no blockchain processing capacity. That task is serviced by a remote server operated (99% of the time) by the wallet provider. This creates a situation where a 3rd party (whoever is running that server) knows of all your transaction history past, present and future, for all operations you perform with that wallet software.
Armory does not provide such remote service. Instead, the software package comes with a local service for all things blockchain, and requires that you operate your own Bitcoin node, which is its interface with the Bitcoin network.
Therefor all your Bitcoin operations are contained within your own hardware and software stack, and Armory has no phone home/eavesdropping code, therefor there is no way, short of an adversary infiltrating your system, for anyone (devs included) to know what you're doing with your coins but you.
There's also the non negligible advantage that you get to choose which Bitcoin node code you want to run, which itself has some minor privacy implications.
|
|
|
|
|
Show Posts
