mirror of
https://github.com/seigler/dash-website
synced 2025-07-26 23:06:09 +00:00
ad056aa1cb
* Remove style-guide from i18n builds * Remove uncategorized from CN blog posts. * Team images and alt attributes. * Fixing language linkage * Ignore missing or empty alt tags * ignore sass-cache * fix gitignore for sass-cache * fix gitignore for sass-cache * Only show language dropdown if the page is not a post (blog) * New url with site.lang included. * Removed the site.baseurl var from the posts.
48 lines
3.7 KiB
HTML
48 lines
3.7 KiB
HTML
---
|
||
layout: post
|
||
title: Development Update - August 19, 2014
|
||
date: 2014-08-19 15:58:30.000000000 -04:00
|
||
type: post
|
||
published: true
|
||
status: publish
|
||
categories:
|
||
- Development Updates
|
||
tags: []
|
||
meta:
|
||
_edit_last: '1'
|
||
slide_template: default
|
||
truethemes_video_url: ''
|
||
truethemes_external_image_url: ''
|
||
truethemes_slider_shortcode: ''
|
||
truethemes_slider_cu3er: ''
|
||
author:
|
||
login: fernando
|
||
email: gutierrezf@gmail.com
|
||
display_name: Fernando Gutierrez
|
||
first_name: Fernando
|
||
last_name: Gutierrez
|
||
---
|
||
<h4>Bug squashing and the stability of Darksend</h4>
|
||
<p>During the last week we’ve been squashing bugs in the RC4 client and getting everything as stable as possible. As of the last update, it’s working for nearly everyone and humming along.</p>
|
||
<p>The next 3-6 weeks will be spent creating the RC5 client which will have a few minor updates including some known issues resolved along with a basic gui that shows the current status of Darksend.</p>
|
||
<p>Also, we’ll be working on improving the Darksend source code and getting it ready for other programmers to help out. It needs heavy commenting and some basic refactoring.</p>
|
||
<h4><b>Kristov Atlas and the code/security review</b></h4>
|
||
<p>Kristov is preparing deliverables for both the strength of anonymity and the code security of Darksend. Expect this to be released while work on RC5 is ongoing. Depending on what Kristov has found, this could delay RC5 so that we can fix important issues. As it currently stands, that doesn’t appear to be a concern.</p>
|
||
<h4><b>Enforcement</b></h4>
|
||
<p>Due to the delayed release of RC4, enforcement of masternode payments was not able to be extensively tested. We plan on beginning testing this feature soon. If possible, it will be turned on in mainnet before the launch of RC5.</p>
|
||
<h4><b>Open Sourcing </b></h4>
|
||
<p>RC5 should be solid for open sourcing. We’ll have someone else look the source over, then we’ll be open-sourcing soon after. While this is ongoing, we’ll start work on our next project.</p>
|
||
<h4><b>Utilizing the Masternode network - DarkTor</b></h4>
|
||
<p>One of the future goals is to turn the masternode network into a decentralized business for masternode operators. To do this we’ll add features that improve the privacy of end users and compete with centralized businesses. Our first endeavor into this is to make a completely private tor network within Dash.</p>
|
||
<p>The Dash network will begin to offer anonymous internet access via the masternode network. As a user, all you’ll have to do is pay a fee for 24 hours of access. This fee will be paid to a masternode in much the same way the masternode fees are paid, using a deterministic algorithm for distributing the payments evenly across the whole network.</p>
|
||
<p>There’s a few benefits to running a private tor network through Dash.</p>
|
||
<ul>
|
||
<li>Sybil resistant - Due to the cost of obtaining masternodes, it will be very difficult for any one person to view all traffic.</li>
|
||
<li>Anonymous Payments - Users can pay anonymously for the service</li>
|
||
<li>Private Network - Our tor network will be internal to darkcoin only. All traffic will be paid traffic, so the cost of running the service should be profitable for the masternode operators.</li>
|
||
<li>Faster than tor - Tor has historically been very slow. This will be a lean version, that has much higher throughput.</li>
|
||
</ul>
|
||
<p>As for the cost of the service we’re thinking $0.50 per day or something to that effect.</p>
|
||
<p>We’re still working on the details how this will function and this isn’t a feature that we’re absolutely set on. We’re very interested to get the community’s response to see if it’s viable .</p>
|
||
<h4><b>Other Future Ideas</b></h4>
|
||
<p>Maybe after it’s opensource other developers can help with some of these ideas:</p>
|