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

[kubuminer]

...snip...

let's start from scratch:
check dependencies here https://github.com/dashpay/dash/blob/master/doc/build-unix.md#dependency-build-instructions-ubuntu--debian and then

Code:

./autogen.sh
./configure --disable-tests
make clean
make

EDIT: when building on server you can also specify " --without-gui" as configure option

after type comand - ./configure --disable-tests

i listen this

configure: creating ./config.status
config.status: creating Makefile
config.status: creating libsecp256k1.pc
config.status: creating src/libsecp256k1-config.h
config.status: src/libsecp256k1-config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
Fixing libtool for -rpath problems.

it is correct

and after make clean
make


/home/user/DashCoin/src/spork.cpp:196: undefined reference to `darkSendSigner'
/home/user/DashCoin/src/spork.cpp:196: undefined reference to `CDarkSendSigner::SetKey(std::string, std::string&, CKey&, CPubKey&)'
/home/user/DashCoin/src/spork.cpp:202: undefined reference to `darkSendSigner'
/home/user/DashCoin/src/spork.cpp:202: undefined reference to `CDarkSendSigner::SignMessage(std::string, std::string&, std::vector<unsigned char, std::allocator<unsigned char> >&, CKey)'
/home/user/DashCoin/src/spork.cpp:207: undefined reference to `darkSendSigner'
/home/user/DashCoin/src/spork.cpp:207: undefined reference to `CDarkSendSigner::VerifyMessage(CPubKey, std::vector<unsigned char, std::allocator<unsigned char> >&, std::string, std::string&)'
collect2: error: ld returned 1 exit status
make[2]: *** [dashd] Error 1
make[2]: Leaving directory `/home/bittrexcoin/DashCoin/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/bittrexcoin/DashCoin/src'
make: *** [all-recursive] Error 1


and error compile. help fix this - Fixing libtool for -rpath problems.

[crowning]

and error compile. help fix this - Fixing libtool for -rpath problems.

That's normal, no need to worry.

I wonder where and how you got the sources. Did you use "git clone https://github.com/dashpay/dash.git" from the official sources?

[kubuminer]

and error compile. help fix this - Fixing libtool for -rpath problems.

That's normal, no need to worry.

I wonder where and how you got the sources. Did you use "git clone https://github.com/dashpay/dash.git" from the official sources?

yes i use this source - Did you use "git clone https://github.com/dashpay/dash.git" from the official sources?


now this error

collect2: error: ld returned 1 exit status
make[2]: *** [dashd] Error 1
make[2]: Leaving directory `/home/bittrexcoin/DashCoin/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/bittrexcoin/DashCoin/src'
make: *** [all-recursive] Error 1

[kubuminer]

...snip...

let's start from scratch:
check dependencies here https://github.com/dashpay/dash/blob/master/doc/build-unix.md#dependency-build-instructions-ubuntu--debian and then

Code:

./autogen.sh
./configure --disable-tests
make clean
make

EDIT: when building on server you can also specify " --without-gui" as configure option

after type comand - ./configure --disable-tests

i listen this

configure: creating ./config.status
config.status: creating Makefile
config.status: creating libsecp256k1.pc
config.status: creating src/libsecp256k1-config.h
config.status: src/libsecp256k1-config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
Fixing libtool for -rpath problems.

it is correct

and after make clean
make


