--
You should "focus" on getting a new email and registering under a different nick.
Like a pit bull, I will not let go of your hypocrisy, you low-life, degenerate troll.
Now he even give lessons lol.
Unbelievable really...
Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 3498. (Read 9723748 times)
November 15, 2014, 02:29:17 PM
You should "focus" on getting a new email and registering under a different nick.
Like a pit bull, I will not let go of your hypocrisy, you low-life, degenerate troll.
Now he even give lessons lol.
Unbelievable really...
November 15, 2014, 02:27:41 PM
Quote
2014-11-15 19:21:40 dssu - state: 3 entriesCount: 0 accepted: 0 error: Last darksend was too recent
DarkCoin version v0.10.16.6-g80c65cb-beta ()
DarkCoin version v0.10.16.6-g80c65cb-beta ()
what is a typical ETA until darksend mixing starts moving up from 0% ?
November 15, 2014, 02:26:19 PM
You should "focus" on getting a new email and registering under a different nick.
Like a pit bull, I will not let go of your hypocrisy, you low-life, degenerate troll.
November 15, 2014, 02:21:44 PM
Evan, you want the debug.log? (even if I don't see anything "special")
Is there a way to increase trace level?
Is there a way to increase trace level?
Naw, the debug I need would be on your peers.
I'm compiling a new version, we'll see if that works.
Alright, try this and let me know:
http://www.darkcoin.io/binaries/darkcoin-0.10.16.8-linux.tar.gz
November 15, 2014, 02:14:54 PM
probably/hopefully a fake upmove
driven by 500 drk.. just too less coins on the book, next move upward will happen quickly
Yep, the book is really thin to 700k.... DRK should not be down here.. Could be a very quick move up.
Worry about the tech first, price second. Price will follow the tech. More important things going on right now than the immediate price. Focus on the current tech issues getting resolved.
November 15, 2014, 02:06:34 PM
Maybe the masternode must be removed from the old V15 list for it to propagate correctly on the V16 list? All my MNs have been booted from the V16 list but they are still on the V15 list even though they've been running the new software for a day or so.
November 15, 2014, 02:04:19 PM
Evan,
Did you reed my proposal on how to handle the darksend fees? (darkcointalk -> security bulletin?)
Im aware that bringing out a version that just works is more important at the moment,
so my proposal is more about a long-run version.
// -> I m completely okay, if you just answer with something like "read, but its crap",
but i wanted to make sure that it didnt fell through completely.
THANKS FOR YOUR WORK !
Did you reed my proposal on how to handle the darksend fees? (darkcointalk -> security bulletin?)
Im aware that bringing out a version that just works is more important at the moment,
so my proposal is more about a long-run version.
// -> I m completely okay, if you just answer with something like "read, but its crap",
but i wanted to make sure that it didnt fell through completely.
THANKS FOR YOUR WORK !
November 15, 2014, 02:03:55 PM
ok folks. As anticipated, the 1-hour chart finally got its ar*s in sync with the 4-hour.
Dark Elevator has arrived. Hop aboard !
If you need any more convincing read this... https://bitcointalksearch.org/topic/m.9550090
Dark Elevator has arrived. Hop aboard !
If you need any more convincing read this... https://bitcointalksearch.org/topic/m.9550090
November 15, 2014, 01:49:33 PM
Another small observation that might help:
As far as I remember my client with the empty wallet always told me "masternode started". In ver 16 it says "masternode remotley started". But I didn't start it with a remote config.
As far as I remember my client with the empty wallet always told me "masternode started". In ver 16 it says "masternode remotley started". But I didn't start it with a remote config.
November 15, 2014, 01:46:21 PM
Evan, you want the debug.log? (even if I don't see anything "special")
Is there a way to increase trace level?
Is there a way to increase trace level?
Naw, the debug I need would be on your peers.
I'm compiling a new version, we'll see if that works.
November 15, 2014, 01:46:01 PM
Evan, you want the debug.log? (even if I don't see anything "special")
Is there a way to increase trace level?
Is there a way to increase trace level?
Naw, the debug I need would be on your peers.
I'm compiling a new version, we'll see if that works.
On drk.mn the whole hour it was up, my MN had 'active duration' 1s - but I don't know if that's an issue with the site scripting or with the MN pinging the network when launched then not talking anymore?
November 15, 2014, 01:42:38 PM
Evan, you want the debug.log? (even if I don't see anything "special")
Is there a way to increase trace level?
Is there a way to increase trace level?
Naw, the debug I need would be on your peers.
I'm compiling a new version, we'll see if that works.
November 15, 2014, 01:36:19 PM
Evan, you want the debug.log? (even if I didn't see anything "special")
Is there a way to increase trace level?
Is there a way to increase trace level?
November 15, 2014, 01:33:15 PM
What's the difference between:
https://drk.mn/
and
https://drk.mn/masternodes-v15.html
The second shows my MNs are online.. the remote ./darkcoind masternode list doesn't..
https://drk.mn/
and
https://drk.mn/masternodes-v15.html
The second shows my MNs are online.. the remote ./darkcoind masternode list doesn't..
November 15, 2014, 01:31:57 PM
probably/hopefully a fake upmove
driven by 500 drk.. just too less coins on the book, next move upward will happen quickly
Yep, the book is really thin to 700k.... DRK should not be down here.. Could be a very quick move up.
November 15, 2014, 01:31:45 PM
MN got unlisted even in 16.7 and removing peer.dat... After ~1 hour..
Same thing for me.
deleted peer.dat have all set up in 16.7 was up and running and in the list and gone now. And I can't restart it without digging out the 1000drk wallet again.
maybe significant detail: in debug the empty wallet still says master node started despide no more in the list. after closing and restarting the wallet it says not capable masternode.
edit: have to add I don't use a classical remote setup but the hot to cold wallet swap method.
November 15, 2014, 01:30:45 PM
Masternode Update
There's a few possible reasons that some of you are getting delisted.
1. You're not connected to enough peers on the new network (I've confirmed this to be the case on 2 of 3 of the nodes I've looked at)
2. The ping messages in the previous version weren't working correctly and nodes weren't delisted when they should have been. Your setup might not be correct, in this case it would have worked last time.
3. You used start-many, which had a bug in the ping timestamp (fixed in 10.16.17)
To figure out which one you are:
1.) Delete peers.dat (both remote and local)
2.) Start the masternode remotely, afterward you can type "masternode start" on the hot node and it should say "remotely started masternode". If it says "not capable", then you'll need to debug what the problem is.
You can also also try 10.16.7 (this version will ONLY connect to new peers):
Linux 64:
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-38/gitian-linux-darkcoin-bin/bin/64/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-38/gitian-linux-darkcoin-bin/bin/64/darkcoind
Windows:
http://bamboo.darkcoin.qa/browse/DRKW-DEV-36/artifact/JOB1/gitian-win-darkcoin-dist/darkcoin-0.10.16.7-win.zip
After these steps, but after a little over an hour to get the same ie . . .not displayed in "masternode list"(masternode list | grep IP) after start from my Local wallet . . ."successfully started masternode" and now is showing in list There's a few possible reasons that some of you are getting delisted.
1. You're not connected to enough peers on the new network (I've confirmed this to be the case on 2 of 3 of the nodes I've looked at)
2. The ping messages in the previous version weren't working correctly and nodes weren't delisted when they should have been. Your setup might not be correct, in this case it would have worked last time.
3. You used start-many, which had a bug in the ping timestamp (fixed in 10.16.17)
To figure out which one you are:
1.) Delete peers.dat (both remote and local)
2.) Start the masternode remotely, afterward you can type "masternode start" on the hot node and it should say "remotely started masternode". If it says "not capable", then you'll need to debug what the problem is.
You can also also try 10.16.7 (this version will ONLY connect to new peers):
Linux 64:
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-38/gitian-linux-darkcoin-bin/bin/64/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-38/gitian-linux-darkcoin-bin/bin/64/darkcoind
Windows:
http://bamboo.darkcoin.qa/browse/DRKW-DEV-36/artifact/JOB1/gitian-win-darkcoin-dist/darkcoin-0.10.16.7-win.zip
November 15, 2014, 01:26:51 PM
MN got unlisted even in 16.7 and removing peer.dat... After ~1 hour..
Strange. Look at the time on your hot node and see if it's correct, maybe the network is rejecting the pings because of that.
On remote :
lebubar@108:~$ date -u
Sat Nov 15 18:25:41 UTC 2014
and
date
Sat Nov 15 18:25:45 UTC 2014
On local 12:25 (UTC-06:00) Guadalajara, Ciudad de México, Monterrey
seem ok
November 15, 2014, 01:15:18 PM
I'm still on 16.6 and still listed on v.15.21 daemon as :1 since this morning, but not using v.16.6 (either nothing or :0)
Jump to: