Evan Duffield
Aug 23, 2017 · 1 min read

You’re right, there’s a lot going on in the process of updating Dash to support millions of users. First, block propagation is usually an issue in peer-to-peer currencies, with Dash, we have a highly connected second tier of computers that are attached to fiber, usually. This means blocks propagate pretty quickly along that path, faster than they normally would. Upgrading that is a pretty straightforward process and we can also upgrade the processors to something like a xeon, which would get us very far in terms of scalability. The next bottleneck as far as I can tell is the cryptographic signatures for the block transactions and verifying them as they come in. I don’t think the blocksize limitation is 99% constrained by the network, that seems to be in error, unless you have data to support that position? I would be curious to see something like that. From what I done in development of Dash in the lower levels of the Bitcoin protocol, it seems that most of the bottle neck comes from the cryptography, then the thread-locking code (which is cpu-core locked at the moment), then the network throughput, then probably write speeds of the disk. Optimally we’d like to eliminate all of the bottlenecks as we find them and reduce it to a memory-bound program.

)

    Evan Duffield

    Written by

    Dash Labs // Dash Founder