/home/user/DashCoin/src/spork.cpp:196: undefined reference to `darkSendSigner'
/home/user/DashCoin/src/spork.cpp:196: undefined reference to `CDarkSendSigner::SetKey(std::string, std::string&, CKey&, CPubKey&)'
/home/user/DashCoin/src/spork.cpp:202: undefined reference to `darkSendSigner'
/home/user/DashCoin/src/spork.cpp:202: undefined reference to `CDarkSendSigner::SignMessage(std::string, std::string&, std::vector<unsigned char, std::allocator<unsigned char> >&, CKey)'
/home/user/DashCoin/src/spork.cpp:207: undefined reference to `darkSendSigner'
/home/user/DashCoin/src/spork.cpp:207: undefined reference to `CDarkSendSigner::VerifyMessage(CPubKey, std::vector<unsigned char, std::allocator<unsigned char> >&, std::string, std::string&)'
collect2: error: ld returned 1 exit status
make[2]: *** [dashd] Error 1
make[2]: Leaving directory `/home/bittrexcoin/DashCoin/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/bittrexcoin/DashCoin/src'
make: *** [all-recursive] Error 1


and error compile. help fix this - Fixing libtool for -rpath problems.

Could this be a SWAP issue??

swap is empty - 0

[kubuminer]

...snip...

let's start from scratch:
check dependencies here https://github.com/dashpay/dash/blob/master/doc/build-unix.md#dependency-build-instructions-ubuntu--debian and then

Code:

./autogen.sh
./configure --disable-tests
make clean
make

EDIT: when building on server you can also specify " --without-gui" as configure option

after type comand - ./configure --disable-tests

i listen this

configure: creating ./config.status
config.status: creating Makefile
config.status: creating libsecp256k1.pc
config.status: creating src/libsecp256k1-config.h
config.status: src/libsecp256k1-config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
Fixing libtool for -rpath problems.

it is correct

and after make clean
make


/home/user/DashCoin/src/spork.cpp:196: undefined reference to `darkSendSigner'
/home/user/DashCoin/src/spork.cpp:196: undefined reference to `CDarkSendSigner::SetKey(std::string, std::string&, CKey&, CPubKey&)'
/home/user/DashCoin/src/spork.cpp:202: undefined reference to `darkSendSigner'
/home/user/DashCoin/src/spork.cpp:202: undefined reference to `CDarkSendSigner::SignMessage(std::string, std::string&, std::vector<unsigned char, std::allocator<unsigned char> >&, CKey)'
/home/user/DashCoin/src/spork.cpp:207: undefined reference to `darkSendSigner'
/home/user/DashCoin/src/spork.cpp:207: undefined reference to `CDarkSendSigner::VerifyMessage(CPubKey, std::vector<unsigned char, std::allocator<unsigned char> >&, std::string, std::string&)'
collect2: error: ld returned 1 exit status
make[2]: *** [dashd] Error 1
make[2]: Leaving directory `/home/bittrexcoin/DashCoin/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/bittrexcoin/DashCoin/src'
make: *** [all-recursive] Error 1


and error compile. help fix this - Fixing libtool for -rpath problems.

Could this be a SWAP issue??

swap is empty - 0

maybe need update system? ))))))))

[kubuminer]

...snip...

let's start from scratch:
check dependencies here https://github.com/dashpay/dash/blob/master/doc/build-unix.md#dependency-build-instructions-ubuntu--debian and then

Code:

./autogen.sh
./configure --disable-tests
make clean
make

EDIT: when building on server you can also specify " --without-gui" as configure option

after type comand - ./configure --disable-tests

i listen this

configure: creating ./config.status
config.status: creating Makefile
config.status: creating libsecp256k1.pc
config.status: creating src/libsecp256k1-config.h
config.status: src/libsecp256k1-config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
Fixing libtool for -rpath problems.

it is correct

and after make clean
make


