Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 1886. (Read 9723748 times)

Ninja:
 " Total Masternodes: 3009 = 3009 actives + 0 inactives [3005 unique IPs] (Last refresh: Thu Sep 03 2015 00.16.20)
Estimated daily payout for an active node (blocks with MN payments last 24h: 100%): 1437.4282 DASH/day (Last Refreshed: Thu Sep 03 2015 00.16.22 "

Ninja??

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 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

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 :-)

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.

 The Tao is strong with this one 

"If something is not in our Archives, it does not exist." 

 I think, not sure, the Bitcoinwisdom webdev went AWOL. Since DRK changed to Dash, most API got changed and never updated, that's why the old links still exist, but are simply stalled.

 It's a pretty damn cool website IMHO, the amount of functionality is simply amazing.

 I only recently started using tradingview.com and I am in love. Also really starting to "get" chart analysis more deeply, so it's kind of like my new pass-time. Learning a few oscillators, indicator and triggers, I developed my very own strategy that is working pretty fine so far.

 Anyway, I digress...

I dunno. The rotting sheep carcass on the right is bound to have a resonant cavity in there somewhere.

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.

https://bitinfocharts.com/comparison/size-btc-dash.html#log

IMO, the exciting aspect of Dash in the context of scaleability is the prospect (alluded to earlier in the year) of implementing the 2-tier efficiency algo which identifies and excludes a huge amount of redundancy from the network data.

When I first saw this discussed it immediately struck me as being similar to the type of optimisation used in finite element analysis, where the optimised theoretical processing required to get the model from one state to the next can save over 90% of the computation effort due to simple elimination of redundancy. The beauty of this approach is that it's not just a practical optimisation but a theoretical one as well - in other words it's theoretically proven to work before you even write a line of code.

This is one of the many technical challenges that Dash is up to addressing due to its 2-tier network algo that can resonate at multiple solution states where others are about as resonant as a dead sheep.

There you go. Thats today's philosophical ramblings of my chest  (for now).

Could be a mega day trade in the offing, suggest you park everything into gov paper and set your buys just above Otoh at $2.00000001 

Out of interest, where are you seeing the blocksizes ?

P.S. Don't you think Dash should pursue the type of block explorer functionalities that blockchain.info has ? I think they're fantastic - maps, flow diagrams etc. It's the 'window' on the currency and what makes it look like an immense, professional worldwide phenomenon.

This type of stuff:

https://blockchain.info/tree/90920379   (Click on the orange dot - I think this type of stuff is awsome).

https://blockchain.info/tx/2cc1441b14e6a30b288a50d175f5498f2938d4aedb04168f80f543ea504295be

https://blockchain.info/inv/2cc1441b14e6a30b288a50d175f5498f2938d4aedb04168f80f543ea504295be

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)

Fine for me, I can mine, have 10 windows open,watch a video and open and close the wallet without any hanging,
not many wallets I can do that with either, shows how lite the client is.

i dont know if this is hapening to you, but when i open my wallet... it consume 95% of my internet while Syncronizing additional data... i cannot open any websites, my mining stop to work... when i turn off wallet... internet is perfect

you need to setup smaller bandwidth while doing this...

I'm not a programmer but it looks simple to write a software which will check all blocks from the first til' now if they contain only transactions between empty addresses and compare their sum size to the blockchain size.

I asked the Dev how much space could be saved from 'pruning', and he said had no idea.
I suppose it depends how much spam and dead transactions there are, probably quite a lot, eh.

A(0) > B(0) > C(1)

If A sends to B his only 1 DASH and then B sends to C his only 1 DASH, who needs the block that contains transaction A > B? NSA?
If the B > C transaction is confirmed already who needs to verify the A > B transaction? No one.

If I accept cash I don't care who gave it to my client, right?

We should create, if it's possible, a different dynamic type of blockchain which deletes such old useless blocks (with transactions between empty addresses). This will reduce the blockhain size.