Development Update - August 19, 2014

[kryptofoo]

RC5: What happened to summary blocks to prevent blockchain bloat from all the denom transactions? Is this not an issue any more or just tabled for now. I havent heard any more about it but detractors are sure to bring this up at some point.

 

[David]

Isn't Ethereum created by the same guys who were previously involved in Mastercoin and MadeSafe scams? I have a feeling that, Ethereum folks have a habit of taking the money and not finishing the job or making your investment worthless.

Nope, a quick Google search will reveal that they are not the same people. MSAFE for instance is Scottish.

 

[Light]

Nope, a quick Google search will reveal that they are not the same people. MSAFE for instance is Scottish.

well, obviously you are not gonna find the links between these people on a 'quick Google search". Anyway, i don't wanna go into details, plus this is Darkcoin forum

 

[fernando]

Is there any press release & contacting wired, coinbase etc. in plan before the news about DarkTor gets too old?

DarkTor is just an idea still open for discussion about how to do it. I think that media will only take interest once things are more advanced.

 

[David]

well, obviously you are not gonna find the links between these people on a 'quick Google search". Anyway, i don't wanna go into details, plus this is Darkcoin forum

Crypto is an extremely small community, especially alt-crypto. I'm sure you could find links between just about anyone =)

But no, the principals of each project are different.

 

[foulowl]

Oh man DarkTor sounds too good to be true. But I am definitely going to keep my hopes up. This is exciting news. Although the name is lame, I think we can do better than darktor. Keep up the great dev team!

 

[ourlink]

DarkFlash.... I just wanted to be the first to coin the term!

 

[yidakee]

I like DarkNet ... reminds me of old late 80's geek movie stuff

 

[moli]

It seems so many people still don't know Evan posted a new update on bitcointalk last night... For those who aren't aware, here's the link:

https://bitcointalk.org/index.php?topic=421615.msg8476904#msg8476904

****** PLEASE UPDATE TO v9.12.32 (Stable) OR 10.12.32 (RC) *******

Due to the upgrade to a larger keypool in RC4, some users have reported slow client / lockups and in rare cases data corruption.
This only effects encrypted wallets and we have not seen this issue on freshly made wallets with the new keypool size at all.
If you're running RC4 with an encrypted wallet please migrate your funds to a new wallet running 10.12.32.
This doesn't effect the stable client at all (v0.9).

BIP32 (deterministic wallets based on seed phrases) would be really nice in this case because as long as you have the phrase,
restoring every possible key is as simple as restoring the wallet from the seed phrase.

This update is not mandatory for masternode operators

- Added a darksend overview box showing some generic information
- Display n/a in coincontrol for negative numbers
- force users to update to wallet version 60001 when they have an encrypted wallet

Source: Compile if you are running a pool, exchange, etc.

https://github.com/darkcoinproject/darkcoin

9.12.32 (Stable) Binaries: Does not include Darksend

Windows.exe: https://raw.githubusercontent.com/d...in-binaries/master/darkcoin-0.9.12.32-win.zip
Windows installer: https://raw.githubusercontent.com/d...ies/master/darkcoin-0.9.12.32-win32-setup.exe
Mac OSX: https://raw.githubusercontent.com/d...in-binaries/master/darkcoin-0.9.12.32-osx.dmg
Linux: https://raw.githubusercontent.com/d...naries/master/darkcoin-0.9.12.32-linux.tar.gz

10.12.32 (RC) Binaries: Includes Darksend - Masternode Operators

Windows .exe: https://raw.githubusercontent.com/d...inaries/master/rc/darkcoin-0.10.12.32-win.zip
Mac OSX: https://raw.githubusercontent.com/d...inaries/master/rc/darkcoin-0.10.12.32-osx.dmg
Linux: https://raw.githubusercontent.com/d...es/master/rc/darkcoin-0.10.12.32-linux.tar.gz

 

[thelonecrouton]

It seems so many people still don't know Evan posted a new update on bitcointalk last night... For those who aren't aware, here's the link:

https://bitcointalk.org/index.php?topic=421615.msg8476904#msg8476904

****** PLEASE UPDATE TO v9.12.32 (Stable) OR 10.12.32 (RC) *******

OP on BCT thread still not updated as well.

Suggest checklist for future updates:
1. Update darkcointalk.io website and links there
2. Update BCT OP
3. Post update announcement here at darkcointalk
4. Post update announcement on BCT
5. reddit, twitter, whatever else...

Poor comms are a frequent complaint, it's easy to fix.

Aircraft pilots have a checklist for a reason!

 

[moli]

OP on BCT thread still not updated as well.

Suggest checklist for future updates:
1. Update darkcointalk.io website and links there
2. Update BCT OP
3. Post update announcement here at darkcointalk
4. Post update announcement on BCT
5. reddit, twitter, whatever else...

Poor comms are a frequent complaint, it's easy to fix.

Aircraft pilots have a checklist for a reason!

What do you mean on 2. and 4.? What is "BCT OP"? I thought the BCT thread is just that's it, a running cluttered site. Is there a locked BCT thread for Darkcoin updates that I'm not aware of? (I'm not on BCT).

 

[thelonecrouton]

What do you mean on 2. and 4.? What is "BCT OP"? I thought the BCT thread is just that's it, a running clustered site. Is there a locked BCT thread for Darkcoin updates that I'm not aware of? (I'm not on BCT).

I meant the Original Post (1st post) in the DRK thread on bitcointalk: https://bitcointalk.org/index.php?topic=421615.0

 

[moli]

I meant the Original Post (1st post) in the DRK thread on bitcointalk: https://bitcointalk.org/index.php?topic=421615.0

Oh.. Thanks for showing that to me. Normally I would look for info on darkcoin.io and DCT, just hate to have to comb through BCT, so much garbage there.

 

[mattmct]

I'm slightly confused about the latest -.32 release and the wallet talk. I use some old wallets for my masternodes, and a live one for my mining, p2pool fees etc.

How exactly do we migrate over? We make a new wallet by deleting the wallet.dat, and then sending it over to the new wallet address? Is this a requirement?

Is there any chance that users could have problems with their old encrypted wallets? (I assume most run encrypted)

 

[flare]

How exactly do we migrate over? We make a new wallet by deleting the wallet.dat, and then sending it over to the new wallet address? Is this a requirement?

RC4 (v0.10.12.x) introduced a 10x larger keypool (100 --> 1000) due to Darksends' high demand on fresh keys. These keys are added to your old wallet.dat during first launch.

Since go live of RC4 there were several reports of users, experiencing high CPU load on these updated wallet.dat when running encrypted. The CPU load is so excessive that the system gets unresponsive and even starts to skip keyboard input. To avoid further problems with this (which could even lead to keys not written back to wallet.dat in rare occasions) we decided to enforce every RC4 user to create their wallet.dat from scratch, with initial keypoolsize of 1000.

The update is mandatory for Darksend+ users - the client will warn you and will go into failsafe mode, disabling Darksend functionality. You can override this, but we discourage you to do so, and you are acting on your own risk!

Is there any chance that users could have problems with their old encrypted wallets? (I assume most run encrypted)

There is a small risk that keys get lost using the old wallet during "unresponsive system" state - therefore we encourage everyone to recreate wallet.dat with v.32

Please remember: you are using experimental software in beta state.

 

[mattmct]

Cheers for the reply flare . So just to clarify, the latest version will do this automatically for us? (recreate the wallet)

I've been using my wallet.dat from my unix server (when was a hot node), then used with the first windows release of RC4 (it asked for password on launch, I clicked cancel, as I didn't want to risk it denominating my 1k coins). Say I was to use it with the newest version, it would add these keys upon launching with the wallet?

update: I would then assume that these new recreated wallets, will only work with the latest 10. 32+ versions of the software? Ie, not backwards compatible?

 

[David]

Forgive me, but I'm *really* confused now.

If I run a masternode, do I need to create a new address in a .32 wallet and move my MN funds to the new wallet and then set up the MN all over again with a new MN privkey?

 

[flare]

Forgive me, but I'm *really* confused now.

If I run a masternode, do I need to create a new address in a .32 wallet and move my MN funds to the new wallet and then set up the MN all over again with a new MN privkey?

As MNs do not use Darksend (masternode=1 disables darksend functionality implicitly), you don't need to create a new wallet.dat

The recreation of wallet.dat is only encouraged/mandatory for Darksend+ users.

 

[David]

As MNs do not use Darksend (masternode=1 disables darksend functionality implicitly), you don't need to create a new wallet.dat

The recreation of wallet.dat is only encouraged/mandatory for Darksend+ users.

Makes sense! Thanks Flare.

 

[moli]

What's the advantage for having 1000 keys vs. the incompatibility issue with the old wallets?

Update: Ok I had a blonde moment there... Understood now, just wish that it could be compatible with the old wallets.

 

[thelonecrouton]

What's the advantage for having 1000 keys vs. the incompatibility issue with the old wallets?

DS+ gets through a lot of keys - burner addresses for each transaction basically.

The advantage of firing up v32 without anything called wallet.dat in your darkcoin directory, copying the new address it will generate upon generating a fresh wallet.dat, then closing v32, starting v31 and sending your balance to the new v32 address is... that you wont suffer a rare but possible case of wallet corruption.

Up to you! :tongue:

 

[moli]

DS+ gets through a lot of keys - burner addresses for each transaction basically.

The advantage of firing up v32 without anything called wallet.dat in your darkcoin directory, copying the new address it will generate upon generating a fresh wallet.dat, then closing v32, starting v31 and sending your balance to the new v32 address is... that you wont suffer a rare but possible case of wallet corruption.

Up to you! :tongue:

Oh I know I have to migrate my coins... Although last night I contemplated on putting all my coins in a brown bag and bury them until Evan finishes his development . lol...
The reason I'm asking this question is pure curiosity of the technology. I might not understand it completely, but i'm still curious.

Edit: And thanks for your answer. You did migrate your coins (in windows wallet) like that and had no problem?

 

[iHeartSmartArt]

Bury all your coins in a brown bag???:what: No real need but you could use

• Paper Wallet: http://paper.darkcoin.io/

paper wallets of 1k drk and keep it in a bank deposit box.

 

[moli]

Bury all your coins in a brown bag???:what: No real need but you could use paper wallets of 1k drk and keep it in a bank deposit box.

Figuratively speaking, I was joking but this new wallet does sound scary. Like if the keys can't be written back to the wallet.dat, that's an issue we have to be careful in dealing with this now. I'm not sure how paper wallets work with the new version. I guess if we want to migrate paper wallets to v.32, best way is to use the stable version and not DS version?

 

[iHeartSmartArt]

Figuratively speaking, I was joking but this new wallet does sound scary. Like if the keys can't be written back to the wallet.dat, that's an issue we have to be careful in dealing with this now. I'm not sure how paper wallets work with the new version. I guess if we want to migrate paper wallets to v.32, best way is to use the stable version and not DS version?

Stable versions are best until beta is over with and this problem is solved in the final stable DS wallet.
All those who haven't updated will eventually download this final stable wallet and be okay.

 

[Lord Of The Internet]

regarding the legality:

Set up a darkcoin limited liability company. Then, somehow register darkcoin as a religion. Then, somehow buy a plot of land on an American Indian reservation. Then, code laws on your sovereign plot of land that includes any and all darkcoin users as members of your religion, company, indian tribe. Rinse and repeat until there are darkcoin safehavens in every country and state.

i'm halfway serious ; p

 

[JGCMiner]

Figuratively speaking, I was joking but this new wallet does sound scary. Like if the keys can't be written back to the wallet.dat, that's an issue we have to be careful in dealing with this now. I'm not sure how paper wallets work with the new version. I guess if we want to migrate paper wallets to v.32, best way is to use the stable version and not DS version?

I don't understand the concern. The issue only exists if you try to use an existing encrypted wallet.dat with V32. How would this effect paper wallets as you would have to generate a new wallet.dat (which have no reported problems) and then import your private key.

 

[moli]

I don't understand the concern. The issue only exists if you try to use an existing encrypted wallet.dat with V32. How would this effect paper wallets as you would have to generate a new wallet.dat (which have no reported problems) and then import your private key.

Because I'm confused? lol. I was wondering if the new wallet version with 1000 keys also had effect on changing the private key structure. But I guess not. Thanks.

Edit: Also, I don't know much about paper wallets, have never done it. And I was told using paper wallets online isn't a good idea.

 

[dark-sailor]

DS+ gets through a lot of keys - burner addresses for each transaction basically.

The advantage of firing up v32 without anything called wallet.dat in your darkcoin directory, copying the new address it will generate upon generating a fresh wallet.dat, then closing v32, starting v31 and sending your balance to the new v32 address is... that you wont suffer a rare but possible case of wallet corruption.

Up to you! :tongue:

I did the this but sent them from v32 to v32 all seems ok on ubuntu and my mates windows.

 

[moli]

I installed the Stable version (v.0.9.12.32), and migrated my old wallet.dat (v.10.11.5) to this Stable version and it runs fine. I was apprehensive (and i'm not the only one) when hearing of the issues with the DS wallets.

I would recommend using the Stable version (v.0.9.12.32) from darkcoin.io if someone is not sure. I'll install the DS wallet version on another computer and play with it again.