Evan, check your PMs and sign onto Dashtalk!
Fixed! It wasn't a fork, this was due to something with masternodes and multisig donations. The reference node is just going to ignore those, so we shouldn't have issues anymore. We just got 3 blocks in the last couple of minutes, everything is ok. |
|
|
|
************ Dash Release Update : 11.2.17 ************************ - Fixed the "locking up" issue that would cause masternodes to go offline and general instability - Masternode list changes - Udjin - Better icon images - Crowning - Improved Chinese Translation https://www.dashpay.io/downloads/ |
|
|
|
|
We're super low on hashpower for testnet, anyone have any they can spare for a few days?
P2Pool : 103.13.228.168:17903
|
|
|
|
the new windows wallet download installer is not working for me. it dl's but the file is 0 bytes and does nothing when you click it. i'm dl the zip which is 85 megs.
Should be fixed now. |
|
|
|
I thought that according to Duffenomics, the masternode count was supposed to decrease with increasing price as people checked out. (i.e. the price of the collateral increases to less collateral is needed). Then increase as price reduces as a stabilising action.
As far as I can see the masternode has increased over the last week by about 100.
I was aiming for ~3000 masternodes by mid 2016 based on an return-on-investment bond model. The masternode networks fundamentals are pretty similar to that of the bond market, ROI being comparable to expected interest rates. Currently the expected interest rate of the network appears to be about 16%, as our fundamentals strengthen I would expect that expected rate to actually fall allowing more masternodes onto the network (if people feel less risk in having a masternode, they'll accept less return). |
|
|
|
So the lead dev has a private key which lets him control all the MasterNodes? Why does he need to control all MasterNodes? In the future, will he be in control or is this just temporary and if so how long will this continue?
No, he does not. There is a private key for engaging the spork but that's it. This allows us to prevent forks for the time being while bugs are getting troubleshooted on mainnet when new features get rolled out. If he chose to for whatever reason, could he crash/stop/impede the DRK network with this "masterkey"? What exactly does this key allow him to do? He is refering to the Spork, is a message that is send out to the network so that you can activate, deactivate a hard fork. It works similar to the way alerts work in BTC. Is probably one of the coolest things on DASH/DRK and he chooses to troll about it. It poses absolutely no risk and gives no power, it just allows a mature network to innovate and do hard fork after hard fork in the name of progress, like DRK has been doing to implement its features. From the OP: Multi-Phased Fork Implementation (aka the “Spork”) In response to unforeseen issues with the rollout of RC3, the Darkcoin development team created a mechanism by which updated code is released to the network, but not immediately made active (or “enforced”). Communication is sent out to users informing them of the change and the need for them to update their clients. Those who update their clients run the new code, but in the event of errors occurring with that new code, the client’s blocks are not rejected by the network and unintended forks are avoided. Data about the error can then be collected and forwarded to the development team. Once the development team is satisfied with the new code’s stability in the mainnet environment - and once acceptable network consensus is attained - enforcement of the updated code can be activated remotely. Should problems arise, the code can be deactivated in the same manner, without the need for a network-wide rollback or client update. This innovation allows for far smoother transitions than in the traditional hard fork paradigm, as well as the collection of test data in the live network environment. We set out with the intention of calling this method of updating the “Soft Fork”, but the Darkcoin community quickly dubbed it the “Spork” and the name seems to have stuck. Thanks for the answer. With other coins, should the community (read miners and masternodes) choose not to accept whatever new aspect the developer(s) are trying to implement in the existing coins code they could simply not upgrade to the latest version put out by developers and run the current version of the code as they have done since the last update they agreed to apply. This would allow the network to continue to operate normally although perhaps temporarily without the support of the developers since they could not reach a consensus with the miners. I am understanding from your answer, if I understood correctly, that this Spork would in no way provide the DRK dev with the ability of subverting the miners ability to operate as is without accepting and applying the new code? Basically if the DRK dev tried to implement a code change which was greatly unpopular among the community, miners, etc. this Sprok could not be used in any way to force everyone (miners, masternodes) to accept these unpopular changes? Thanks in advance. Well, the same logic applies as in the Bitcoin example you made: If the miners don't like the new version, they won't install it, and thus there will be nothing for the key to activate But this private key/backdoor/troubleshooting tool is already imbeded in the DRK architecture. I'm trying to understand this. Could you please provide a binary answer to my last question? It's exactly the same as the Bitcoin network, it's like the developers adding a hardfork, the miners must support it. The only difference is it can be reversed back to the prior way the code was before the hardfork without an update. There's no magic key that allows debugging or anything like you're saying. |
|
|
|
The revolution is starting....  YEEEEEEESSSSSSSSSSS !!!!!  Cool article. I love how Evan embarrasses himself by saying you have to wait an hour for a bitcoin transaction. I guess it's much better soundbyte than saying you don't have to wait 10 minutes  I have regularly experienced 1 hour + confirms on Bitcoin so it's completely accurate. Once it took 1 hour 32 minutes for 6 confirms. I don't think I've ever had 10 min for even 3 confirmations. But I have experienced around 15 minutes for 3. So you take an extreme example and spin it to your advantage. Definitely sounds like the kind of integrity we can expect from your dear leader. No one waits 6 confirmations anymore. Even exchanges make your funds available after only 1 confirmation. Rubbish! Which exchange allows you full access to your BTC on one confirmation? Certainly not Bitfinex, Cryptsy, Poloniex, Bittrex, Bitstamp or BTC-e. So where, who, what? I have to wait for about an hour for 6 confirms regularly so quoting an hour for BTC is completely valid. The BS just pours unrestrained out of your mouth Adam. Out of the hundreds of Bitcoin transactions I have performed, I have never, NEVER had to wait for anything even close to one hour in order to be granted full access to my funds after confirmation. Well, I was misquoted. The idea is when you have a 4 second IX confirmation, that's equal to about an hour of mining on the Bitcoin network. Statistically IX is very secure after it confirms. |
|
|
|
Optional Donations of Masternode Income
Udjin and I just wrote an extension that allows the masternode network operators to voluntarily sponsor initiatives. This is a super powerful feature, you can specify that a percentage of your earnings will be redirected to any other address. I imagine people will lobby for an initiative, then they will post an address in the forums, if masternode operators supports it, they could donate 30% of their income (or any other amount). Examples include: - Sponsoring an advertising campaign - Sponsoring development - Donating to the Darkcoin Foundation's address Another benefit of utilizing the protocol for something like this is, when used a percentage of payments will bypass you, creating no taxation (you never controlled the money at all). https://github.com/darkcoin/darkcoin/commit/70164b2d4c507669aea0043ccde19226f49aaabd* This is 100% voluntary, we'll never require donations. This line here is just for testing and has already been removed: https://github.com/darkcoin/darkcoin/commit/70164b2d4c507669aea0043ccde19226f49aaabd#diff-345a95f756731b98ecccf4a05e6bd4e2R113
|
|
|
|
|
Show Posts
