Nope, a quick Google search will reveal that they are not the same people. MSAFE for instance is Scottish.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.
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 forumNope, a quick Google search will reveal that they are not the same people. MSAFE for instance is Scottish.
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.Is there any press release & contacting wired, coinbase etc. in plan before the news about DarkTor gets too old?
Crypto is an extremely small community, especially alt-crypto. I'm sure you could find links between just about anyone =)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![]()
OP on BCT thread still not updated as well.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) *******
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).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!![]()
I meant the Original Post (1st post) in the DRK thread on bitcointalk: https://bitcointalk.org/index.php?topic=421615.0What 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).
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.I meant the Original Post (1st post) in the DRK thread on bitcointalk: https://bitcointalk.org/index.php?topic=421615.0
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.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?
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.32Is there any chance that users could have problems with their old encrypted wallets? (I assume most run encrypted)
As MNs do not use Darksend (masternode=1 disables darksend functionality implicitly), you don't need to create a new wallet.datForgive 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?
Makes sense! Thanks Flare.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.
DS+ gets through a lot of keys - burner addresses for each transaction basically.What's the advantage for having 1000 keys vs. the incompatibility issue with the old wallets?
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...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:
Figuratively speaking, I was jokingBury 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.![]()
Stable versions are best until beta is over with and this problem is solved in the final stable DS wallet.Figuratively speaking, I was jokingbut 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.Figuratively speaking, I was jokingbut 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?
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.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.
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: