The Beginning of Internet Privacy ?
Dark IRIS
like I said use the pyramid as the logo why not go all the way and use a knock off of the all seeing eye
Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 4216. (Read 9723787 times)
August 21, 2014, 07:02:13 PM
like I said use the pyramid as the logo why not go all the way and use a knock off of the all seeing eye
August 21, 2014, 06:58:37 PM
The Beginning of Internet Privacy ?
Dark IRIS
I like this, my only concern with iris was conveying the opposite message, with Dark Iris I think is much more clear and I like your graphics. Nice
August 21, 2014, 06:55:07 PM
like I said use the pyramid as the logo why not go all the way and use a knock off of the all seeing eye
August 21, 2014, 06:24:52 PM
They should be fine, as Darksend should be disabled for those wallets, thus no large keypool issues (which were rare anyway).
Someone please correct me if I'm wrong, but I have no plans to mess with my MN wallet.dat files.
As my MN wallet.dat has a balance of 0.00 i will simply delete it on next update to v32+Someone please correct me if I'm wrong, but I have no plans to mess with my MN wallet.dat files.
I meant (and I think oblox said) the local/cold wallet that has the 1000DRK in it.
Btw. So far worked all fine.
August 21, 2014, 06:24:21 PM
If anyone's planning on creating physical darkcoins this has just got to be the material to make them with!
http://www.dailymail.co.uk/sciencetech/article-2690424/Scientists-discover-new-black-British-researchers-devise-material-dark-looks-like-black-hole.html
http://www.dailymail.co.uk/sciencetech/article-2690424/Scientists-discover-new-black-British-researchers-devise-material-dark-looks-like-black-hole.html
August 21, 2014, 06:23:48 PM
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.
restoring every possible key is as simple as restoring the wallet from the seed phrase.
Can't wait for this, it will make wallet management and security so much easier.
August 21, 2014, 06:20:51 PM
They should be fine, as Darksend should be disabled for those wallets, thus no large keypool issues (which were rare anyway).
Someone please correct me if I'm wrong, but I have no plans to mess with my MN wallet.dat files.
As my MN wallet.dat has a balance of 0.00 i will simply delete it on next update to v32+Someone please correct me if I'm wrong, but I have no plans to mess with my MN wallet.dat files.
I meant (and I think oblox said) the local/cold wallet that has the 1000DRK in it.
Correct, the one holding the 1000 DRK.
August 21, 2014, 06:17:19 PM
They should be fine, as Darksend should be disabled for those wallets, thus no large keypool issues (which were rare anyway).
Someone please correct me if I'm wrong, but I have no plans to mess with my MN wallet.dat files.
As my MN wallet.dat has a balance of 0.00 i will simply delete it on next update to v32+Someone please correct me if I'm wrong, but I have no plans to mess with my MN wallet.dat files.
I meant (and I think oblox said) the local/cold wallet that has the 1000DRK in it.
August 21, 2014, 06:15:40 PM
They should be fine, as Darksend should be disabled for those wallets, thus no large keypool issues (which were rare anyway).
Someone please correct me if I'm wrong, but I have no plans to mess with my MN wallet.dat files.
As my MN wallet.dat has a balance of 0.00 i will simply delete it on next update to v32+ Someone please correct me if I'm wrong, but I have no plans to mess with my MN wallet.dat files.
August 21, 2014, 06:12:43 PM
Since it's not mandatory for MN opps, will cold-storage wallet files for a cold/remote masternode be fine running v30/v31?
They should be fine, as Darksend should be disabled for those wallets, thus no large keypool issues (which were rare anyway). Someone please correct me if I'm wrong, but I have no plans to mess with my MN wallet.dat files.
edit: if you use the QT client to manage your MN funds, make sure you disable Darksend before loading the MN wallet to withdraw payments etc., or load it in conjunction with the darkcoin.conf file associated with that MN, which should have masternode=1 in it, disabling Darksend.
August 21, 2014, 06:10:27 PM
Whether it impacts me or not, I'm updating to the latest version.
Can't help it...
Can't help it...
August 21, 2014, 06:05:56 PM
- Added a darksend overview box showing some generic information
Yes. This... Rudimentary as it is, having it on the main wallet overview is crucial. Excellent.
August 21, 2014, 06:04:04 PM
Since it's not mandatory for MN opps, will cold-storage wallet files for a cold/remote masternode be fine running v30/v31?
August 21, 2014, 06:03:19 PM
****** 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/darkcoinproject/darkcoin-binaries/master/darkcoin-0.9.12.32-win.zip
Windows installer: https[Suspicious link removed]
Mac OSX: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/darkcoin-0.9.12.32-osx.dmg
Linux: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/darkcoin-0.9.12.32-linux.tar.gz
10.12.32 (RC) Binaries: Includes Darksend - Masternode Operators
Windows .exe: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/rc/darkcoin-0.10.12.32-win.zip
Mac OSX: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/rc/darkcoin-0.10.12.32-osx.dmg
Linux: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/rc/darkcoin-0.10.12.32-linux.tar.gz
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/darkcoinproject/darkcoin-binaries/master/darkcoin-0.9.12.32-win.zip
Windows installer: https[Suspicious link removed]
Mac OSX: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/darkcoin-0.9.12.32-osx.dmg
Linux: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/darkcoin-0.9.12.32-linux.tar.gz
10.12.32 (RC) Binaries: Includes Darksend - Masternode Operators
Windows .exe: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/rc/darkcoin-0.10.12.32-win.zip
Mac OSX: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/rc/darkcoin-0.10.12.32-osx.dmg
Linux: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/rc/darkcoin-0.10.12.32-linux.tar.gz
Nice work with the constant updates, very impressive.
August 21, 2014, 06:02:43 PM
10.12.32 The Money Bags Update
August 21, 2014, 05:59:10 PM
****** 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/darkcoinproject/darkcoin-binaries/master/darkcoin-0.9.12.32-win.zip
Windows installer: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/darkcoin-0.9.12.32-win32-setup.exe
Mac OSX: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/darkcoin-0.9.12.32-osx.dmg
Linux: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/darkcoin-0.9.12.32-linux.tar.gz
10.12.32 (RC) Binaries: Includes Darksend - Masternode Operators
Windows .exe: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/rc/darkcoin-0.10.12.32-win.zip
Mac OSX: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/rc/darkcoin-0.10.12.32-osx.dmg
Linux: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/rc/darkcoin-0.10.12.32-linux.tar.gz
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/darkcoinproject/darkcoin-binaries/master/darkcoin-0.9.12.32-win.zip
Windows installer: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/darkcoin-0.9.12.32-win32-setup.exe
Mac OSX: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/darkcoin-0.9.12.32-osx.dmg
Linux: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/darkcoin-0.9.12.32-linux.tar.gz
10.12.32 (RC) Binaries: Includes Darksend - Masternode Operators
Windows .exe: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/rc/darkcoin-0.10.12.32-win.zip
Mac OSX: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/rc/darkcoin-0.10.12.32-osx.dmg
Linux: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/rc/darkcoin-0.10.12.32-linux.tar.gz
August 21, 2014, 05:56:23 PM
Thats a posibility, but in general, its more for speculatif point of view (exchange coin to coin), dont know if stability is not more importante ?
I dont said my point of view is good, its just mine at this time.
I dont said my point of view is good, its just mine at this time.
Its a good point.
Regulations are different in different countries. Something legal in one place, might be illegal in another.
So, it makes lots of sense to have an option to run or not a particular service.
August 21, 2014, 05:41:58 PM
In the absence of DarkNet, I would go with:
It has to be catchy and roll off the tongue...
Keep the creative juices flowing all...
- MasterNet
- DarkMesh
- DarkSwarm
- Hive by Dark
It has to be catchy and roll off the tongue...
Keep the creative juices flowing all...
August 21, 2014, 05:41:00 PM
As a MN owner, I like the idea of making slow (or basic, you name it) browsing of MasterNet free, but as soon as one wants to watch videos, download, stream etc, make them pay. This way you get MUCH MORE people motivated to try out the service, and the ones willing to have something fast will pay.
This is a great idea. Limited at 64/128 kbps or something similar for those browsing for free, then whatever the network allows for those paying. I have no idea whether it's possible to implement though.
August 21, 2014, 05:39:45 PM
How about free (basic, capped) access for maintaining, say 100DRK in your wallet? Or something along those lines - might help price stability?
Good enough for private email, chat etc.
Good enough for private email, chat etc.
Jump to: