Development Update - August 19, 2014

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.
 
Light said:
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.
Click to expand...

Nope, a quick Google search will reveal that they are not the same people. MSAFE for instance is Scottish.
 
David said:
Nope, a quick Google search will reveal that they are not the same people. MSAFE for instance is Scottish.
Click to expand...

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 :)
 
hard_forker said:
Is there any press release & contacting wired, coinbase etc. in plan before the news about DarkTor gets too old?
Click to expand...
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.
 
Light said:
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 :)
Click to expand...

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.
 
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!
 
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
 
moli said:
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) *******
Click to expand...

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! ;)
 
thelonecrouton said:
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! ;)
Click to expand...

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).
 
Last edited by a moderator:
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)
 
mattmct said:
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?
Click to expand...
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)
Click to expand...

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.
 
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?
 
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?
 
David said:
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?
Click to expand...
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.
 
flare said:
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.
Click to expand...

Makes sense! Thanks Flare.
 
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.
 
Last edited by a moderator:
You must log in or register to reply here.
Back
Top