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

[spatula]

I just entered "Bitcoin" in Google, and saw this
...
With a link that hops you over to:
http://forklog.net/dash-is-determined-to-supersede-bitcoin-as-a-real-paypal-alternative/

I just tried Dash and its now on the the first page of Google (last link on the page).

tante:
this is nothing special. Google already knows that you love dash. Logout from your browser and try this again.

Can confirm. Logged out (and in incognito mode) Dash.org now shows up on the first page of google results for "dash". Last week it was in the middle of page 2!!

Making good progress!

[f2000]

I just entered "Bitcoin" in Google, and saw this
...
With a link that hops you over to:
http://forklog.net/dash-is-determined-to-supersede-bitcoin-as-a-real-paypal-alternative/

I just tried Dash and its now on the the first page of Google (last link on the page).

tante:
this is nothing special. Google already knows that you love dash. Logout from your browser and try this again.

Can confirm. Logged out (and in incognito mode) Dash.org now shows up on the first page of google results for "dash". Last week it was in the middle of page 2!!

Making good progress!

@Raptor, derp...well spotted.

[penambang]

Based on GTMetrix, dash.org performace is little bit slow with many unoptimized resources, I think webmaster could improve it based on gtmetrix recommendation.
compared to bitcoin.org, which loaded in just 0.6s, dash.org loaded in 6s. also total page size of dash.org is really big compared to bitcoin.org, 2.03MB vs 175KB.



Detailed result is here: https://gtmetrix.com/compare/RUpaNoUh/4VrVVDoV

[pille]

Where is the new website? Any progress updates please?

[qwizzie]

Where is the new website? Any progress updates please?

https://dashtalk.org/threads/hows-the-new-forum-coming-along.7902/

tungfa's reply :

everything in progress , still needs time and work , hopefully a couple of weeks +

[toknormal]

The masternode graph's gone a bit wonky.

[crowning]

The masternode graph's gone a bit wonky.

Unwonked!

[Honest Tim]

Yeah, been running for almost a year now. 768Meg, never had any probs before. Nothing has changed.

 HDD ? How long since you've dumped the debug.log? Also, keep in mind Dashninja may have it's quirks from time to time. If Elb is working the backend, some funky info may result from it.

 Did you try list | grep xx.xx.xx.xx ?

hmmm. Is there a way to search by IP address now?? It appears you need to search by Vin (Hash-Index), now that we use "dash-cli" Unless theres a switch somewhere??

This gives me hope..... but also a headache!

root@vultr:~/.dash# ./dash-cli masternodelist help
error: {"code":-1,"message":"masternodelist ( \"mode\" \"filter\" )\nGet a list of masternodes in different modes\n\nArguments:\n1. \"mode\"      (string, optional/required to use filter, defaults = status) The mode to run list in\n2. \"filter\"    (string, optional) Filter results. Partial match by IP by default in all modes,\n                                    additional matches in some modes are also available\n\nAvailable modes:\n  activeseconds  - Print number of seconds masternode recognized by the network as enabled\n                   (since latest issued \"masternode start/start-many/start-alias\")\n  addr           - Print ip address associated with a masternode (can be additionally filtered, partial match)\n  full           - Print info in format 'status protocol pubkey IP lastseen activeseconds lastpaid'\n                   (can be additionally filtered, partial match)\n  lastseen       - Print timestamp of when a masternode was last seen on the network\n  lastpaid       - The last time a node was paid on the network\n  protocol       - Print protocol of a masternode (can be additionally filtered, exact match))\n  pubkey         - Print public key associated with a masternode (can be additionally filtered,\n                   partial match)\n  rank           - Print rank of a masternode based on current block\n  status         - Print masternode status: ENABLED / EXPIRED / VIN_SPENT / REMOVE / POS_ERROR\n                   (can be additionally filtered, partial match)\n"}

[dihydrogenmonoxide]

Yeah, been running for almost a year now. 768Meg, never had any probs before. Nothing has changed.

 HDD ? How long since you've dumped the debug.log? Also, keep in mind Dashninja may have it's quirks from time to time. If Elb is working the backend, some funky info may result from it.

 Did you try list | grep xx.xx.xx.xx ?

hmmm. Is there a way to search by IP address now?? It appears you need to search by Vin (Hash-Index), now that we use "dash-cli" Unless theres a switch somewhere??

This gives me hope..... but also a headache!

