Search results

Duffs? Really?

Obsolete is a strong term assuming this is as implemented in core v.0.9.3, but you do almost have to try to shoot yourself in the foot with that configuration.

Public shaming until at least page 10... But seriously, you're not the only one to misconstrue the intended functionality of the address book, This guy had it worse...Solution vectors involve [1] replacing the "These are your [X]Coin addresses for sending[...]" dialog and possibly [2] altering...

Exactly... The "New Address" button in the addresses tab does add a new payee address to your payee list, but naturally, it requires you to specify the address as generally, these will not be your addresses at least within the scope of that wallet.

It's not a bug, it's tool misuse. New personal addresses are generated within the "Receive" tab. The "Addresses" tab is a storage list for payee addresses. The expectation is that you enter a valid address to allow you to pay this address multiple times. Edited to quote more relevant post.

Use the binaries in OP if that 's your preferred method at 10.17.21 or build from source at 10.17.23. Effective differences aren't incredible in most case, protocol difference was effective 10.17.19, the following were cleanup.

.22 just changed MIN_PEER_PROTO_VERSION = 70043 so p2pool-drk should run without any of the indicated tweaks in this thread.

It's really down to feature use here. Naturally nodes are important, but optimizing rpc clients designed to this task using masternode start is a better path and seems to provide greater flexibility through ability to target more unique RPC calls.

github @ darkcoin/darkcoin