It's Mac OS cache. Just reboot and it should show the new D in dmg too.Final tweak is needed on the OSx side.
When opening the .dmg, the app icon is still the old darkcoin D.
Once copied over to the system, the app does have the new D. On the dock its the new D too, looks really really cool !
I'm afraid the whitepapers are not updated yet. Evan is working on that, but it is either coding or writting... Masternode blinding is not yet included in today's update. I think the most informative approach would be a few links to announcements here (including the one on vulnerabilities in CoinShuffle and DarkWallet) and maybe Evan's last interview in LTB:Hey guys crosspost from bitcointalk if anyone can help me
Hey guys - I contacted the author of this article https://medium.com/@eordano/we-need-more-coinjoin-c7fefd12dc5e on coinjoin and asked him if he had looked into Darkcoin/Dash. He did respond but I'm not sure if I can link him to any whitepapers right now on our anonimity seeing as they are maybe out of date since the last few updates and don't include masternode blinding etc?
Here's our interaction so far. https://twitter.com/eordano/status/582610820636532736
I know, I'm working on thatBy the way fernando - The dashpay website is broken in various ways (not your fault necessarily some links seem to be dead). Documentation for example leads to a dead page. Whitepaper downloads from the bitcointalk thread also lead to a dead link, etc.
Sorry to do it in this thread it's just the most active one currently.
Hello, I'm afraid that OCD windows may have something wrong with registry but for workaround please edit your Dash shortcut to have "Dash-qt.exe -datadir=[your expected folder path, ex c:\dashdata]"
Basically, just replace darkcoind with dashd and darkcoin with dashGreat job on releasing a brand new wallet with that many improvements!
But for the less Tech-Savvy Linux users, I used to follow TAO's update guide: https://dashtalk.org/threads/taos-masternode-setup-guide-for-dummies.2680/#post-25672
Anyone that can help me along? I'm rather safe than sorry....
Wish it was that easy..Basically, just replace darkcoind with dashd and darkcoin with dash
Other new things in this release:
- New masternode voting system for new Dash initiates, each masternode gets one vote. See the new commands “masternode list votes” and “masternode vote yea|nay”. First vote, what color is this dress : http://imgur.com/QjqfntR ? Blue and Black (yea) or White and Gold (nay)
I say thee nay. There is a better way to do that. You only need to open your client and type:Hi,
anyone can post how to do masternode vote ?
Solved: you have to execute it on each masternode separately
" dashd masternode vote yea"
masternode vote-many nay
Not really sure how all this should look like (a clueless n00b) here:Hello, I'm afraid that OCD windows may have something wrong with registry but for workaround please edit your Dash shortcut to have "Dash-qt.exe -datadir=[your expected folder path, ex c:\dashdata]"
then create folder (ex. c:\dashdata) and run the shortcut again.
really quick run up. sorry, don't want to go too much into details. Taos' guide does that.Wish it was that easy..
[email protected]:~$ ./dashd
Error: To use the "-server" option, you must set a rpcpassword in the configuration file:
It is recommended you use the following random password:
(you do not need to remember this password)
The username and password MUST NOT be the same.
If the file does not exist, create it with owner-readable-only file permissions.
It is also recommended to set alertnotify so you are notified of problems;
for example: alertnotify=echo %s | mail -s "Dash Alert" [email protected]
Yeah thanks mate, but already found out myself. (Edited my previous post )really quick run up. sorry, don't want to go too much into details. Taos' guide does that.
local machine: does not need to be online after MN started
MN_ALIAS MN_IP:9999 rpcpassword_you_set_up_in_your_remote_MN TX_ID_WITH_1000_DASH_THAT_YOU_GET_FROM_dashd_masternode_outputs index_from_the_same_command
same as above and masternode=1
no need to have masternode.conf file on remote
Then, start both with dashd -daemon
wait till blocks are synced
and do on local
dashd masternode start-alias <your_alias_you_set_up_in_masternode.conf>
afterwards, check https://dashninja.pl/ IP of your remote MN shows active
How it's showing which is not work?Not really sure how all this should look like (a clueless n00b) here:
"C:\Program Files\Dash\Dash-qt.exe -datadir=c:\dashdata" is the path. Does not work. What am I doing wrong?
elbereth, post: 49076, member: 175anyone else than me noticing that dashninja.pl isnt updating the blockcount? noticed it when updating MNs and uptimerobot didnt report them as up
if you just move or copy all the files from your desktop to the new directory it should not need to re sync the entire block.Thanks. The shortcut's working only that it now needs to sync with the network. The good news so far, nothing appeared on the desktop this time... (all these data that used to pop up on desktop are now in C:\dashdata )
All I need to see now are Dash in the wallet
This way or another, thank you for helping me out!
No problems here, tested with 3 different win7 pc.Am I the only one that gets access violation exceptions when trying to start up the wallet? Win32 dash-qt.exe. This started after migrating to bitcoin codebase. Sometimes I have to start it 10 times before it manages to load up fully. After that it works just fine.
Bump for visibility.Am I the only one that gets access violation exceptions when trying to start up the wallet? Win32 dash-qt.exe. This started after migrating to bitcoin codebase. Sometimes I have to start it 10 times before it manages to load up fully. After that it works just fine.