I think I saw on the coins specs that the block reward is now halved at 2 years instead of 1
source? What is DarkCoin? DarkCoin is a lite version of Bitcoin using X11 as a proof-of-work algorithm. Super secure hashing algorithm: 11 rounds of scientific hashing functions (blake, bmw, groestl, jh, keccak, skein, luffa, cubehash, shavite, simd, echo) Block reward is controlled by moore's law: (11111 / (((Difficulty+51)/6) ^ 2)) CPU only mining Block generation: 2.5 minutes Difficulty Retargets every 576 blocks 84 Million Coins Max Block reward halving every 2 yearsEncrypted transaction network: Work In Progress Anonymous blockchain using coinjoin technology: Work In Progress Actually there is no more halving at all. After 5000 difficulty the block reward hits the minimum of 5 coins per block and that is supposed to be the reward until all 84 000000 are mined. Which @ 1 million a year will take a long time. In 10 years there will just a hit more coins than what bitcoin has now, so how about calming down for everyone who is saying it's not scarce anymore? This is accurate. The halving was a mistake, for the currency to work there needs to be some inflation, even if it's really low. I don't want the mining to collapse on itself and it won't happen with a reward of 5. Also, I believe the curving that I'm using is less shocking to the ecosystem than the halving that other currencies use, it happens much slower and has the same overall effect on scarcity. |
|
|
|
Testing went fantastic. We all decided we're ready for public beta on mainnet, so I'll be releasing executables some time this weekend!
Are there any foreseeable dangers for the mainnet by the beta and darksend going live? It's pretty safe, but I'll make a very detailed post about the dangers before I post the executables that work with mainnet. |
|
|
|
|
Testing went fantastic. We all decided we're ready for public beta on mainnet, so I'll be releasing executables some time this weekend!
|
|
|
|
|
Testing went fantastic. I'm going to shut it down and I'll make some executables for mainnet, maybe tomorrow/sunday.
Thanks for the help everyone!
|
|
|
|
Cheers eduffield, I noticed the txt was crossed out yesterday after the reschedule. And it was edited again, but the post date still says the 27th. Is the test happening again today? (28th?) Yep, you're correct. |
|
|
|
Ok, will be there  BTW, do you know what went wrong? Yes, someone from a previous test did not clear their block chain so it caused a fork in the testnet. I added a checkpoint into the source so the clients won't be tricked again. |
|
|
|
Yes, this is going to have to be assigned to eduffield as soon as darksend is completed,  I think it'll take him a week or two.  I think I'd rather have the main DEV out of jail. Not sure about you guys? The Darkroad marketplace will pop up soon enough. I wouldn't touch that with a ten foot stick |
|
|
|
Here it is! https://en.bitcoin.it/wiki/Securing_your_walletA pretty paranoid piece, so perhaps incorrect, however if you look down to the section that says Securing the Bitcoin-QT or bitcoind wallet, you'll see what I read. Perhaps I'm understanding it wrongly. Or perhaps it's wrong? Please, smart guys and gals out there, check it out and confirm or clarify for us Thanks
So when a backup is first created, it has all of your old keys plus 100 unused keys. After sending a transaction, it has 99 unused keys. After a total of 100 new-key actions, you will start using keys that are not in your backup. Since the backup does not have the private keys necessary for authorizing spends of these coins, restoring from the old backup will cause you to lose Bitcoins. I hate to keep bringing this up, but could eduffield, CHAOSiTEC , InternetApe or someone tell me if this is true or not? Thanks so much! It's my understanding that change addresses usually use the unused pool addresses, then every time you use 100 it will make another new 100 addresses to use. So you technically only need to backup whenever that mass generation happens. This about sums it up: The wallet contains a pool of queued keys. By default there are 100 keys in the key pool. The size of the pool is configurable using the "-keypool" command line argument. When you need an address for whatever reason (send, “new address”, generation, etc.), the key is not actually generated freshly, but taken from this pool. A brand new address is generated to fill the pool back to 100. So when a backup is first created, it has all of your old keys plus 100 unused keys. After sending a transaction, it has 99 unused keys. After a total of 100 new-key actions, you will start using keys that are not in your backup. Since the backup does not have the private keys necessary for authorizing spends of these coins, restoring from the old backup will cause you to lose Bitcoins |
|
|
|
Here it is! https://en.bitcoin.it/wiki/Securing_your_walletA pretty paranoid piece, so perhaps incorrect, however if you look down to the section that says Securing the Bitcoin-QT or bitcoind wallet, you'll see what I read. Perhaps I'm understanding it wrongly. Or perhaps it's wrong? Please, smart guys and gals out there, check it out and confirm or clarify for us Thanks
So when a backup is first created, it has all of your old keys plus 100 unused keys. After sending a transaction, it has 99 unused keys. After a total of 100 new-key actions, you will start using keys that are not in your backup. Since the backup does not have the private keys necessary for authorizing spends of these coins, restoring from the old backup will cause you to lose Bitcoins. I hate to keep bringing this up, but could eduffield, CHAOSiTEC , InternetApe or someone tell me if this is true or not? Thanks so much! It's my understanding that change addresses usually use the unused pool addresses, then every time you use 100 it will make another new 100 addresses to use. So you technically only need to backup whenever that mass generation happens. |
|
|
|
Has anybody managed to compile the most recent elmad / darkcoin-cpuminer-1.3-avx-aes version for Windows 64-bit? I have been trying with MinGW and can't figure it out. I would be very grateful if someone more skilled at this than I could share a compiled binary.
Thanks,
Mike
I was also looking for a windows binary. So would be really great if someone could build it. And omg, on the front page is still the very old xcoin windows miner with like 25/50 detection rate in virustotal and like no performance compared to drk-1.2c binary... devs do really not like windows it seems Can someone give me a better binary to link to? I must have missed that one |
|
|
|
Just read the announcement on the main thread, super excited to be part of this next test tomorrow.
Just one concern, there isn't any chance I could mess up my main Darkcoin wallet / blockchain etc is there? I don't want to loose my coins of course lol.
I'll be running Windows, do we add
addnode=23.22.165.148
testnet=1
debug=1
to the config file in \AppData\Roaming\DarkCoin\ ? or another folder?
Thanks.
Nope, you won't lose your coins. However, you should have your wallet.dat backed up somewhere. Not really for the test, but just because it's a good idea. You'll add those lines to Darkcoin\darkcoin.conf, then when you start the program it will build out Darkcoin\testnet3 and operate in that folder |
|
|
|
We're happy to announce development on alpha v3 has completed, we have a really improved, fully functional version of DarkSend for you all to test. The next test will be tomorrow at 7PM EST. Just like last time, if you want to test join us in #darkcoin-test on freenode, we'll be sending money around and testing out the implementation. Updates include: - Transactions for 0.00 fixed - "Not enough funds" problems fixed - Completely 100% anonymous transactions implemented using Darksend denomination pooling - Multiple transactions per pooling support This version is WORLDS ahead of the last one, I can't wait to show everyone. For download links and other information checkout: https://bitcointalk.org/index.php?topic=467857.0 Very nice, too bad that it's the middle of the night for me. Are there still any known bugs lurking in the implementation? I wonder if it's possible to do beta release if there are no bugs found during the test of alpha v3. That's a possibility. It seems pretty stable to me. |
|
|
|
We're happy to announce development on alpha v3 has completed, we have a really improved, fully functional version of DarkSend for you all to test. The next test will be tomorrow at 9PM EST. Just like last time, if you want to test join us in #darkcoin-test on freenode, we'll be sending money around and testing out the implementation. Updates include: - Transactions for 0.00 fixed - "Not enough funds" problems fixed - Completely 100% anonymous transactions implemented using Darksend denomination pooling - Multiple transactions per pooling support This version is WORLDS ahead of the last one, I can't wait to show everyone. For download links and other information checkout: https://bitcointalk.org/index.php?topic=467857.0 The download links are not working. They'll work at Tomorrow @ 9PM EST |
|
|
|
|
Show Posts
