Yep, Gregory musste früher gehen, das Barpersonal musste uns um kurz nach 10 rauskehren.
Manche sind noch weitergezogen, die meisten dann nach Hause.

Bis zum nächsten Mal!

Ente

..this escalated quickly.
See you folks at the 10,000 party then?

Cheers, gentlepeople!

Ente

Diesmal waren zwölf neue Gesichter dabei, das Uptown ist fest in unserer Hand! :-)
..und keiner kam über Bitcointalk zu uns. Ist die Zeit der klassischen Foren vorbei?

Bis zum nächsten Mal,

Ente

Me neither :-)
Maybe merging all four categories and three subcategories into one large list, with sortable fields? It was more like that when there were only "regular" and "imported" addresses. Of course it wouldn't make sense to have 12 more rows though.

Nice! That is, for me, the much more helping change of the two. I'm happy :-)

Cheers,

Ente

Two small UI notes:

- when clicking a wallet, I get four categories (used, unused, change, imported), and inside of those again three categories (p2pkh etc). Only then I actually get to see the individual addresses. I liked it more as it was earlier, with one large list as soon as I open the wallet. Back then, "imported" was a field in the long list, for example. It's not too bad yet, as I only have coins in the "used - p2pkh" category.

- in coin control, I don't see the comment I wrote to an address. This would make coin control close to useless for me. My workaround is to click through the wallet the regular way, mentally choose the inputs I would want to use, and choose the corresponding bitcoin-amount-address in coin control.

Both aren't that tragic, but maybe it's easy to change, as it only changed recently afaik.

Cheers,

Ente

Of how many coins are we talking here? Like, do 7 out of 100,000 coins trace back from 'loaded' to this one, or is it a significant amount?

Ente

I did pull the sources from git and compiled myself, from the v0.96.0.1-testing tag. The regular way with
I am unsure what you mean with "build yourself", something different than what I did?

Ente

It still does the same instant segfault crashing when trying to load the GUI (apparently), like in v0.96.
I don't know about "invalig instruction", I never saw any logentries or the like considering the segfault.
To me, it looks like the same (crashing) behavior as before.

I didn't upgrade the remote ArmoryDB though, only the local ArmoryQT.

Ente

All the same segfault with v0.96.0.1-testing.

Ente

I'll try to give more details:

- I empty the entire .armory folder
- I copy that old 01.wallet
- I start Armory
- a "mirroring" popup shows for some seconds , the following files are created:


- the licence agreement shows, I accept it
- a short flash of GUI is seen, file "multipliers" is created,  new entries into armorylog (last one: "Dashboard switched to "Scanning" mode")
- segfault with no entries into any logfiles or on the terminal that I can see

My Armory is pulled from Git, checkout v0.96, regular installation procedure with no edits to any files.
Started with regular And as I hinted, if this is a local problem here on my side, I don't even need this fixed.

I hope anything is of help here?

Ente

Diesen Donnerstag, 2017-05-18, treffen wir uns wie immer im Café Uptown [1].

Bis dahin,

Ente

[1] Uptown Coffee Bar
Riemannstraße 44, 04107 Leipzig
http://www.uptowncoffee.de/

..seems like ATI is gone for good now. Maybe they'll give us the domain? Maybe a small fundraiser would help. Or they shall shut it down, link to the new one or similar? I guess they would have a small, vague interest to help the current development, if they still hope to gain anything from their involvement back then?

Ente

In fact I am not entirely sure what exactly I imported.
It certainly was a vanity-address, generated with vanitygen.
I imported the private key. I couldn't spend funds on that address with Armory. I believe I sent the funds to the vanity-address I created, but Armory showed a different address when importing the privkey. But then I did see the funds in a pre-0.96 Armory, just couldn't spend them. I am not too sure.

I remember that I could import privkeys created by bitcoinj, but couldn't see the funds there, and that bitcoinj used compressed keys back then already.

Anyway, I'll just wait for the final version of the new wallet format and check again then.
If you want I'll send you the crashing wallet to have a look by yourself.
It's all not too important for me. But maybe I found some weird cornercase that helps for finalizing the wallet format?

Cheers,

Ente

I have two old wallet files, both have an imported privatekey.
The first wallet file has a "regular" address imported, and works fine (that specific imported address is empty though).
The second wallet file has that compressed type privkey (I think) imported. Armory segfaults immediately on startup with that wallet in its folder.

Ente

I didn't "import" with that feature, but copied some old wallets into my armory folder.
The compressed address I imported years ago into that wallet was created with vanitygen, afaik. I imported the private key back then into said wallet, not just a pubkey or watch-only address or the like.
I can't tell you much more any more, sorry, as it's been so long ago.

In older Armory versions, I couldn't import compressed keys from other wallets, for example from bitcoinj. What changed with regards to compressed addresses/keys in the new (c?) wallet format? I think I am mixing up different types of compression now..

Ente

Hi everyone,

as my v0.96 with remote ArmoryDB finally works, I imported old wallet files.
When using a wallet where I imported a compressed-key address, I get a segfault in ArmoryQT.
Earier versions worked, showed the address and balance, just couldn't spend the funds.

I have no entries in the logs whatsoever (neither in armoryDB nor armorylog.txt), just bam, segfault and gone.

Anything else I can provide? Want the wallet file to test?

Cheers,

Ente

Ah, good, that explains it!


It seems to work just fine. I used the example config with just the interface, address and ports edited.
ArmoryQT took a while to rescan the blockchain for the new wallet, after that loads up lightning fast.
My only issue is that I'd prefer to only have apache installed :-)
I guess I'll just leave nginx installed for this anyway, and book it as "security by separation".

I am very happy to have bitcoin-core, blockchain, armorydb and database on a server and a lightweight, always-syncronized notebook.
Thank you again, goatpig!

Ente

I found my problem with RPC. I did most of my testing on the client (ArmoryQT) side, and forgot to actually keep the server side (ArmoryDB) up-to-date as well. After updating to v0.96, it RPC-connects to bitcoin-core as well. D'oh!

I couldn't find a "make server" option any more. So I had to install all dependencies (including QT stuff) and compile all Armory components, including ArmoryQT. Is there a better way to do this, when only ArmoryDB is needed?

Now I am troubleshooting why both my nginx- as well as my apache fcgi middleman doesn't seem to work.

Does anyone use ArmoryDB behind an apache?

I probably am missing important fcgi parameters as stated in the nginx example config https://github.com/goatpig/BitcoinArmory/blob/master/nginx_example.conf
especially
At least I am one step further now!

edit: it works with nginx! yeah! :-)
I'll try to get it to work with apache as well. Else I'll have to move to nginx..

Ente

Thanks, goatpig.
I added "addnode=127.0.0.1" as the only obvious relevant difference I can see here, no luck.

Is there a minimum bitcoin core version armory needs? I still run could that be it?

Ente

No matter what, I can't get Armory to connect to Bitcin Core via RPC.

I threw everything out of my bitcoin.conf and only have
in it now. I had it with manual rpcuser/rpcpassword credentials before, and without any rpc-options as well.
Everything looks fine to me, the auth cookie is there, both Core and Armory run under the same user, no errors anywhere, and Armory can connect (read blockfiles) to Core just fine.

Still, no luck with RPC.
Could anyone post their bitcoin.conf please?
Does anyone use Bitcoin Core without wallet functionality (not compiled in) and has Armory working with it?

Thank you,

Ente