Hello Guys,
does anybody knows when block is halfing in dark coin?
Thanks
It's a 7% per year decline and it should happen January next year. |
|
|
|
Always so much talk about a new logo. Great to see involvement.
I was under the impression that Evan and InternetApe has already picked the logo / graphic already? (the one currently being used) I'd hate to see people waste their time.
This thread is pretty long, so correct me if I'm wrong.
We did a poll and asked if we should design a new logo and the community was pretty split, so we decided to give the community more options to pick from. It seems like it was a good idea, the new stuff is really high quality. |
|
|
|
Could anyone that runs an exchange/pool/other tool fill out the following form? http://goo.gl/mSYVhX
|
|
|
|
Wow, that's so nice to look at. It's soo simple too |
|
|
|
Not to pick nits, but how long ago was the name changed from XCoin to DarkCoin? The tray icon is still XCoin... How long would it take to clear that bit of low-hanging fruit? Just built the latest and that still give me a sad.
I was unaware of that. I'll fix it, thanks. |
|
|
|
2014-04-03 19:02:48 SetBestChain: new best=0000000000048df5a5abb1c3b8f58ab4f7415240f0ba253c51ba59a46fd98d10 height=34139 log2_work=53.845982 tx=140299 date=2014-03-15 19:28:04 progress=0.887914
2014-04-03 19:02:48 ProcessBlock: ACCEPTED
2014-04-03 19:02:48 received block 0000000000007cc9f8fa630d36b57820f83ab3797c6f2e6656ab839237bfebf6
2014-04-03 19:02:48 ProcessBlock: ORPHAN BLOCK, prev=0000000000c96993de760afea8978cc0da0f9b9a65aa20eb10382c6a9da8ba8d
2014-04-03 19:02:48 received block 00000000001369658c1e06834fb6f5e7ec892d44ffc765f81e7e36acad39a4b6
2014-04-03 19:02:48 ProcessBlock: ORPHAN BLOCK, prev=000000000098b29655459f1cbfd05d8736a27d0a804eb72736af0a6ee60ea891
2014-04-03 19:02:48 received block 00000000007dda6b77dc0575cca14aecdc36cbdb07afe364d55e8def556304c2
2014-04-03 19:02:48 ERROR: AcceptBlock() : incorrect proof of work
2014-04-03 19:02:48 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-04-03 19:02:48 Misbehaving: 64bitserverip:9999 (0 -> 100) DISCONNECTING
{
"blocks" : 34139,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 278.98827638,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 8076638933,
"pooledtx" : 0,
"testnet" : false
}
It's fine, I need to enable the 32bit support. The DGW2 difficulties are now compatible, but the client still doesn't like V1 numbers. Then this might be work !! I have downloded blocks and chainstate folder from 64bit. Now 32bit has 2014-04-03 19:36:53 Committing 19 changed transactions to coin database...
2014-04-03 19:36:53 SetBestChain: new best=000000000036d972c558575cba3f7a96aa72301122f0825036578553c864a5fa height=45035 log2_work=54.936633 tx=185039 date=2014-04-03 19:36:49 progress=1.000000
2014-04-03 19:36:53 ProcessBlock: ACCEPTED
I removed download link for sure. Hah, yeah that would work  |
|
|
|
2014-04-03 19:02:48 SetBestChain: new best=0000000000048df5a5abb1c3b8f58ab4f7415240f0ba253c51ba59a46fd98d10 height=34139 log2_work=53.845982 tx=140299 date=2014-03-15 19:28:04 progress=0.887914
2014-04-03 19:02:48 ProcessBlock: ACCEPTED
2014-04-03 19:02:48 received block 0000000000007cc9f8fa630d36b57820f83ab3797c6f2e6656ab839237bfebf6
2014-04-03 19:02:48 ProcessBlock: ORPHAN BLOCK, prev=0000000000c96993de760afea8978cc0da0f9b9a65aa20eb10382c6a9da8ba8d
2014-04-03 19:02:48 received block 00000000001369658c1e06834fb6f5e7ec892d44ffc765f81e7e36acad39a4b6
2014-04-03 19:02:48 ProcessBlock: ORPHAN BLOCK, prev=000000000098b29655459f1cbfd05d8736a27d0a804eb72736af0a6ee60ea891
2014-04-03 19:02:48 received block 00000000007dda6b77dc0575cca14aecdc36cbdb07afe364d55e8def556304c2
2014-04-03 19:02:48 ERROR: AcceptBlock() : incorrect proof of work
2014-04-03 19:02:48 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-04-03 19:02:48 Misbehaving: 64bitserverip:9999 (0 -> 100) DISCONNECTING
{
"blocks" : 34139,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 278.98827638,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 8076638933,
"pooledtx" : 0,
"testnet" : false
}
It's fine, I need to enable the 32bit support. The DGW2 difficulties are now compatible, but the client still doesn't like V1 numbers. |
|
|
|
Beta version (v0.10.0.0-unk-beta) doesn't sync after hard fork. Last block is 44999.  Opps, beta doesn't have DGW2 yet. I'll upload a fix |
|
|
|
current block number is 45000
Hard fork : 0 blocks , 0 min left
current block number is 45001
Hard fork : -1 blocks , -2.5 min left
!!
Awesome, now 32bit wallets should be able to sync (After I update the exe again) |
|
|
|
If we have the limit at 250DRK, the person with 1000DRK will just have four "tickets" instead of 1. So the outcome is the same really, with the same security too.
The only difference between 250DRK and 1000DRK is that we'll end up with lower end master nodes. I think we need only people that really understand security, ddos protection and how to run a service with 99.9999% uptime. These nodes are going to be the life blood of the whole network, so those things are highly valuable.
I agree in principle, I'm just not sure I understand how a higher cost of entry ensures those things. A higher cost of investment and a lot of money as risk will ensure the person at least understands what he's doing. Later on I envision we'll have master node pools where you can buy shares and receive a percentage of the payout. This will offer smaller investors the same investment, with someone else managing the node that can protect it. |
|
|
|
As i understood the cost to run a masternode will be 1000 DRK .
1000 DRK is way too high, i understand you ambition but it would eventually prevent a healthy amount of masternodes.
I would host masternodes worth 2000 DRK, i even have the option to provide different IP geo locations, if one masternode costs 1000 DRK to run i can only host two with my budget. NSA can host thousands!!!!
Please consider that there indeed should be a monetary hurdle but it should be considered really, really carefully. Because probably the advantages outweight the disadvantages from lowering the monetary hurdle.
I really want to urge you to double think about that! 150 - 500 DRK should be much enough to host a masternode!
Best Regards,
If we have the limit at 250DRK, the person with 1000DRK will just have four "tickets" instead of 1. So the outcome is the same really, with the same security too. The only difference between 250DRK and 1000DRK is that we'll end up with lower end master nodes. I think we need only people that really understand security, ddos protection and how to run a service with 99.9999% uptime. These nodes are going to be the life blood of the whole network, so those things are highly valuable. |
|
|
|
back to a master node misbehaving, there is a problem here.
A human will not know if they are hosting a master node as they shut off their machine for whatever reason, therefore we have a backup slave node to take over. I would think that the only "punishment" for the master node is that they will not participate in that round's rewards. Otherwise, we can hurt people who are just running their wallets.
I still haven't seen, but may have missed it, can we password protect our wallet while running the nodes? Also, can our balances and identity be inferred from running a node?
So all clients have a full list of the masternodes and they can sort them like: Winner, Runner up, Next runner up, etc So if you can't connect to the first, you'll connect to the second. The one who gets the payment needs to be the one who actually did the work, maybe he could sign the finalized transaction or something. How is this achieved? A hash map? Something like that, when the client starts by propagating a message saying "Hey I'm a capable masternode ,here's my input and sig to prove it and this is where I'd like to be reached" . |
|
|
|
back to a master node misbehaving, there is a problem here.
A human will not know if they are hosting a master node as they shut off their machine for whatever reason, therefore we have a backup slave node to take over. I would think that the only "punishment" for the master node is that they will not participate in that round's rewards. Otherwise, we can hurt people who are just running their wallets.
I still haven't seen, but may have missed it, can we password protect our wallet while running the nodes? Also, can our balances and identity be inferred from running a node?
So all clients have a full list of the masternodes and they can sort them like: Winner, Runner up, Next runner up, etc So if you can't connect to the first, you'll connect to the second. The one who gets the payment needs to be the one who actually did the work, maybe he could sign the finalized transaction or something. |
|
|
|
Expect a lot more coins to implement Dark Gravity Wave KGW --> Needs a fix. Digishield --> Needs a fix https://bitcointalk.org/index.php?topic=552895.msg6034641#msg6034641Too bad it is a BTC bear market going on. Confidence in cryptos might be at an all time low which is hindering Darkcoin as well. I still think Bitcoin rushed too much too soon. Yeah, DGW2 fixes what they're talking about |
|
|
|
As I'm thinking more of it, perhaps the greatest weakness of the system is the requirement to have hundreds of thousands of DRKs online: If a network exploit is found at some point that allows the hacking of the master nodes, then every single node can be emptied of their money and a hacker will end up with something like half a million DRK... wallets and stuff are relatively safe due to the encryption, offline protection etc, but networks have a much weaker reputation: Exchanges, pools, even dice games -as reported above- are getting hacked.
Cryptoland and online money seem to be the hacker's paradise and the DRK master node network will be a multimillion dollar bounty for someone who finds a good exploit for the node daemons.
You're referring to the 1000DRK kept in the hot wallet right? All of the Bitcoin exchanges have began to switch to multisig setups that would require 2 of 3 of the different networks to be breached. I'm sure the same thing will happen for Darkcoin, we just need a good enough setup to protect the money. |
|
|
|
Is there a binary for bitcoind to run as a master node on Linux? Or on Windows will the QT client work as a masternode? I can have 5 master nodes up this evening. I also need to know what exactly belongs in the .conf for this.
That's great, but I still need to write the election code and hard folk the mainnet to enable it. Soon  |
|
|
|
The next stage of DarkSend
The design of Darkcoin is all about economic incentives, I've tried to bake as much of that in as possible. I've been thinking about the reliance on master nodes in our new design for securing the network and I see some room for improvement.
With the current design we will require 1000DRK to operate a master node. That requires you putting 1000DRK in a hotwallet (dangerous) only to collect the collateral fees which won't amount to much.
So what do we want?
- We want as many master nodes as possible (the more nodes the more secure the network)
- We want them to be profitable to run
- We want it to be very expensive investment to operate a master node
So I propose the following solution, each block the last master node will receive 10% of the mining reward (in addition to the reward given to the miner). So for example, if the mining reward was 19DRK the last master node will automatically receive 1.9DRK.
This also has some really great side effects:
- It creates a completely new type of investor that buys DRK and holds it (where as miners create dark coin and sell it for the most part)
- It adds a ton of full nodes to the network
- It creates demand and scarcity, which should provide a nice return for our investors
Also, these payments are completely secure. New blocks with the dividend payment made out to the incorrect master node will be rejected (the whole network knows who won the election).
At the present moment we have a chicken and egg problem. We need master nodes to support darksend and we don't want to go live with 1 or 2 master nodes. To solve this we will implement the election code into the main client, along with the payments to master nodes while DarkSend is still beta.
What type of return will you see?
- If there’s 1 capable master node, you’ll receive all payments 576*(AverageReward/10) per day
Capable Nodes, Daily Reward
1, 1094DRK
2, 547DKR
5, 218DRK
10, 109DRK
20, 54DRK
50, 21DRK
100, 11DRK
As you can see, we’ll quickly reach equilibrium with the price and at the same time this will create buying pressure raising the price more and causing the network to become increasingly secure.
Also, we can build our master node network now in the immediate. Users can buy the darkcoin needed to run one and they will just run the beta client. We'll open source the election code and hard fork to add the payments to master nodes in and our network will be secure by the time we're ready to do a full launch.
I really love the idea, thoughts?
What would happen if I have the same wallet in 2 or 3 computers? I guess they shouldn't all be able to act as a master node but only 1. Yeah, they have the same "ticket" they're entering with. So 1 of them would act as master if selected. |
|
|
|
What happens when max coins is reached?
"We actually never will reach max coins, since the decline is 7% a year, it goes on forever." Up to how many digits is the block reward capable of handling? I mean if it's like 0.0000000000000000000000000000000000000165 DRK block reward and you have to divide that to a further 1000 nodes, and the float variable precision is up to a point that it can't handle it, perhaps it'll simply return a zero. I have no idea by what year we'll reach that number though  Heh, yeah I calculated it and we'll be at about a 2.2 duff (satoshi, saroshi? what did we pick?) in 300+ years. |
|
|
|
My question, I suppose is to do with block rewards diminishing as you approach max coins, while the number of nodes goes up. Smaller rewards are split amongst greater numbers?
Correct |
|
|
|
What happens when max coins is reached?
We actually never will reach max coins, since the decline is 7% a year, it goes on forever. Edit: Actually, it'll take about 350 years. |
|
|
|
|
Show Posts
