• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

Evolution - Dashdrive Discussion

Hey Guys

Can I please ask that we keep VPS prices in mind when the main developers decide on harddrive space requirements. I am only here at Dash because I wanted to help the Bitcoin XT crowd, and then found out how much a VPS with a 60GB/80GB harddisk would cost. I realised I would run at a massive loss if I ran a node. Not all ISP connections in the world are great, and not all people can run their computers 24h a day.

For me a masternode is never about making a profit. But I love that it pays for itself. That's the beauty.
It is possible to buy a Xeon-D machine and run it with a 1Gbps fiber at home to host 16+ MNs with 6~8 HDDs. It is really low cost. If someone is willing to pay me some DASH, I could write a guide on how to do this. Give me an offer and I will write it up if the offer is right.
Last edited by a moderator:
I have been thinking some more about DashDrive.

As I have explained before, implementing a sharded consistent storage on top of trustless (master)nodes is hard. But we already have a well-known technology for this: The blockchain! Therefore, I think each masternode shard should have its own blockchain with transactions storing the contents of that shard of the DashDrive. This makes sure that writes to DashDrive are consistent, persistent and durable. Whenever a masternode is chosen to collect the masternode fee of the main chain, it broadcasts a transaction that roots the head of the blockchain of its shard into the main chain. This is a requirement to collect the masternode fee.

The masternodes need a incentive to actually add transactions to the side chain. Therefore, as on the main chain, storing data (transaction) in the DashDrive blockchain requires a fee. Mining on the sharded blockchains is done in pure PoS using the masternode's stake. The only block reward on the side chains are the storage fees which get transferred to main chain with the rooting transaction. A unfortunate side effect of this is that main chain miners will have to verify the side-chain transactions to make sure they are valid (or some selected masternode quorum could do that).

There is still the problem that someone could take over a majority of masternodes in a shard. But because the side chains are auditable and rooted in the main chain this is note so much of a problem:
- Even if a majority of the masternodes denies service, the other masternodes in the shard will still keep serving the shard's content and root new transactions. Also non-masternodes can keep track of side chains increasing the storage redundancy.
- Because side chains are rooted in the main chain it is not possible to alter the history of the side chain beyond the last rooted block even when owning a majority of the side chain masternodes.
So, the worst thing that could happen is that someone owning all masternodes of a side chain could refuse to accept new transactions. This per se does not have any benefit to the attacker unless he manages to force higher storage fees for this shard. This can be counteracted by making it easy to move one's data from one shard to another.

greensheep I think that is Evan's current strategy, i.e. a second blockchain for DashDrive data. And just for the important data like user account data and communication / relationships between accounts, basically anything Evolution needs to function internally. DashDrive will be a new core feature though not part of the Evolution side me and the other web team members are working on.