Recent content by freynder

Personally I would prefer option 2, for the following reasons: Regarding 1): - A dedicated IP does not guarantee less centralization and computing power, most run on cheap (possibly oversold) VPS servers with their preferred provider (centralized). A dedicated IP is probably an indication but...

Hello, I'm trying to get this up and running. Current status is: issues when syncing from wallet.dat, no issues when syncing from rpc. Running but transactions may not show up completely due to problems locating TXouts. Need further debugging and darkcoin branding. Test version is currently...

Welcome Aswan!

Hi Propulsion, When you change the passphrase in the darkcoin client, and keepass integration is activated, it will try to automically update the entry in KeePass through the integration. The video shows this at the end using the console but it should work from the GUI as well. No information...

I was referring to the proof of service. The explicit dynamic IP support is something that will need to be discussed further as it might have implications on the quality of the masternode network as eduffield stated in bitcointalk. It will be considered though during the rewrite.

I think so, the dsee registration does not do much with the IP besides registering it for that particular vin at the moment. As flare mentioned, this will be reworked.

Hi. The workspace can be locked if you like, KeePassHttp will ask to unlock it when it needs to retrieve the passphrase. I definitely agree on how essential KeePass is :) I don't think it necessarily weakens security. It basically replaces the copy paste mechanism you currently use with a direct...

As of v0.11.0, Darkcoin Core client offers KeePass integration. This guide will show you how to configure the association between Darkcoin and KeePass and how to save a Darkcoin wallet passphrase entry in KeePass through the integration. When this is done, KeePass can be used to unlock the...

Of course that was a non negotiable condition :smile:

Thank you for the nice welcome. Looking forward to help contribute to this great coin!

Ran into this paper: Two-factor authentication for the bitcoin protocol Section 3.2 describes how this can be implemented in the existing protocol using multisig as already stated by fernando and vertoe.

Created pull request: https://github.com/darkcoin/darkcoin/pull/96

Small update: There is a first working version ready in dev. Available at https://github.com/freynder/darkcoin/tree/keepass It will need some considerable refactoring though as I'm not very happy with what the code looks like. It makes use of crypter.h and openssl base64 enc/decoding which...

Great to hear that, thanks! I've started development yesterday and expect a first working version today or tomorrow. Will keep you posted.

None taken, I appreciate everyone's input and concerns.