root@vultr:~/.dash# ./dash-cli masternodelist help
error: {"code":-1,"message":"masternodelist ( \"mode\" \"filter\" )\nGet a list of masternodes in different modes\n\nArguments:\n1. \"mode\"      (string, optional/required to use filter, defaults = status) The mode to run list in\n2. \"filter\"    (string, optional) Filter results. Partial match by IP by default in all modes,\n                                    additional matches in some modes are also available\n\nAvailable modes:\n  activeseconds  - Print number of seconds masternode recognized by the network as enabled\n                   (since latest issued \"masternode start/start-many/start-alias\")\n  addr           - Print ip address associated with a masternode (can be additionally filtered, partial match)\n  full           - Print info in format 'status protocol pubkey IP lastseen activeseconds lastpaid'\n                   (can be additionally filtered, partial match)\n  lastseen       - Print timestamp of when a masternode was last seen on the network\n  lastpaid       - The last time a node was paid on the network\n  protocol       - Print protocol of a masternode (can be additionally filtered, exact match))\n  pubkey         - Print public key associated with a masternode (can be additionally filtered,\n                   partial match)\n  rank           - Print rank of a masternode based on current block\n  status         - Print masternode status: ENABLED / EXPIRED / VIN_SPENT / REMOVE / POS_ERROR\n                   (can be additionally filtered, partial match)\n"}

The answer is in the output you provided

Code:

root@vultr:~/.dash# ./dash-cli masternodelist full

or to filter by specific IP

Code:

root@vultr:~/.dash# ./dash-cli masternodelist full 127.0.1.47

[toknormal]

Third party solutions for securing 0-conf instant transactions starting to appear.

[Honest Tim]

Yeah, been running for almost a year now. 768Meg, never had any probs before. Nothing has changed.

 HDD ? How long since you've dumped the debug.log? Also, keep in mind Dashninja may have it's quirks from time to time. If Elb is working the backend, some funky info may result from it.

 Did you try list | grep xx.xx.xx.xx ?

hmmm. Is there a way to search by IP address now?? It appears you need to search by Vin (Hash-Index), now that we use "dash-cli" Unless theres a switch somewhere??

This gives me hope..... but also a headache!

root@vultr:~/.dash# ./dash-cli masternodelist help
error: {"code":-1,"message":"masternodelist ( \"mode\" \"filter\" )\nGet a list of masternodes in different modes\n\nArguments:\n1. \"mode\"      (string, optional/required to use filter, defaults = status) The mode to run list in\n2. \"filter\"    (string, optional) Filter results. Partial match by IP by default in all modes,\n                                    additional matches in some modes are also available\n\nAvailable modes:\n  activeseconds  - Print number of seconds masternode recognized by the network as enabled\n                   (since latest issued \"masternode start/start-many/start-alias\")\n  addr           - Print ip address associated with a masternode (can be additionally filtered, partial match)\n  full           - Print info in format 'status protocol pubkey IP lastseen activeseconds lastpaid'\n                   (can be additionally filtered, partial match)\n  lastseen       - Print timestamp of when a masternode was last seen on the network\n  lastpaid       - The last time a node was paid on the network\n  protocol       - Print protocol of a masternode (can be additionally filtered, exact match))\n  pubkey         - Print public key associated with a masternode (can be additionally filtered,\n                   partial match)\n  rank           - Print rank of a masternode based on current block\n  status         - Print masternode status: ENABLED / EXPIRED / VIN_SPENT / REMOVE / POS_ERROR\n                   (can be additionally filtered, partial match)\n"}

The answer is in the output you provided

Code:

root@vultr:~/.dash# ./dash-cli masternodelist full

or to filter by specific IP

Code:

root@vultr:~/.dash# ./dash-cli masternodelist full 127.0.1.47

Thank you Sir. I just didn't know how to go that final step with the syntax.

Anyway, this proves that this particular masternode is not live, which is very irritating as it's still simply "falling off" the dash ninja radar.

[BusterNutBag]

The masternode graph's gone a bit wonky.

Unwonked!

link?

[toknormal]

link?

You just quoted it. (In my original post    )

[qwizzie]

Yeah, been running for almost a year now. 768Meg, never had any probs before. Nothing has changed.

 HDD ? How long since you've dumped the debug.log? Also, keep in mind Dashninja may have it's quirks from time to time. If Elb is working the backend, some funky info may result from it.

 Did you try list | grep xx.xx.xx.xx ?

