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

[Jeff8247]

I don't get it IceShitter, you call DASH a scam and you sir are quite clearly are a scammer yourself! Ironic don't you think?

[eduffield]

Dash's NBT (Next Big Thing)  will be revealed 7th of october 2015 and appearently consists of a juicy 50 pages of whitepaper.
Exciting times ahead...

Actually this paper is quite special and we're going to release this the correct way. This is going to be huge  

[eduffield]

I don't get it IceShitter, you call DASH a scam and you sir are quite clearly are a scammer yourself! Ironic don't you think?

The true irony is knowing about this project so early in it's life and not seeing what is right in front of you. That's going to sting in five years...

[AdamWhite]

I don't get it IceShitter, you call DASH a scam and you sir are quite clearly are a scammer yourself! Ironic don't you think?

The true irony is knowing about this project so early in it's life and not seeing what is right in front of you. That's going to sting in five years...

You sound delusional.  Congratulations on the Bitfinex delisting, its nice to see scam coins getting delisted.

[tungfa]

lol
lol
you guys eh
 

[TaoOfSaatoshi]

Dash's NBT (Next Big Thing)  will be revealed 7th of october 2015 and appearently consists of a juicy 50 pages of whitepaper.
Exciting times ahead...

Actually this paper is quite special and we're going to release this the correct way. This is going to be huge 

I don't get it IceShitter, you call DASH a scam and you sir are quite clearly are a scammer yourself! Ironic don't you think?

The true irony is knowing about this project so early in it's life and not seeing what is right in front of you. That's going to sting in five years...

Well said, oh captain my captain!

[wozzek23]

After doing extensive researched on DASH, and the developers behind the coin, I have decided to invest. I really think DASH has a bright future ahead of it. The developers behind DASH really are passionate about their work and all they want is to see their baby succeed.

Whomever is doing this seems to me as a troll, but this time on our side. I dislike this shite more than these spouting garbage, it feels so phony and reeks of despair. If this is a legitimate new user / investor, I am sorry for my skepticism, but it would take something more than one post to convince me.

[wozzek23]

Actually this paper is quite special and we're going to release this the correct way. This is going to be huge  

The true irony is knowing about this project so early in it's life and not seeing what is right in front of you. That's going to sting in five years...

THIS is real   -- when you have a genius developer who had been delivering on his promises for months and months stating something like that...

[moocowmoo]

my weekend hack session ran a little long...

https://github.com/moocowmoo/dashman

Enjoy!

[Sub-Ether]

Actually this paper is quite special and we're going to release this the correct way. This is going to be huge  

The true irony is knowing about this project so early in it's life and not seeing what is right in front of you. That's going to sting in five years...

THIS is real   -- when you have a genius developer who had been delivering on his promises for months and months stating something like that...

+1
and waiting for deletion 

[Nexious]

Nexious has updated to Version: 0.12.0.53

[110110101]

my weekend hack session ran a little long...

https://github.com/moocowmoo/dashman

Enjoy!

Working great moocowmoo! May I perhaps ask for a future feature? When looking for the dash-cli path, could we perhaps make a local setting that is not overwritten after each update? I am running the dashd and dash-cli binaries in a local folder (not in path) rather than in .dash

I was thinking if we had a dashman_local.conf where the paths could be specified. if this file is not present than the dasman tool looks into .dashman-functions.sh for the "normal" paths for the binaries. Additionally, when updating dashman or making a new install, the dashman_local.conf is not created/overwritten so the user must make this modification themselves. I am aware that this takes some time to create so if you are too busy or think that this is unnecessary, I will continue to adjust my paths by hand

[moocowmoo]

Working great moocowmoo! May I perhaps ask for a future feature? When looking for the dash-cli path, could we perhaps make a local setting that is not overwritten after each update? I am running the dashd and dash-cli binaries in a local folder (not in path) rather than in .dash

I was thinking if we had a dashman_local.conf where the paths could be specified. if this file is not present than the dasman tool looks into .dashman-functions.sh for the "normal" paths for the binaries. Additionally, when updating dashman or making a new install, the dashman_local.conf is not created/overwritten so the user must make this modification themselves. I am aware that this takes some time to create so if you are too busy or think that this is unnecessary, I will continue to adjust my paths by hand

Glad to hear it!

You can just run dashman from that directory and it'll choose that directory for the install path.
(it searches the current directory first)

For instance if you're keeping dash-cli and dashd in ~/my_dash_folder and have cloned dashman into ~/src, you can do:

Code:

cd ~/my_dash_folder
~/src/dashman/dashman [command]

Maybe that'll work for you?

Alternately you can symlink them from the ~/.dash directory into your ~/my_dash_folder like this:

