Search results

  1. F

    Which Masternode model should we implement?

    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...
  2. F

    We need a blockchain explorer with HD wallet support!

    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...
  3. F

    Welcome Mario Müller To The Team

    Welcome Aswan!
  4. F

    KeePass Integration

    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...
  5. F

    Static IPs definitely not a requirement for Masternodes

    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.
  6. F

    Static IPs definitely not a requirement for Masternodes

    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.
  7. F

    KeePass Integration

    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...
  8. F

    KeePass Integration

    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...
  9. F

    Welcome Francis Reynders to the team!

    Of course that was a non negotiable condition :smile:
  10. F

    Welcome Francis Reynders to the team!

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

    Feature - 2 Factor Authentication

    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.
  12. F

    Proposal: KeePass integration

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

    Proposal: KeePass integration

    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...
  14. F

    Proposal: KeePass integration

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

    Proposal: KeePass integration

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

    Proposal: KeePass integration

    Indeed, the KeePass vault can be protected by additional security mechanisms besides the master password (two factor authentication using key or certificate, OTP), effectively removing one attack vector (key logger only).
  17. F

    Proposal: KeePass integration

    Try to think of unlocking KeePass as an alternative to unlocking the wallet. The risk is basically the same. The attack example you provide is similar to a process that sits quietly, wait until the user unlocks the wallet and do anything it likes by RPC.
  18. F

    Proposal: KeePass integration

    Anyone would be free to use it, or not if he has a concern with it. The original client security with the passphrase would still be in place, the integration would just offer a way to securely transmit the passphrase from the password manager to the client. Regarding security, please have a...
  19. F

    Proposal: KeePass integration

    Thanks for the feedback. KeePass offers several advantages though that would be leveraged by the integration. Example: 2 factor authentication (using key file or certificate), OTP (using a plugin). The integration would allow darkcoin to use all security features that KeePass has to offer...
  20. F

    Proposal: KeePass integration

    Hello all, I would like to propose implementing KeePass integration in the core client. This would allow us to leverage all the security features that KeePass brings and make the client more secure. More info regarding KeePass: http://keepass.info/ I believe this could be a key feature and...
  21. F

    two masternode keys?

    Hi UdjinM6, I just checked again with a clean repository checkout and indeed it works as you are saying. I must have used a bugged instance while doing the refactoring which was very confusing. Everything you and UdjinM6 stated is indeed correct. I apologize for the confusion. Thank you
  22. F

    two masternode keys?

    vertoe, I understand what you are saying, and I'm more than willing to help refactor. That is actually what I'm currently trying to do for the masternode start-many part. The problem here is that both pubkeys are being sent with the dsee message so it's part of the protocol. I would really need...
  23. F

    two masternode keys?

    Since they are the same it will probably work. I'm a bit hesitant to just remove one as I don't know why it was put there in the first place.
  24. F

    two masternode keys?

    Are you sure about this? As stated, when you check the code you can see that both of them use the masternode private key. Also confirmed by checking pubkey and pubkey2 for the list of active masternodes.
  25. F

    two masternode keys?

    Hello, I'm currently reviewing darkcoin code and was wondering the following: masternode.h: contains: CPubKey pubkey; CPubKey pubkey2; Why are there 2 public keys? When checking CActiveMasternode::RegisterAsMasterNode I can see that two keypairs are being used to create the initial...
  26. F

    v0.10.17 - Onyx v3

    Oops, didn't realize this was already proposed by camosoul. Will update the ticket when ready as requested.
  27. F

    v0.10.17 - Onyx v3

    I can confirm this, had the same problem. Had nothing but issues so far using start-many so I decided to move the funds to seperate wallets again. I intend to review the code next week and submit a pull request for better start-many support. I'm thinking of adding the transaction and output...