hmmm. Is there a way to search by IP address now?? It appears you need to search by Vin (Hash-Index), now that we use "dash-cli" Unless theres a switch somewhere??

This gives me hope..... but also a headache!

root@vultr:~/.dash# ./dash-cli masternodelist help
error: {"code":-1,"message":"masternodelist ( \"mode\" \"filter\" )\nGet a list of masternodes in different modes\n\nArguments:\n1. \"mode\"      (string, optional/required to use filter, defaults = status) The mode to run list in\n2. \"filter\"    (string, optional) Filter results. Partial match by IP by default in all modes,\n                                    additional matches in some modes are also available\n\nAvailable modes:\n  activeseconds  - Print number of seconds masternode recognized by the network as enabled\n                   (since latest issued \"masternode start/start-many/start-alias\")\n  addr           - Print ip address associated with a masternode (can be additionally filtered, partial match)\n  full           - Print info in format 'status protocol pubkey IP lastseen activeseconds lastpaid'\n                   (can be additionally filtered, partial match)\n  lastseen       - Print timestamp of when a masternode was last seen on the network\n  lastpaid       - The last time a node was paid on the network\n  protocol       - Print protocol of a masternode (can be additionally filtered, exact match))\n  pubkey         - Print public key associated with a masternode (can be additionally filtered,\n                   partial match)\n  rank           - Print rank of a masternode based on current block\n  status         - Print masternode status: ENABLED / EXPIRED / VIN_SPENT / REMOVE / POS_ERROR\n                   (can be additionally filtered, partial match)\n"}

The answer is in the output you provided

Code:

root@vultr:~/.dash# ./dash-cli masternodelist full

or to filter by specific IP

Code:

root@vultr:~/.dash# ./dash-cli masternodelist full 127.0.1.47

Thank you Sir. I just didn't know how to go that final step with the syntax.

Anyway, this proves that this particular masternode is not live, which is very irritating as it's still simply "falling off" the dash ninja radar.

maybe put both cold and hot wallet on latest version (.56) as that has some bug fixes and give it a restart from cold wallet just to be sure ?
followed by ./dash-cli masternodelist full | grep -e IPADDRESS to make sure its enabled ? (just thinking outloud here...)

edit : and maybe delete your peers.dat before the restart...
edit : and check if your debug.log on the hot wallet (server) has not grown too large..
edit : and check if both your wallets are in total sync with the blockchain before restart from cold wallet (you can check here for example : https://chainz.cryptoid.info/dash/)

[BusterNutBag]

link?

You just quoted it. (In my original post    )

oh - lol
I thought that was just a pix and not the 'live' screen - lol
[it is the live screen - right? lol]

[semajjames]

edit : and check if your debug.log on the hot wallet (server) has not grown too large..

So qwizzie this "debug log" you talk about that lives on my MN's vultr server yeah ?

[spatula]

edit : and check if your debug.log on the hot wallet (server) has not grown too large..

So qwizzie this "debug log" you talk about that lives on my MN's vultr server yeah ?

Correct. It can be found in your .dash directory

[semajjames]

edit : and check if your debug.log on the hot wallet (server) has not grown too large..

So qwizzie this "debug log" you talk about that lives on my MN's vultr server yeah ?

Correct. It can be found in your .dash directory

how big is "to big" and how long does this take to happen ?

[qwizzie]

edit : and check if your debug.log on the hot wallet (server) has not grown too large..

So qwizzie this "debug log" you talk about that lives on my MN's vultr server yeah ?

Correct. It can be found in your .dash directory

how big is "to big" and how long does this take to happen ?

my current debug.log is about 2.5 MB, people have reported in the past that their debug.log got into the gigabytes i think.
i normally delete it between version upgrades (a new one gets created automatically upon restart).
There are also commands available to "auto-shrink" your debug.log

[BusterNutBag]

edit : and check if your debug.log on the hot wallet (server) has not grown too large..

So qwizzie this "debug log" you talk about that lives on my MN's vultr server yeah ?

Correct. It can be found in your .dash directory

how big is "to big" and how long does this take to happen ?

my current debug.log is about 2.5 MB, people have reported in the past that their debug.log got into the gigabytes i think.
i normally delete it between version upgrades (a new one gets created automatically upon restart).
There are also commands available to "auto-shrink" your debug.log

would .....

debug=0

turn off the file?


Or - can't it be dumped into 'no-where'?
[not actually creating the file?]