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

[yurimir]

It appears, that according to the good folks at Bitcoinwisdom, DRK/DASH, the fifth largest marketcap in crypto, simply doesn't exist!

What a joke that website is.

This hidden link works (should be used USA IP)

https://bitcoinwisdom.com/markets/cryptsy/drkbtc

[Triptolemoose]

It appears, that according to the good folks at Bitcoinwisdom, DRK/DASH, the fifth largest marketcap in crypto, simply doesn't exist!

What a joke that website is.

This hidden link works (should be used USA IP)

https://bitcoinwisdom.com/markets/cryptsy/drkbtc

Or just use the shortcut http://dashwisdom.com/

(Still need USA IP etc)

[toknormal]

Mike Hearn responding to the core devs open letter about "workshops".

https://www.reddit.com/r/Bitcoin/comments/3j8rg1/an_open_letter_to_the_bitcoin_community_from_the/cunzj9z

I think he's right. The last thing Bitcoin (or any crypto) needs is a developer cartel trying to pass itself off as "consensus".

The Bitcoin core devs have become a runaway train. Penny bricklayers who think they're monetary architects.

If they really understood the least thing about the decentralised ethics they claim to champion, they'd be celebrating the diversifying code and developer base, not trying to shut it down. They'd be celebrating the diversified crypto-economy and not trying to shut that down.

Real cryptocurrency "consenus" (all it is is a mining consensus) was designed specifically to handle this situation. Anybody is allowed to chuck anything they want at the miners and try to get it accepted. The idea of "developer consenus" never existed - neither in crypto, nor in the open source world itself. How many disparate interpretations of the Linux Standard Base specs are there in existence ?

Bitcoin was designed to cope with diversity and challenges to the accepted codebase - so lets see it in action ! 

[toknormal]

P.S. Notice that in the above debate, nobody talks about coherence.

When it comes to long term development, coherence is far more important than consensus, as long as sensible goals are being established. That is what's great about the blockchain governance mechanism that Dash is implementing.

The Dash network still requires a mining consensus for revisions to be accepted, but the blockchain governance mechanism now supports a level of developmental coherence and continuity (not to mention funding) on top of that that's non-existent in bitcoin. It can prevent the "runaway train" phenomenon that's happening in bitcoin.