Code:

ln -s ~/.dash/dash-cli ~/my_dash_folder
ln -s ~/.dash/dashd ~/my_dash_folder

Personally, I like to keep everything dash in ~/.dash, because (for me) it's "dashs spot", less to think about.

My setup is this:

Code:

mkdir ~/bin
ln -s ~/.dash/dash-cli ~/bin
ln -s ~/.dash/dashd ~/bin
echo 'export PATH=~/bin:$PATH' >> ~/.bashrc

With my single addition of ~/bin to PATH (the .bashrc addition), adding things to the search path (run anywhere) is just a matter of symlinking them into ~/bin

The bonus here is ~/bin/dash-cli points to ~/.dash/dash-cli which points to ~/.dash/dash-cli-0.12.0.53 -- so I always know what version I have running just by looking at the target by doing:

Code:

$ readlink -f `which dash-cli`
/home/ubuntu/.dash/dash-cli-0.12.0.53

where PATH is actually finding (running):

Code:

$ which dash-cli
/home/ubuntu/bin/dash-cli

It may seem like overkill, but I learned to appreciate version-named executables for maintenance reasons. (I maintain a *lot* of systems)
A simple

Code:

ls -l

tells you everything you need to know.

[Kienbui]

I have a problem:

./dashman status

 --> public IP address        : XXXXXXXX
 --> dashd version            : 0.12.0.53
 --> dashd up-to-date         : YES
--> dashd running            : NO
 --> dashd responding (rpc)   : YES
 --> dashd listening  (ip)    : YES
 --> dashd connecting (peers) : YES
 --> dashd blocks synced      : YES
 --> masternode started       : YES
 --> masternode visible       : YES
 --> public IP port open      : YES
 --> dashd connections        : 8
 --> total masternodes        : 3016
 --> dashd last block         : 332254
 --> chainz last block        : 332254

Despite

./dash-cli getinfo
and

./dash-cli masternodelist full | grep -e IP

still gives a running status

[moocowmoo]

I have a problem:
--> dashd running            : NO

congratulations! you found a bug! Sorta.

That test looks for a pidfile at ~/.dash/dashd.pid

Which the daemon doesn't create sometimes.

I'm guessing you haven't restarted that wallet in a while, or it'd be there.
(I'm pretty sure it creates it on exit, but I'm guessing.)

See if that file is there.  If not do:

Code:

./dash-cli stop ; sleep 10 ; ./dashd

or, even better:

Code:

./dashman restart now

and look again.

[BiteMyShinyMetalAss]

Now with EuroBasket 2015 directbet.eu is just nice! It accepts DASH and its nice to bet there. Although they lack app and you have to use proxy for lots of countries being banned, but so nice to bet there! Go team LT! 

[tombtc]

Dash's NBT (Next Big Thing)  will be revealed 7th of october 2015 and appearently consists of a juicy 50 pages of whitepaper.
Exciting times ahead...

Actually this paper is quite special and we're going to release this the correct way. This is going to be huge  

Have I missed something or there was no info about this whitepaper released yet?
And what do you mean by "the correct way"?
Thanks

[Kienbui]

I have a problem:
--> dashd running            : NO

congratulations! you found a bug! Sorta.

That test looks for a pidfile at ~/.dash/dash.pid

Which the wallet doesn't create sometimes.

I'm guessing you haven't restarted that wallet in a while, or it'd be there.
(I'm pretty sure it creates it on exit, but I'm guessing.)

See if that file is there.  If not do:

Code:

./dash-cli stop ; sleep 10 ; ./dashd

or, even better:

Code:

./dashman restart now

and look again.

I tried, but that problem still persist.

[moocowmoo]

I have a problem:
--> dashd running            : NO

congratulations! you found a bug! Sorta.

That test looks for a pidfile at ~/.dash/dashd.pid

Which the daemon doesn't create sometimes.

I'm guessing you haven't restarted that wallet in a while, or it'd be there.
(I'm pretty sure it creates it on exit, but I'm guessing.)

See if that file is there.  If not do:

Code:

./dash-cli stop ; sleep 10 ; ./dashd

or, even better:

Code:

./dashman restart now

and look again.

I tried, but that problem still persist.

if that file isn't being created, try:

Code:

touch ~/.dash/dashd.pid

then restart dashd and see if it's put it's pid in it by doing:

Code:

cat ~/.dash/dashd.pid

and see if it spits out a number.

[cjmoles]

Wow!....Just went thru the first few pages of this thread and it is amazing how much FUD this dev had to deal with in the beginning and he just kept working hard!  And, now it's of the more successful coins out there!  Very inspiring...well done!

Just WOW!