/home/user/DashCoin/src/spork.cpp:196: undefined reference to `darkSendSigner'
/home/user/DashCoin/src/spork.cpp:196: undefined reference to `CDarkSendSigner::SetKey(std::string, std::string&, CKey&, CPubKey&)'
/home/user/DashCoin/src/spork.cpp:202: undefined reference to `darkSendSigner'
/home/user/DashCoin/src/spork.cpp:202: undefined reference to `CDarkSendSigner::SignMessage(std::string, std::string&, std::vector<unsigned char, std::allocator<unsigned char> >&, CKey)'
/home/user/DashCoin/src/spork.cpp:207: undefined reference to `darkSendSigner'
/home/user/DashCoin/src/spork.cpp:207: undefined reference to `CDarkSendSigner::VerifyMessage(CPubKey, std::vector<unsigned char, std::allocator<unsigned char> >&, std::string, std::string&)'
collect2: error: ld returned 1 exit status
make[2]: *** [dashd] Error 1
make[2]: Leaving directory `/home/bittrexcoin/DashCoin/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/bittrexcoin/DashCoin/src'
make: *** [all-recursive] Error 1


and error compile. help fix this - Fixing libtool for -rpath problems.

Could this be a SWAP issue??

swap is empty - 0

maybe need update system? ))))))))

sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade && sudo apt-get autoremove


I doubt it but you should always update first

i am chesk on empty system - work correct. on my old system dont have compile. after copy dash-master with compille walet from empty system on my old system wallet launch with error

[coins101]

Tao sync update time  
https://dashtalk.org/threads/dash-versus-bitcoin-versus-darkcoin-wallet-update-benchmark-times.4479/#post-61751

Short summary

Total time for entire Dash (0.12.0.49) blockchain = 35 minutes and 2 seconds
Average Tao sync ratio from 2 samples = 0.1517 sec / hour

% Tao sync improvement from earlier Tao ratio (v0.11.2.23) = (0.2389 - 0.1517 ) /0.2389 = + 36.5%
Degree of Tao improvement  compared to darkcoin (0.11.1.25) = (1.345 / 0.1517) =  8.86 times faster

Average Tao bitcoin to Tao dash ratio = (4.144 / 0.1517) = 27.32 times faster than bitcoin
(best tao / tao ratio = 4.144 / 0.1345 = 30.8 times faster)

Average Tao Monero to Tao Dash ratio = (14.22 / 0.1517) = 93.7 times faster than Monero
(best tao / tao ratio = 14.22 / 0.1345 = 105.7 times faster)

Edit: Notice that in March we were only 2.4 times faster than bitcoin, the gap is widening..

We could do with an idea of what is causing this speed improvement. Bitcoin core should be being updated to be more efficient, even though the chain is growing.

[tungfa]

Please Vote
https://dashtalk.org/threads/budget-proposal-promotion-reimbursement-core-team.6006/
 

[moocowmoo]

Luv the pix but the vote basically ended :-PASSED

Not quite.  What happened is we reached the threshold of required YES's to go ahead with the proposals.

If all the masternodes that haven't voted vote NO I think this would reverse this, but I'm not sure how it all works quite yet.

What I do know is that Dash's Blockchain Governance voting is not a one-time vote -- anybody can change their vote at any time.

This is how projects that aren't living up to expectation get cancelled.  People simply vote no (even if they'd previously voted yes.)

[eduffield]

*********** v12.0.51 *************

Author: Evan Duffield <evan@dashpay.io>

    mnbudget nextblock
    v51 bump
    revert c5d6b reduced mnw bandwidth
    finbudget old vote check removed
    enable cache files / remove old vote check

--

https://www.dashpay.io/downloads/

[tungfa]

*********** v12.0.51 *************

Author: Evan Duffield <evan@dashpay.io>

    mnbudget nextblock
    v51 bump
    revert c5d6b reduced mnw bandwidth
    finbudget old vote check removed
    enable cache files / remove old vote check

--

https://www.dashpay.io/downloads/

[TanteStefana2]

*********** v12.0.51 *************

Author: Evan Duffield <evan@dashpay.io>

    mnbudget nextblock
    v51 bump
    revert c5d6b reduced mnw bandwidth
    finbudget old vote check removed
    enable cache files / remove old vote check

--

https://www.dashpay.io/downloads/

Great update.  It took no time for my wallets to see that the masternode was successfully started.  Before it could take up to 5 minutes, but instant again here

[Bridgewater]

A friendly reminder to all who have Dash stored on Bitfinex, you will have untill 31st of august to move Dash out to your local Dash wallet

Per their announcement,

August 31 is actually the deadline for trading Dash on their exchange.
September 30 is the deadline for moving your Dash out.

And if you miss the Sept. 30 deadline, you can still contact 'finex directly to get your Dash back (but you might have to say "pretty please" and refer to them as "Darkcoins" before they'll release them to you)  

[Rux]

4/4 Masternodes from my MN Service are updated to .51

Have a nice flight

[Sub-Ether]

Tao sync update time  
https://dashtalk.org/threads/dash-versus-bitcoin-versus-darkcoin-wallet-update-benchmark-times.4479/#post-61751

Short summary

Total time for entire Dash (0.12.0.49) blockchain = 35 minutes and 2 seconds
Average Tao sync ratio from 2 samples = 0.1517 sec / hour

% Tao sync improvement from earlier Tao ratio (v0.11.2.23) = (0.2389 - 0.1517 ) /0.2389 = + 36.5%
Degree of Tao improvement  compared to darkcoin (0.11.1.25) = (1.345 / 0.1517) =  8.86 times faster

Average Tao bitcoin to Tao dash ratio = (4.144 / 0.1517) = 27.32 times faster than bitcoin
(best tao / tao ratio = 4.144 / 0.1345 = 30.8 times faster)

Average Tao Monero to Tao Dash ratio = (14.22 / 0.1517) = 93.7 times faster than Monero
(best tao / tao ratio = 14.22 / 0.1345 = 105.7 times faster)
Edit: Notice that in March we were only 2.4 times faster than bitcoin, the gap is widening..

We could do with an idea of what is causing this speed improvement. Bitcoin core should be being updated to be more efficient, even though the chain is growing.

Thoughts on that are,

1) bitcoin locks onto outdated client seed nodes (see end of post) this makes for slow downloads
Dash has 8 or 9 V12 seed nodes immediately making faster coms due to protocol matching and connection speeds

2) shortly after bitcoin 10 release(note:significant hop time improvement), the Tao ratio noticably increased to a high of 2.35 sec/hr on 7th March, this only lasted for around 2 weeks because by 27th March, was already hitting over 4 sec/hr.
The conclusion from this was that the network was satuated and the client speedups had absorbed any spare network speed, and now
bitcoin was back to a maxed out situation.

3) I overlooked measuring the total chain size in March, but was something like dash ~.7 gig and bitcoin ~35 gig, now we have dash = 1.2 gig and bitcoin =45 gigabytes, so both have increased in a similar manor, is it that the full bitcoin client is too much for the average personnal computer and global connections to handle and is going outside of Moore's law? if this is true there will be more Tao divergence as a tell sign.

[tungfa]

Luv the pix but the vote basically ended :-PASSED

Not quite.  What happened is we reached the threshold of required YES's to go ahead with the proposals.

If all the masternodes that haven't voted vote NO I think this would reverse this, but I'm not sure how it all works quite yet.

What I do know is that Dash's Blockchain Governance voting is not a one-time vote -- anybody can change their vote at any time.

This is how projects that aren't living up to expectation get cancelled.  People simply vote no (even if they'd previously voted yes.)

i totally agree with Moocowmoo
we want this as clear as possible

so please VOTE

[qwizzie]

Budgets Are Live
dashtalk post : https://dashtalk.org/threads/budget-proposal-promotion-reimbursement-core-team.6006/page-3#post-65239

A note about the budget system: https://dashtalk.org/threads/budget-proposal-promotion-reimbursement-core-team.6006/page-3#post-65235

I've added the budgets to the system and we are all set to vote. All you have to do to vote is load up a client with the masternode.conf. Your actual funds are NOT required to be online to vote on proposals

core-team :
eac6392cd0d63e4b2ebd3c60da2d3e13137c892cd4cd1a8f3885077ac86b7487

public-awareness :
cbafad18687045bb72fae611078fac09c3ec09c8379e357c36901ce84891f189

reimbursement :
428438998eeb3234b232a3609d2e0f1122049241e5ecad972554ad163772a109

To vote simply execute these commands:

./dash-cli mnbudget vote-many eac6392cd0d63e4b2ebd3c60da2d3e13137c892cd4cd1a8f3885077ac86b7487 yes
./dash-cli mnbudget vote-many cbafad18687045bb72fae611078fac09c3ec09c8379e357c36901ce84891f189 yes
./dash-cli mnbudget vote-many 428438998eeb3234b232a3609d2e0f1122049241e5ecad972554ad163772a109 yes

and for voting with a single masternode change "vote-many" to "vote"
end-result should be : "Voted successfully"

If you want to specifically vote against a specific budget because you dont agree with it then change the "yes" into a "no"

Masternode-owners please vote on the three existing budget proposals and also make sure you have upgraded to v0.12.0.51 !!

To check on the budget proposals : ./dash-cli mnbudget show (or in qt-wallet just type "mnbudget show") or check crowning's site Masternode status
To check on finalized budget proposals : ./dash-cli mnbudget projection (or in qt-wallet just type "mnbudget projection")

Eventhough these budget proposals have already passed i too think its important to ensure every masternode owner is aware of current and future budget proposals
and understand they have the power to vote !! (even after budget proposals have already passed). We need to involve as many masternode owners as possible both for now
and for in the future.

[BiteMyShinyMetalAss]

DO you have to vote from the cold wallet? can you vote from the server where masternode is running?

[qwizzie]

DO you have to vote from the cold wallet? can you vote from the server where masternode is running?

you can vote from hot wallet (server wallet without the actual coins). For single masternode voting it needs the dash.conf there and for
starting many masternodes at the same time it needs the masternode.conf there.

[LiteMine]

DO you have to vote from the cold wallet? can you vote from the server where masternode is running?

you can vote from hot wallet (server wallet without the actual coins). For single masternode voting it needs the dash.conf there and for
starting many masternodes at the same time it needs the masternode.conf there.

Are any instructions available for voting from an empty Windows wallet with the dash.conf or masternode.conf?