Jetzt, seit dem ich die Termine nicht mehr vergesse, weil endlich ich einen wiederkehrenden Kalendereintrag definiert habe, hatte ich das Glück einmal gesundheits-bedingt und die letzten 3 mal ernsthaft dienstlich verhindert gewesen zu sein.
Schau mehr mal 2017.
Yep, lange nicht mehr gesehen. 2017 dann! Der Stammtisch wird immer voller und lustiger, es lohnt sich :-) |
|
|
|
|
Weiter geht's, die nächste Episode spielt diesen Donnerstag, wie immer um 19:00 im Café Uptown.
Bis dahin!
Ente
|
|
|
|
DB is full cpp code. There is no install process to just install the DB, but you can only build that if you wish so, by running Sounds like exactly what I need! Great! For everyone trying this, you need to enter the cppForSwig folder to compile the server. I will come back and add the whole install procedure for the server and client side. It doesn't seem too complicated, but the info is a bit spread out. Cheers, Ente |
|
|
|
I try to install ArmoryDB on a headless machine, to connect with a 'lite' Armory from another machine to it. Is there a recommended way to install only ArmoryDB, without ArmoryQT? I ask because I don't use a GUI nor ArmoryQT on that machine, and would like to skip the *qt dependencies. Afaik all dependencies are git-core build-essential swig python-dev python-twisted python-psutil pyqt4-dev-tools libqtcore4 libqt4-dev python-qt4 where I guess the bold ones aren't necessary for ArmoryDB? Cheers, Ente |
|
|
|
That symlink was already at 777. Changing "4" to "2" solved it! Thank you, Goatpig! :-) I'll set up that client-server-mode on the weekend, aww yeah! Ente |
|
|
|
Today I tried to import a paperwallet privkey into 0.94.1. It worked (import, not sweep), but I couldn't spend the funds: File "/opt/BitcoinArmory/armoryengine/Transaction.py", line 1054, in __init__
raise KeyDataError('Must give pubkey map for singlesig USTXI!')
armoryengine.ArmoryUtils.KeyDataError: Must give pubkey map for singlesig USTXI! So I upgraded to 0.95.1. Which I can't get to start up. Even with an empty armory user folder, it complains about (ERROR) BDM.py:184 - DB error: /home/user/.bitcoin/blocks is not a valid path My .bitcoin folder is a softlink to a folder on another harddisk, as I ran out of space for the bitcoind blockchain. I set all data to my user and 777 again (before, bitcoind ran on its own user with more strict permissions). Still, I get the same error. Is this a known problem? If it takes too much effort to fix, I'll set up the client-server mode on separated machines right away instead. Also, goatpig, I will need to hug you just for this client-server mode alone! Most awesome softwarefeature of the year! :-) Ente |
|
|
|
|
I suppose 0.96 will also include compatibility with compressed keys?
I read a comment that uncompressed keys are deprecated with segwit, and will be turned off completely at some point.
Ente
|
|
|
|
|
Habe mir auch einen Gutschein bei KC377 gekauft, zuerst bezahlt, und schnell erhalten.
Gleich bei Amazon eingelöst und bestellt, alles problemlos.
Danke dir, Bewertung ist abgegeben.
Ente
|
|
|
|
|
Better get used to it, noone ever gets caught. Even when taking millions from an eschange, and even when everyone can closely watch the coins move. I too am puzzled about this phenomenon.
Heck, with MtGox, noone even knows if those vanished coins even existed to begin with.
Ente
|
|
|
|
|
Diesen Donnerstag ist es wieder so weit, der Bitcoin-Stammtisch trifft sich wie immer im Café Uptown um 19:00.
Ente
|
|
|
|
|
I'll start the off-topic-spam:
Bruno, you are a machine! This is some mighty impressive bookkeeping and organizing!
Sad that BTC100 is winding down, but it did it's mission very successful. The time is over, Bitcoin has it's publicity now, mission accomplished.
So, it started and ends with you, Bruno. Thank you for taking it in your hand again, your procedure is well done.
Adress sent via PM.
So, see you people in the next project!
Ente
|
|
|
|
Under ATI, this was in the tubes to synchronize several instances of Armory across machines.
I won't be doing this because
1) It acts as phone home code, and there won't be any of that under my watch.
2) This is over engineered if the only thing you want is to back up your wallets meta data. I plan to add a feature to extract meta data with the new wallets
3) If there is demand for this, I would consider adding a feature to the DB to distribute WO wallets and/or meta data to authenticated instances. This would keep all data under your control, but add remote sync'ing for deployment convenience.
4) I don't intent to monetize any feature in the main Armory client.
I like your straight motives and straight language! No buzzwords, no mumbo-jumbo, no compromises for the user. (I remember the outcry ages ago when someone found some phone-home code in the old ATI armory..) Ente |
|
|
|
und ich habs verpeilt :/ verdammte axt
Nächste Chance: diesen Donnerstag, 2016-10-20, wie immer im Café Uptown :-) Bringt Bitcoins mit, es gibt Essen, Barista-Zubereitungen und Kekse! Ente [1] Uptown Coffee Bar Riemannstraße 44, 04107 Leipzig http://www.uptowncoffee.de/ |
|
|
|
|
Aah, I see! Thanks for the clarification!
edit: So Armory doesn't like a pruned bitcoin-core? I need the whole blockchain each time Armory starts up?
edit2: Restoring 91 GB bitcoin-core stuff.. *sigh*
Ente
|
|
|
|
All releases are signed. All future tags will be signed.
Sounds great! Just to be clear, a "release" is like a major version, right? Is 0.94.0 a release then, and is it signed already? I'd like to step up to 0.94, for the much reduced database size.. Ente |
|
|
|
does goatpig have 0.94.1 git tagged?: Ubuntu:~/BitcoinArmory$ git tag -v v0.94.1
error: 811798a9282d216e0a450fe342d8a4671fee01d3: cannot verify a non-tag object of type commit.
error: could not verify the tag 'v0.94.1'
It isn't signed. that's not good, is it? So both v0.94.0 and v0.94.1 are not signed? That way I have to trust that noone manipulated data in the repo circumventing the regular, visibly logged commit infrastructure? Are/will any releases be signed? For me, this repo is so much of a target that the risk of unsigned releases is too high for me.. Ente |
|
|
|
|
I nominate Bruno for king of BTC100! :-)
Bruno, what should we do at this point?
I propose we either follow up on the original mission, or shut it down.
Ente
|
|
|
|
|
I agree on your observation and questions. And I'm puzzled too, why noone demands answers to this correlation. It should be trivial for Bitfinex to check which accounts caused the volume and drop in exchange rate. Might very well be the best "follow the money" clue here. Maybe they are on to it already in the background, who knows.
Also, I am puzzled why bitgo were let off the hook that easily. Even if it were bitfinex' servers that were compromised, bitgo didn't find it suspicious to have 120k BTC withdrawals within hours?
Let's see if we ever get answers here, and if it will be earlier than with the mtgox implosion..
Ente
|
|
|
|
|
Except, they will reimburse for 1$ per token only, and bitfinex employees are not allowed to trade BFX.
That's what they say at least, make of that what you want.
I have enough trust in them that I keep my BFX, and bought some more for a nice profit already.
Ente
|
|
|
|
|
Show Posts
