Yes, true, VI is running on any sysrtem remotely tasting like linux.
And I have to install nano first, from time to time.
Ah well, I think I got thrown at VI too early, it wouldn't be a problem now if I had a second look?

Oh, yes, good things in the Armory pipeline. New wallet format, litenodes with very little space, and much more for later on.
I do appreciate they do a rock solid job and take their time for that, but boy, have I grown impatient since playing in the Bitcoin world! :-)

Also, I forgot to mention, why on earth would someone put the watch-only wallet on a linux and the wallet holding the keys on a windows machine? No, really, if it's for more than you would put in your physical wallet, think about it a little more :-)

Ente

Hmm, getting a linux-bash-newbie to use VI, and successfully so - respect to both of you! :-)
I use "nano" in the shell and like it more. Yes, less powerfull,but I don't want to reprogram my stuff, just edit a few lines ;-)

Another option to the initial problem would be to drop the big Armory folder anywhere else, and create a link to the place where Armory expects the folder. As easy as "ln -s hdd-folder ssd-folder". Or with drag-and-drop and using "copy link" in the popup.

And yes, I feel your pain, only a system-ssd here too (everything else on a server). Hope there'll be some remedy in Armory before my space runs out..

Ente

Technically it's safe, as there are no privkeys on your phone.
The attack vectors are, as so often, targeting the user. Tricking him to believe something was paid which wasn't (with somehow having the attackers watch-adresses added), or simply checking out the users watch-adresses-balance, and forcing him to give up the coins.
This will eventually be a problem, I suppose. That attackers find out the balance of someone, and simply use force to overcome any smart technical obstacle.
Oh, by the way, sadly, I own no bitcoins. At all.

Ente

Okay, ich hab meine Meinung geändert. Kein Troll, valide Meinung (der ich nicht bin), und nur OT :-)

Ente

This comes up regularly, to add a public key/adress to your Armory wallet.
Currently it is not possible, because this would be an attack vector, where the user believes he received a payment, but in fact only sees a payment on an adress he doesn't control.
The next suggestion was to clearly highlight those adresses, but as of now, nothing like that is possible.

I, for one, would like that feature as well. I would create a watching-only wallet with interesting external adresses.
Oh, wait, the name "watch-only wallet" is already occupied for something similar, but completely different in Armory.. See the problems?

Ente

Absolut.
Macht einen eigenen Thread dafür auf.

@Rent_a_Ray: Bei so viel Unsinn und Zeitinvestition deinerseits frage ich mich ob du ein bezahlter Studententroll bist.

Ente

Happy birthday Zhou Tong!

Ente

Ente

Ah, that's some sort of explanation.
I have signatures deactivated since years *shudders*

Ente

Korrekt. Wer behauptet den 18.?

Nächster Leipziger Bitcoin-Stammtisch: 20.08. um 19:00, wie immer im Café Puschkin.

Bis dahin!

Ente

DAAAAAAMN RIGHT!

Ente
Ente
.
.
.
Ente

Ja, lustig wie viele Leute Kurse, Bitcoin und Entwicklungen betrachten, als würden sie Auto fahren indem sie in den Rückspiegel schauen..

Das einzig sichere in der Bitcoinwelt: Popcorn und Drama werden immer Hochkonjunktur haben ;-)

Ente

Alle öffentlich (und manche nicht öffentlich) bekannten Dinge sind im Wechselkurs mit eingerechnet. Mit der nächsten Halbierung wird sich im Kurs also kurzfristig gar nichts ändern.

Der Kurs hat sich noch nie nach den Minern oder Blockreward oder Difficulty gerichtet, es war und ist immer andersrum. Die Summe an BTC, die täglich gemint werden, sind einfach viel zu wenige im Vergleich zu den auf allen Börsen getradeten, i.e. mehr oder weniger spekulativen BTC.

