OK. Does Armory have any bounty system at all so that other contributors could help get features implemented and you can verify/merge?
You can start one on your own if there is a feature you're really after. I'm wouldn't take charge on that stuff atm, too busy. |
|
|
|
|
The ZC parser only processes tx that it gets from your node. The tx your broadcast through Armory are pushed as is to your node. The DB will then requests the tx by hash from your node. This sets in motion the inv packet and subsequent tx fetching that happens for all ZC your node sees. Only after that process is the tx parsed and added to the DB's mempool (if it's relevant to your wallets).
In other words, there's a unified pipeline that's only ever triggered by your node pushing a tx to the DB (which for all intents and purposes, mimics itself as a node to your actual Bitcoin node).
This gives you 2 ways of getting a ZC to appear in your GUI:
- Carry over the zeroconf db to your new db folder and cycle ArmoryDB.
- Successfully push your tx again to your node. If that tx is already in your node's mempool, you'll have to clear, or it won't let your broadcast it again.
|
|
|
|
|
I don't accept donations.
|
|
|
|
goatpig: If I donate could I incentivize you to put it in 0.96.4?
Not really. BTG is too intrusive so it will be a binary on its own. At the same time I'm due work for other stuff, so I can't do BTG first thing. Sometimes next week maybe. |
|
|
|
Hopefully soon Armory will support BIP39 seeds
You should wait for that imo. |
|
|
|
Just a quick note to say i've had success with 0.96.4 RC2 on multiple platforms.
Compiled from source with armory_0.96.3.991_src.tar.gz on Ubuntu 16.04.3 LTS. Installed onto a clean machine with a full and updated Core node behind it.
Installed from pre-package armory_0.96.3.991-gcc4.7_amd64.deb on Ubuntu 14.04 LTS. An install onto a persistent USB over the top of the existing 0.95.1. Wallet conversion successful - running Offline, no Core database. Created some new Segwit addresses.
Historically I had been unable to move past 0.95.1 on MacOS (for TX Broadcast) and kept my offline signers at 0.95.1 to match. I used a standalone copy of Bitcoin-ABC / 0.96.1 to securely claim BCH back in August.
I wanted to create some Segwit addresses to transfer the main BTC holdings. I made various attempts at getting the latest versions working on MacOS (used for watch-wallets and to broadcast offline signed transactions). None of the pre-compiled OSX versions would work with the two Mac High Sierra versions I had locally - 10.12.6 and 10.13.2.
I tried rolling my own version on Mac without initial success.
Eventually it came down to uninstalling Xcode 8 completely, removing the brew installed python and then installing Xcode 7.3.1 from the Apple Developer Site, Python 2.7.14 from python.org. Downloaded armory_0.96.3.991_src and compiled the osxbuild, running smoothly and synced to a full Core node.
Happy to offer logs or advice to anyone else needing a hand with setup/compiling.
Probably about time I offer my thanks to goatpig and droark for continued work on the project (I've been using it since 2014!).
Maybe consider contributing to this PR, if anything, testing the new OSX build setup (once it congeals): https://github.com/goatpig/BitcoinArmory/pull/403 |
|
|
|
|
Is your Bitcoin Core synced properly?
|
|
|
|
How Armory is maintaining mempool? - what I understand it's loading mempool from network, not from bitcoin core mempool.
It holds its own mempool in the zeroconf db file |
|
|
|
That is a strange arrangement, but I guess it is what it is. Yeah, at the end of the day goatpig still needs to approve the PRs for the gh-pages branch too and of course that is at his discretion. Thanks for the info and the FAQ  I don't really intent to moderate the gh-pages beyond the regular sanity checks. It's really intended as a community maintained page, expect me to be much laxer with PRs to that branch than any actual code branch. |
|
|
|
Meant to report back on this.
I think Armory is hanging when starting the db process with with popen.
Also verified that there is no need to delete the above two dlls.
To get RC2 running under windows 10, only need to run armorydb separately from the command prompt with the switches in the install-dir armoryqt.exe.log, and then run armoryqt RC2.
Thanks for figuring it out, I'll look into it. sure enough, spoke too soon. CoinControl freezing problem still prominent. seems to always occur after first use. ccDLGeometry keeps coming back too after deletion.
What are the values in that field when you have to delete them? |
|
|
|
I'm pretty sure Bcash can handle RBF.
RBF is non standard on BCash, i.e. the replacement tx can be mined but won't be relayed by the network. |
|
|
|
|
Did it create an ArmoryQt.exe.log? If not, run it with admin privilege, you should get the file.
|
|
|
|
Armory 0.96.3.991(RC2) hangs on splashscreen under Windows 10.
Reverting to 0.96.3.99 (RC1) - runs fine.
Delete crypt32.dll and psapi.dll from the install folder and try to run it again. |
|
|
|
|
Fixed the Windows builds, should work now.
|
|
|
|
|
I can't sleep so ima setup a Win7 VM and see for myself.
|
|
|
|
|
I have no issues running this on my machine. I'll to investigate on another setup. I'm for the new year's weekend so that may have to wait till 2018 =O
|
|
|
|
Binaries:https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.3.991Notes:This is mostly fixes, notably: - All things RBF - Unsigned tx creation with a mix of P2SH and P2PKH outputs - Some lockbox signing issues Also, the auto fee GUI has been updated to use the reworked estimatesmartfee method from Core 0.15. People using older nodes won't see that change. Test away =D
|
|
|
|
|
Nothing is ever getting phased out.
|
|
|
|
|
Show Posts