(b.t.w., whatever you think of Mike Hearn - and I accept that he's had some dodgy ideas like blacklisting etc - he has been attempting to pursue a coherent technical strategy in terms of adhering to the Satoshi agenda of an independent, universally accessible monetary token. It's the so-called "Blockstream" agenda that's the runaway train here because they are ditching that idea in favour of a network thats dependent on horizontal and vertical superstructures (in the form of sidechains and payment channels respectively), which dominates all sectors and which is governed by a developer cartel instead of popular choice).

P.P.S. I'm not against "superstructures" in principle - I think that mass adoption of any crypto will require payment channels to handle extreme loads such as in retail sectors etc. However I think the network should still be useable directly by individuals and that its development agenda should make its independence of third party services a very high priority.

[tungfa]

3013 MN's !!
Congrats all around !
https://dashninja.pl

[tungfa]

Is that a Cover or what !
(No Dash, just crypto)
http://www.bloomberg.com/news/features/2015-09-01/blythe-masters-tells-banks-the-blockchain-changes-everything

[110110101]

Is there a simply guide how to build the Dash Linux daemon from source?
i read the instructions in the source but I was having building problems and thought that there might be something that I was missing or that the build environment is incorrect.

This one https://github.com/dashpay/dash/blob/master/doc/build-unix.md ? What kind of build problems did you have?
Post error here and we'll try to help.

And btw, check "Dependencies" section there first.

Thanks UdjinM6 for the pointer, I'm checking it out and correcting a few errors; I had the wrong version of libdb and also no swap space. Fixing these problems and trying again.

Update: seems now that when running make, it crashes when attempting to build libbitcoin_server_a-main.o

Code:

~/dash_git/dash$ make
Making all in src
make[1]: Entering directory `/home/****/dash_git/dash/src'
make[2]: Entering directory `/home/****/dash_git/dash/src'
  CXX      libbitcoin_server_a-main.o
g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[2]: *** [libbitcoin_server_a-main.o] Error 4
make[2]: Leaving directory `/home/****/dash_git/dash/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/****/dash_git/dash/src'
make: *** [all-recursive] Error 1
****@masternode01:~/dash_git/dash$ free
             total       used       free     shared    buffers     cached
Mem:        501800     174040     327760         16       1780      25236
-/+ buffers/cache:     147024     354776
Swap:      1048572     205620     842952

In most cases this "g++: internal compiler error: Killed (program cc1plus)" means you need even more memory for compiler otherwise OS see that it running out of memory and kill the heaviest process. Make swap 2Gb for example and try again (I have 4Gb just in case).

Thanks a lot sir! This indeed was the case, I changed the swap to 3GB and the compiler error went away. Cheers!

[Sub-Ether]

edit: maybe they should test DASH also? - we ready for some thing like this?

Our blocks would fill up the same and the attack could be performed with less transaction charges incurred, but we have more headroom because we are 4 times more blocks, are more empty than full and there is a flood spike preventative fail safe with instantX that does not need confirming as such but would have to go into the chain at some point.
(btw, my record in testnet using IX flooding into only 1 block is 340 transactions using 1 client)

Bllock size puts a limit on transactions, but also limits blockchain growth.  The questions is what happens to the block chain with millions of transactions.  It still isn't close to the point of sale transactions in the trillions.  DASH doesn't really look any better than BTC.  Transaction size is about the same (1KB) and this is what makes the blockchain bloat when it scales up.  See below.
For BTC
Currently, bitcoin can only do 2-4 transactions per second.  So if 64 million people want to transact in bitcoin, they could only make 1 transaction per year with current block size.
If we look at banking transaction, this is what is needed for blocksize for each.
US Bank Wires(150 Million transactions) = 1.7MB
Swift(international) wires(5 Billion transactions) = 53.3MB
ACH(19 Billion transactions) = 202.4MB
With the 202.4MB blocksize that would add 29GB to the blockchain each day.

For DASH
OK so looking at one of the peak transaction days June 21st.  5K average block size (I assume this is Kilobytes) and 2.75K transactions (I assume 2750 transactions)
5KB/2750 * 576 blocks/day = 1.04 KB transaction size(.001MB)

Block size with DASH needed for:
US Bank Wires(150 Million transactions) = 0.74MB
Swift(international) wires(5 Billion transactions) = 24.7MB
ACH(19 Billion transactions) = 93.9MB
Now lets look at the ACH transactions with DASH. 93.9MB X 576 blocks/day so daily add to the blockchain is 54GB.

We need to find a way to cram more transactions in less data, cutting out old transactions, or doing something Dashingly smart.

I don't agree with your calculation, but I like the all inclusive idea of capturing every transaction on the planet.
so using 1k as the average transaction size and extending:-

Total transaction size per day = [(.150 + 5 +19)*10^9] * 1024 =24.7 terrabytes per day !

if 576 blocks per day, that would mean every block size = 24.7 * (10^12) /576 = 42.9 gigabytes per block required !!

assuming 1 block= 1MB,
42.9 GB / 0.001 GB =42882

scalability factor required for entire transactions= 42882 times size reduction !!!
(and with 1 as yet unpruned transaction = 1024 / 42882 = 0.024 Bytes long)

It could be possible if a secondary master records database was created, the same addresses were used, scrubbing the empty addresses and with a limited number of new replacement addresses ? ...

[TanteStefana2]

HOWDY DOODY!  Ugh!  This took almost 4 hours, hows that?

Ok, I made a tutorial on how to restart your dashd daemon in case of shutdown or crash.  I explained it in detail, hopefully correctly.

https://dashtalk.org/threads/keep-your-mn-up-and-running-after-crash-ubuntu-w-explainations.6063/

Thanks to all of you who explained how to do this, I made a tutorial that I try to explain in detail how it works.  Thanks especially to GermanRed+ because he/she gave me the final key to making this work on a system with multiple users running a masternode.  It can still be used as is for single users, but if used with multiple users, you will be able to detect if any running instance of dash has crashed and have it start back up.   I explain my setup, and hopefully, if anyone needs something slightly different they will be able to figure out how.  The last post, #3 summarizes it all for quick setup

[BiteMyShinyMetalAss]

I am a bit slow... Which excange has the biggest volume for $ Dash trades? Is this new russian based in London?

[tungfa]

I am a bit slow... Which excange has the biggest volume for $ Dash trades? Is this new russian based in London?

http://coinmarketcap.com/currencies/dash/#markets

cryptsy (as always) on #1
try the russian/london one, i hear good things about them

[BiteMyShinyMetalAss]

I am a bit slow... Which excange has the biggest volume for $ Dash trades? Is this new russian based in London?

http://coinmarketcap.com/currencies/dash/#markets

cryptsy (as always) on #1
try the russian/london one, i hear good things about them

Thank you.
This means we dont have strong DASH/USD market place... Damn...

[miningpros]

http://www.zerohedge.com/news/2015-09-02/china-scrambles-enforce-capital-controls-capital-flight-threatens-economy-which-grea

No Dash, just about blockchain , maybe already posted

[Solarminer]

edit: maybe they should test DASH also? - we ready for some thing like this?

Our blocks would fill up the same and the attack could be performed with less transaction charges incurred, but we have more headroom because we are 4 times more blocks, are more empty than full and there is a flood spike preventative fail safe with instantX that does not need confirming as such but would have to go into the chain at some point.
(btw, my record in testnet using IX flooding into only 1 block is 340 transactions using 1 client)

Bllock size puts a limit on transactions, but also limits blockchain growth.  The questions is what happens to the block chain with millions of transactions.  It still isn't close to the point of sale transactions in the trillions.  DASH doesn't really look any better than BTC.  Transaction size is about the same (1KB) and this is what makes the blockchain bloat when it scales up.  See below.
For BTC
Currently, bitcoin can only do 2-4 transactions per second.  So if 64 million people want to transact in bitcoin, they could only make 1 transaction per year with current block size.
If we look at banking transaction, this is what is needed for blocksize for each.
US Bank Wires(150 Million transactions) = 1.7MB
Swift(international) wires(5 Billion transactions) = 53.3MB
ACH(19 Billion transactions) = 202.4MB
With the 202.4MB blocksize that would add 29GB to the blockchain each day.

For DASH
OK so looking at one of the peak transaction days June 21st.  5K average block size (I assume this is Kilobytes) and 2.75K transactions (I assume 2750 transactions)
5KB/2750 * 576 blocks/day = 1.04 KB transaction size(.001MB)

Block size with DASH needed for:
US Bank Wires(150 Million transactions) = 0.74MB
Swift(international) wires(5 Billion transactions) = 24.7MB
ACH(19 Billion transactions) = 93.9MB
Now lets look at the ACH transactions with DASH. 93.9MB X 576 blocks/day so daily add to the blockchain is 54GB.

We need to find a way to cram more transactions in less data, cutting out old transactions, or doing something Dashingly smart.

I don't agree with your calculation, but I like the all inclusive idea of capturing every transaction on the planet.
so using 1k as the average transaction size and extending:-

Total transaction size per day = [(.150 + 5 +19)*10^9] * 1024 =24.7 terrabytes per day !

if 576 blocks per day, that would mean every block size = 24.7 * (10^12) /576 = 42.9 gigabytes per block required !!

assuming 1 block= 1MB,
42.9 GB / 0.001 GB =42882

scalability factor required for entire transactions= 42882 times size reduction !!!
(and with 1 as yet unpruned transaction = 1024 / 42882 = 0.024 Bytes long)

It could be possible if a secondary master records database was created, the same addresses were used, scrubbing the empty addresses and with a limited number of new replacement addresses ? ...

I see what you did there. Totaled up the bank and wire transactions.  Actually, those numbers were based on yearly transactions.  That's about 365x too much.  On the other hand this is probably pretty close for all point of sale transactions when you include credit cards, cash, etc.

I agree, there needs to be a scrubbing done.  Maybe the standard blockchain includes only latest transactions.  So basically, when you update your client it deletes the old stuff as it downloads the new stuff.  There would need to be some way to store old data to get clients updated, so maybe the masternodes store the monster blockchain and then compress it with the Evan Almighty Algorithm.

[mjsrs]

nice TED about dark net and privacy

http://www.ted.com/talks/jamie_bartlett_how_the_mysterious_dark_net_is_going_mainstream

unfortunately the talker misses Dash

[AizenSou]

We really do have an end-to-end solution to all problems within crypto now. I'm working on a 50+ page whitepaper that details the rest of the solution, I'm quite excited about it  

I'm waiting for Evan to publish his 50+ page whitepaper... It sounds like he has solved the block size problem, and many others haunting crypto at the moment :-)

Just keep buying DASH and waiting for the news.

[Jestah]

nice TED about dark net and privacy

http://www.ted.com/talks/jamie_bartlett_how_the_mysterious_dark_net_is_going_mainstream

unfortunately the talker misses Dash

It's totally not surprising.  There has been zero mainstream marketing.  Zero DN marketing. How would anyone outside of our micro crypto world ever know about it?

[TanteStefana2]

nice TED about dark net and privacy

http://www.ted.com/talks/jamie_bartlett_how_the_mysterious_dark_net_is_going_mainstream

unfortunately the talker misses Dash

It's totally not surprising.  There has been zero mainstream marketing.  Zero DN marketing. How would anyone outside of our micro crypto world ever know about it?

I agree, and I'm frustrated as well.  But on the happy side, the marketing video is almost ready, and it will be sent out to news outlets as I understand it with a press release.  And of course, then it will be part of the youtube channel.  The guys have even made a multi language sound track!  I can't wait!  It's so exciting!

And now we have a budget for marketing, so hopefully the next push won't be far behind.

[tungfa]

Masternode “Start” Announcement/Reminder v12 !

Please do NOT use  "masternode start" or "masternode start-many/alias" commands anymore to bump your node !!
This worked before, but now since v12 this will affect your node position quite the opposite way now. Use them only when you actually start new MN or MN that dropped out of list. You should not use this command if there is no additional announcement and/or no protocol bump mentioned because in usual cases MN will start automatically on daemon restart.

Some simple notes on what to do in case of some issues:
- If your daemon died but MN still in the list - just restart the daemon and check in next 5-10 minutes if it's still in the list.
- If your daemon died and MN dropped from the list on some site - that doesn't really mean 100% that it dropped on the whole network, could still be visible in some parts of network for another few minutes so just restart demon again and see if it reappear in next 5-10 minutes there. If not - no luck then, everyone kicked you out of list and you have to use "masternode start" or "masternode start-many/alias" and start from the end of payment queue again.

we have many many people asking the same question:
why are my MN's not getting paid since 7-10 days ?
Well, everybody made the same mistake as described above.
only use "start' when actually needed

Tx Udjin

[Jestah]

Our old friend:

Child Harold • 3 hours ago
This is most dissatisfying and I am unhappy with the way this has been handled. That you are unable to resolve your differences is remarkable to me and what the hell is ursium btw? This release should have come from the Team /Stephan simultaneouly. Stephan may well have done a lot for Ethereum but he's also made substantial profits which one presumes he'll inject into his next project. Good luck I guess even though at this time I really dont mean it. If the Ethereum community is so wonderful why not stick around? And if you had these issues (presumably related to some of the early investment) why did you not step down sooner?

Poor show, a bientôt.