[ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency

[Divorcion]

Hi,

sorry for the maybe stupid question but:

i have a cold wallet which i made, is it in any way affected by the recently hard fork, should i do something or can the wallet stay cold as it actually is? I saw same coin-swaps where you had to transfer your coins to exchanges and so on, therefore the question, because i'm not sure what is the difference between a hard-fork and a coin-swap-fork.

thank you

It should be fine, no need to open it in a newer version of the wallet until you want to access your coins.  The wallet.dat file doesn't change.

Of course if you use your coins a lot, moving them around, etc... you'll want to update your wallet.dat file more often, but if it's just in cold storage, there is no need to worry about saving new account numbers being used, etc...

thank you very much for the info

[Populus]

My wallet was working fine, then suddenly it was not.
I get this message when I try to start darkcoin-qt.exe, normally, as administrator and in compatibility mode for Windows XP.

"This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information."

Thanks, the constructive feedback is appreciated. However I missed the part where you gave constructive feedback. Would you like to kindly try again?
I'm simply trying to access the wallet, not setup a node. So I don't see why you're being a superior elitist.
Thanks in advance to any help!

Are you using XP or have your wallet running in xp compatibility mode?  I'm a little confused by the question.  I don't think the windows binary was compiled in 32bit.  There might be a 32 bit version available, but I don't recall...  it's getting a little old to use.  However, honestly, Ubuntu is an easy to use 64bit system, if your computer can do 64 bit.... just an idea. 

I don't know how to compile on windows, so I can't really help there, sorry

I'm using Win 7, 64 bit system. It was working fine at first, however after the problem arose I tried running the darkcoin-qt.exe in compatibility for XP among other attempts on solutions.
There should be no need to compile anything, I downloaded the wallet/qt-client from here and I've tried both the 0.9.11.5 and 0.10.11.5 version.
Both yield the same error message :
"This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information."

Ubuntu is incredibly easy, yes, no doubt. However this 'should' work just fine on Windows. Thanks for helping out.

[TanteStefana2]

I'm using Win 7, 64 bit system. It was working fine at first, however after the problem arose I tried running the darkcoin-qt.exe in compatibility for XP among other attempts on solutions.
There should be no need to compile anything, I downloaded the wallet/qt-client from here and I've tried both the 0.9.11.5 and 0.10.11.5 version.
Both yield the same error message :
"This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information."

Ubuntu is incredibly easy, yes, no doubt. However this 'should' work just fine on Windows. Thanks for helping out.

Oh, ok.  Maybe there was an error in the compilation of the latest wallet and you're just the first to notice.  I'm running 10.11.04 on my machine.  I'll download and see if I have issues with the latest  BRB

I'm sorry, I'm not having any trouble with the latest.  Maybe, if you haven't already tried it, you can try downloading it again?  Or try the 10.11.05 version (with darksend) 

[thelonecrouton]

Banning on "bad masternode signatures" is temporary removed.
This will help other nodes and yours.

So, *if* my masternodeprivkeys are banned, anyone running 10.11.5 will ignore the ban and my MNs should get paid eventually anyway?

I have updated my MNs to 10.11.5 but not generated a new privkey for each, not got any payments yet.

[Ozziecoin]

Banning on "bad masternode signatures" is temporary removed.
This will help other nodes and yours.

So, *if* my masternodeprivkeys are banned, anyone running 10.11.5 will ignore the ban and my MNs should get paid eventually anyway?

I have updated my MNs to 10.11.5 but not generated a new privkey for each, not got any payments yet.

I generated new privkeys and almost immediately got paid across a few MNs. Then a couple got rebanned. I'm setting up new IPs for banned ones.

[CryptoPleb]

Banning on "bad masternode signatures" is temporary removed.
This will help other nodes and yours.

So, *if* my masternodeprivkeys are banned, anyone running 10.11.5 will ignore the ban and my MNs should get paid eventually anyway?

I have updated my MNs to 10.11.5 but not generated a new privkey for each, not got any payments yet.

I generated new privkeys and almost immediately got paid across a few MNs. Then a couple got rebanned. I'm setting up new IPs for banned ones.

So you could tell that a couple got rebanned because they turned from green to red on chaeplins list?

[innergy]

Banning on "bad masternode signatures" is temporary removed.
This will help other nodes and yours.

So, *if* my masternodeprivkeys are banned, anyone running 10.11.5 will ignore the ban and my MNs should get paid eventually anyway?

I have updated my MNs to 10.11.5 but not generated a new privkey for each, not got any payments yet.

Same here... green everywhere..

[Ozziecoin]

Banning on "bad masternode signatures" is temporary removed.
This will help other nodes and yours.

So, *if* my masternodeprivkeys are banned, anyone running 10.11.5 will ignore the ban and my MNs should get paid eventually anyway?

I have updated my MNs to 10.11.5 but not generated a new privkey for each, not got any payments yet.

I generated new privkeys and almost immediately got paid across a few MNs. Then a couple got rebanned. I'm setting up new IPs for banned ones.

So you could tell that a couple got rebanned because they turned from green to red on chaeplins list?

Turned to grey on http://drk.poolhash.org/masternode.html - I waited >12 hours on greyed out ones and realised they were probably never going to be paid.

[CryptoPleb]

Banning on "bad masternode signatures" is temporary removed.
This will help other nodes and yours.

So, *if* my masternodeprivkeys are banned, anyone running 10.11.5 will ignore the ban and my MNs should get paid eventually anyway?

I have updated my MNs to 10.11.5 but not generated a new privkey for each, not got any payments yet.

I generated new privkeys and almost immediately got paid across a few MNs. Then a couple got rebanned. I'm setting up new IPs for banned ones.

So you could tell that a couple got rebanned because they turned from green to red on chaeplins list?

Turned to grey on http://drk.poolhash.org/masternode.html - I waited >12 hours on greyed out ones and realised they were probably never going to be paid.

Sweet thanks

[chaeplin]

Banning on "bad masternode signatures" is temporary removed.
This will help other nodes and yours.

So, *if* my masternodeprivkeys are banned, anyone running 10.11.5 will ignore the ban and my MNs should get paid eventually anyway?

I have updated my MNs to 10.11.5 but not generated a new privkey for each, not got any payments yet.

Banning last 24 hours.
Banning is on ip address not on pubkey holding 1K or masternode pubkey.

If "bad masternode address signature thing" is occurred, bp is new ip + new genkey + new address for 1K.
But you can't assure wether your NM is banned by looking log of your NM.

[innergy]

Banning on "bad masternode signatures" is temporary removed.
This will help other nodes and yours.

So, *if* my masternodeprivkeys are banned, anyone running 10.11.5 will ignore the ban and my MNs should get paid eventually anyway?

I have updated my MNs to 10.11.5 but not generated a new privkey for each, not got any payments yet.

Banning last 24 hours.
Banning is on ip address not on pubkey holding 1K or masternode pubkey.

If "bad masternode address signature thing" is occurred, bp is new ip + new genkey + new address for 1K.

Can we see somehow the banned IP addresses?

[chaeplin]

Banning on "bad masternode signatures" is temporary removed.
This will help other nodes and yours.

So, *if* my masternodeprivkeys are banned, anyone running 10.11.5 will ignore the ban and my MNs should get paid eventually anyway?

I have updated my MNs to 10.11.5 but not generated a new privkey for each, not got any payments yet.

Banning last 24 hours.
Banning is on ip address not on pubkey holding 1K or masternode pubkey.

If "bad masternode address signature thing" is occurred, bp is new ip + new genkey + new address for 1K.

Can we see somehow the banned IP addresses?

I don't think so.

Banned by peered clients.

[TanteStefana2]

Banning on "bad masternode signatures" is temporary removed.
This will help other nodes and yours.

So, *if* my masternodeprivkeys are banned, anyone running 10.11.5 will ignore the ban and my MNs should get paid eventually anyway?

I have updated my MNs to 10.11.5 but not generated a new privkey for each, not got any payments yet.

Banning last 24 hours.
Banning is on ip address not on pubkey holding 1K or masternode pubkey.

If "bad masternode address signature thing" is occurred, bp is new ip + new genkey + new address for 1K.

Can we see somehow the banned IP addresses?

I don't think so.

Banned by peered clients.

So we could be banned, which lasts 24 hours, and have no way of knowing it?  Geepers!  I doubt this is an offence that happens often, but it should be viewable somewhere.  I scanned my debug logs for "ban" and didn't get anything, so hopefully I haven't been banned for anything, LOL

[Aswan]

ich habe einen Test mit 3 clients gleichzeitig und darksend gemacht:

funktoniert einwandfrei

was ist  funktoniert einwandfrei auf English?

"Works flawlessly"

[Macno]

Great to see the MN payments working.
What does it take now for Darkmarkets to actually use DRK? The Darksend 10 DRK limit has to be lifted, right?

[Spratan]

"Unable fo bind to 0.0.0.0.9999" when launching 

Same problem as here, remains unsanswered : https://darkcointalk.org/threads/unable-to-bind-9999.677/

I can't launch the wallet, and no other coin on google mentionning this error.  Any solution ?

[GhostPlayer]

Great to see the MN payments working.
What does it take now for Darkmarkets to actually use DRK? The Darksend 10 DRK limit has to be lifted, right?

 That, but also good amounts of PR to get the word out.

[chaeplin]

Banning on "bad masternode signatures" is temporary removed.
This will help other nodes and yours.

So, *if* my masternodeprivkeys are banned, anyone running 10.11.5 will ignore the ban and my MNs should get paid eventually anyway?

I have updated my MNs to 10.11.5 but not generated a new privkey for each, not got any payments yet.

Banning last 24 hours.
Banning is on ip address not on pubkey holding 1K or masternode pubkey.

If "bad masternode address signature thing" is occurred, bp is new ip + new genkey + new address for 1K.

Can we see somehow the banned IP addresses?

I don't think so.

Banned by peered clients.

So we could be banned, which lasts 24 hours, and have no way of knowing it?  Geepers!  I doubt this is an offence that happens often, but it should be viewable somewhere.  I scanned my debug logs for "ban" and didn't get anything, so hopefully I haven't been banned for anything, LOL

If anyhow NM is banned(ip or pubkey..), ping of NM will not be relayed.
So if a NM is green on the list at least 2 hours, I think the NM is ok.

http://drk.poolhash.org/masternode.html
https://elbzo.net/masternodes.html

[GhostPlayer]

"Unable fo bind to 0.0.0.0.9999" when launching 

Same problem as here, remains unsanswered : https://darkcointalk.org/threads/unable-to-bind-9999.677/

I can't launch the wallet, and no other coin on google mentionning this error.  Any solution ?

Refer back to that link. I just gave a shot at a fix

[chaeplin]

"Unable fo bind to 0.0.0.0.9999" when launching  

Same problem as here, remains unsanswered : https://darkcointalk.org/threads/unable-to-bind-9999.677/

I can't launch the wallet, and no other coin on google mentionning this error.  Any solution ?

I had that error once in linux with multiple interface and aliased ip.

If port 9999 is not used by other applications, please try this.

make darkcoin.conf with options

Code:

bind=change_this_to_internal_interface_ip_public_or_private
bind=127.0.0.1
rpcport=9998
port=9999