Ich vermute, es bleibt alles wie bisher:
manche haben günstigen Zugang zu Mininghardware (selbst hergestellt, Großkunde etc) und billigstem Strom. Die Difficulty geht soweit hoch, dass diese Leute noch etwas Gewinn machen (abzüglich etwas höherem Overhead für Orga). Für viele, die die Hardware auf dem Endkundenmarkt kaufen und hiesige Strompreise zahlen, wird es eng (bleiben).

Tja, im nachhinein war der Plan mit "one cpu, one vote" doch gar nicht so schlecht..

Ente

Yes, I'd agree to your findings.
A die could be cheaply manufactured and be biased.

Also, depending on what you want to create, you won't need 256 bits (can't remember what made use of effectively 192bits only, I think?).

Either way, anything remotely like those are going to be fine. I wouldn't trust the pseudo-RNG of some tiny embedded device (raspi included), but other than that and faulty RNGs, this doesn't seem to be a plausible attack vector.
Not until every single brainwallet was emptied, more than half of all computers are infected with bitcoin-targeting malware, and the first hacks of "offline" wallets are reported :-)

Still, never wrong to err on the save side here.

Raalok

As I believe, it's not that much a "long jump" where you prepare for one year, and then, voilá, are the great new programmer for Armory, but more like a marathon. You start with reading the code and understanding the functions, then maybe do a few simple external scripts for that, then do little patches. With time, you get better at programming and knowing Armory, and as important as that, knowing the Armory team and getting the team to know you, your skills, interests, and reliability.

What's your startingpoint?
Like, are you a propgrammer already? How about Python especially?

Then there's a whole world waiting for programmers through Armory plugins.
I have a project in mind where I'm looking for a programmer for an Armory plugin, hint hint :-)

Ente

Yes.

It goes something like this:
- anything fishy in your bitcoin.conf?
- is the port forwarded so external nodes can reach your bitcoind?
- any packetfilter/firewall/antivirus in between?

Check that with https://getaddr.bitnodes.io/, there's a test in the lower area.

Ente

Great to see you active again, Rassah!

About donating to Sean's outpost:
I like the project, and personally donated several times already. Still, I don't feel too good about changing the rules here. In hindsight, we should have put an expiration date, or the like, in the original proposal.
We could, however, try to get as many donators to say "go ahead for Sean's outpost". Those accepting would have their donations forwarded accordingly. Maybe we can collect enough "go for it" that we can spend a big bunch of the funds. And use "no go" and "no reply" donations to btc100 for their regular cause, for past NGOs and future NGOs, depending on the sum.
I, for one, would agree to have the funds I initially donated to BTC100 used for Sean's outpost.

I would, however, prefer to have a long-term solution which continues the path BTC100 created. But if we don't find people willing to keep it up, well, not much to do about it except have BTC100 in hiatus, or send funds to non-original causes, or try to send the funds left back to their original donators.

AS this is more-or-less a project of this thread, we could make the process more streamlined as well. Like, post an applicant here, with a 3 day deadline. If noone has any objection until then, go ahead with the donation. If none of the BTC100-donators  has objections, or noone cares enough to spend some time do research, well, at least the Bitcoins are in the flow again :-)

Ente

This is the most blatant spam or postcount-levelling I saw in some time.
Stop that.
Post whatever you want in *one* post, and edit your last post if noone wrote in the meantime.
It will rain negative reputation if you continue such behavior.

Ente

No, no trezor for me, not even donated!
:-P

(The new wallet format has to launch first for trezor integration, which is in the works already.
Yes, let's donate some to the Armory team: https://bitcoinarmory.com/contact/)

Ente

About #2:
Yes, this is very confusing, there are two kinds of comments you can fill in. One for the transaction in the main list, and one for the address when you open a specific wallet. The way the GUI looks those would be the same, so the average user would expect that entering stuff in one of the fields copies it to the other list as well.
Ah, got used to it by now.

Ente