One thing I am missing, though, is the "hide empty" button.
Will think about it I am not sure I like the tree-structure, but there is probably too much info to show otherwise.
Have to distinguish between the new script types now. |
|
|
|
Exactly, how did you proceed to delete the wallet? I tried deleting my empty wallet, which seams to be a simple procedure, but following the instructions would endup doing just nothing. Am i missing someting here ? Thanks for your help
First elaborate on your issue. |
|
|
|
|
If you don't shut down Core gracefully, the leveldb database may get corrupted. Your best bet is to manually control BitcoinQt to make sure it is shut down properly (that the shut down period is respected).
|
|
|
|
|
Get 0.95.1 synced:
1) Turn off auto bitcoind in File > Settings
2) Upgrade to Core 0.12+, but don't run 0.14. Otherwise, try the 0.96 testing builds as long as your online machine is not running Windows.
3) Get rid of any rpclogin and rpcpassword entries in your bitcoin.conf. Make sure it has "server=1"
4) Delete your database folder
That should get you going with 0.95.
0.93.3 has hardcoded fee limits, you can't do anything about it without modifying the Python scripts.
|
|
|
|
Viewing the addresses in a walled does not work
There are addresses. What is happening is that Qt is using weird column sizing by default, and the first (left most) column (the one for addresses) is shrunk. You have to enlarge it and your setting will carry over from there on, but the first time around, the first column on any tree structure is super tiny. |
|
|
|
First rule of Armory Club...  This But where's the "Armory Army" medallion?
I missed the event but looks like the theme was alt coins rather than service providers. goatpig and Ente are "Dogecoin followers"
ugh no... I'm "Ripple chief scientist"
...
But where's the "Armory Army" medallion?
Maybe this was a cue to run a quick shitcoin pump and dump scheme? ScaleCoin anyone? |
|
|
|
|
I sign the tags, and more often than not forget to set the clock on my offline signer for testing builds, which then reminds me to do it for the actual release.
The device I use to sign the tags/binaries has no internal battery, thus it can't keep track of time while it is powered off. This explains why the date on the signed tag is so close to the one for 0.95.1 (I don't typically let this device run for more than 5min at a time).
|
|
|
|
|
Nothing you can do about this in 0.95. Starting 0.96, you can either create the tx with RBF and bump the fee, or CPFP the change.
|
|
|
|
|
Bundling the Windows tsl fix with a bunch of others, new build ETA: Friday
|
|
|
|
Any estimated time to a final 0.96 release yet? Ty for all your work btw  Can't tell. If a lot of bugs are found during this testing phase, I can't quite release in such state. |
|
|
|
No exe's in the test branch?
I don't understand the question |
|
|
|
Testing builds are out, moved the code to the testing branch. Dev will be unstable again soon. Unsticking this thread. Tested the compressed key script on the mainnet. RBF too. So far so good. Would making it easier in one way, yet making it harder feature to discover and understand in others, achieve less abuse of the RBF feature in practice?
Usually, honest users don't try as hard to get things to work as malevolent ones. You are better off making the thing easy to use in the end. But UX is a pain to work on, so in due time. |
|
|
|
Third testing builds, updated changelog. Added RBF auto fee bump from the ledger (right click a RBF zc to see the option) Binaries: https://github.com/goatpig/BitcoinArmory/releases/tag/v0.95.99.3-testing--------------------------------- The changelog covers most of what's new with a couple caveats: - Added CPFP and RBF. CPFP is accessible from the coin control GUI, RBF has its own. CPFP and RBF are mutually exclusive. The RBF GUI is up for change, this is just a tentative approach for now. - Auto bitcoind woes should be fixed, give it a spin --------------------------------- I'll repeat the warning in the changelog for the good measure: This version introduces new address types. These address types are not compatible with previous versions of Armory. Any version of Armory (or any wallet for that matter) can pay to these addresses, but only Armory 0.96 can spend from them. Naturally, the new features are opt-in, even code wise. Legacy P2PKH addresses are untouched and can still be signed by anything 0.92+. The SegWit address type is locked to testnet only. --------------------------------- I've spent to and from the new nested compressed key script on the mainnet. Regardless, I recommend to start with small amounts at first, as a precaution. |
|
|
|
Unfortunately my offline machine is 32bit windows and I don't think I can compile.
0.92.3 had a x86 release for Windows and can sign for up to 0.95.1. I don't have these so you will have to look for them on your own. 0.93.2 offline bundles are available in x86 for Ubuntu and RPi armv7. You should still update your Bitcoin node regardless. One question I still have is why I couldn't broadcast from Electrum after importing my addresses to the online Electrum and the corresponding private keys to the offline Electrum? Why would my Armory setup matter at all in the case where I was using Electrum? Do the addresses not correspond to the private keys?
I do not know, I have no idea what Electrum is doing with those keys. You should ask them directly. |
|
|
|
|
I strongly advise you to update everything. You are using dated and obsolete software.
As for your transactions failing to broadcast, there has been a few changes to signature serialization in the past to reduce malleability. While any Armory pre 0.92 can sometimes create properly serialized signatures, it will more often than not create invalid ones.
Around the time these serialization rules were added, there was a few bots grabbing the bad transactions and reserializing the signatures to the proper format as a public service. I don't know that these bots are active anymore. At any, you will have a hard time broadcasting anything with that setup.
|
|
|
|
I'm using Armory wallet 0.91.2.
You can't be serious? Give me the versions of: 1) Your node 2) Your online Armory 3) Your offline signer (if applicable) I haven't rebuilt the block database yet as my CLI/Linux skills aren't the best.
Do you not have bitcoin-qt installed? Does this mean I'd have to download the entire blockchain again?
No, reindexing the node DB means to reverify all blocks and transactions. It won't try to redownload data it already has. It is a long process regardless. |
|
|
|
|
1) Are you using a wallet or a lockbox?
2) What version of Armory are you using?
3) Did you see your balance on Electrum?
4) What's the state of your Armory setup? Start BitcoinQt on its own, is it syncing?
|
|
|
|
|
Show Posts
