[XDN] DarkNote. Anonymous 100% PoW CPU+Untraceable Crypto Messages+GUI Client!

[dNote]

It's not FUD. There's no fear, uncertainty, or doubt about it. More than half of all coins were mined when ducknote had a lower hashrate than any other Crytponote coin (except maybe quazar or fantomcoin which are dead/dying), even lower than the obvious scam bytecoin.

1. There is NO matter what hashrate was! The matter is the number of initial ordinary XDN workers and miners.

You're the one who brought up how the hashrate was to the moon/sky:

2. To be fair and honest and to avoid any misunderstandings XDN announce was at the same second as first block was generated. Being true it was a BIG surprise to see hashrate going to the sky, just after launch. XDN had more than 40 000 000 difficulty in first hours after launch.  Also first month we promoted XDN very active and asked people to mine it, we explained Economy and logic.

The hashrate didn't go to the sky and there wasn't a lot of miners, unless they were all mining at 1 h/s, which seems quite unlikely.

I said what i said man. XDN is the only CN coin with mass users, miners and traders joining since the first blocks.  

4 hours after an announce XDN had 250 000 H/s !
Good core i7 linux with CPU-miner multi gives ~ 230 h/s
Average windows PC or laptop gives you ~ 50 h/s
Let it be 140 h/s on average . So 250 000/ 150 = 1785 miners 4 hours after announce.
 
But it is hard to argue with you, because you can't hear the voices on multiple people, who mined and traded XDN long before our dispute.


EDIT: Even now We have more than 12% of mined coins on major exchanges on sell orders.

[1715663376]

1715663376

[1715663376]

1715663376

[dNote]

We are happy to announce v 0.97beta of DarkNote GUI client. MAC version included!
Lots of small improvements and fixes, and the main work was about MAC mining.
Please, test it.

DarkNote GUI Windows 64 Client

http://darknote.cc/sites/darknote.cc/files/darknotewallet_64.exe
Mirror Mega - https://mega.co.nz/#!rpBzVBpJ!TmLIBpBJHn8fSISwCliYoxBJNATRa45LjQIQEByj9OM

DarkNote GUI Windows 32 Client

http://darknote.cc/sites/darknote.cc/files/darknotewallet_32.exe
Mirror Mega - https://mega.co.nz/#!v1JEzAAA!_fRZrhEQMspO4WoLCh6_YzIwq_opoBYYNOrVOGc6nh0

DarkNote Client GUI for MAC

http://darknote.cc/sites/darknote.cc/files/darknotewallet.zip
Mirror Mega - https://mega.co.nz/#!L8xkSIJK!tge6Cb19kHTp8mjndNXJWnnMrIZ9Uf7qM_p80hWjH_k

Is this still all closed-source?

not all at all

We understand your confusion, but all software that we upload to open source source should be tested and verified multiple times, to avoid any issues.

Currently we pushed "reinvented" DarkNote code to github (new updated DarkNoted daemon + Simplewallet):
https://github.com/ducknote/darknote/commit/7c60affd32065eb0a8704e7a7f862a260869d5a9

Please, be careful, commit is SO big, that your browser can stuck 

Just about now we are ending all cryptography implementation tests and will push all cryptography, described in whitepaper to github. I think it will be pushed in next 48 hours.
Stay tuned.

[Toninho]

We are happy to announce v 0.97beta of DarkNote GUI client. MAC version included!
Lots of small improvements and fixes, and the main work was about MAC mining.
Please, test it.

DarkNote GUI Windows 64 Client

http://darknote.cc/sites/darknote.cc/files/darknotewallet_64.exe
Mirror Mega - https://mega.co.nz/#!rpBzVBpJ!TmLIBpBJHn8fSISwCliYoxBJNATRa45LjQIQEByj9OM

DarkNote GUI Windows 32 Client

http://darknote.cc/sites/darknote.cc/files/darknotewallet_32.exe
Mirror Mega - https://mega.co.nz/#!v1JEzAAA!_fRZrhEQMspO4WoLCh6_YzIwq_opoBYYNOrVOGc6nh0

DarkNote Client GUI for MAC

http://darknote.cc/sites/darknote.cc/files/darknotewallet.zip
Mirror Mega - https://mega.co.nz/#!L8xkSIJK!tge6Cb19kHTp8mjndNXJWnnMrIZ9Uf7qM_p80hWjH_k

Is this still all closed-source?

not all at all

We understand your confusion, but all software that we upload to open source source should be tested and verified multiple times, to avoid any issues.

Currently we pushed "reinvented" DarkNote code to github (new updated DarkNoted daemon + Simplewallet):
https://github.com/ducknote/darknote/commit/7c60affd32065eb0a8704e7a7f862a260869d5a9

Please, be careful, commit is SO big, that your browser can stuck 

Just about now we are ending all cryptography implementation tests and will push all cryptography, described in whitepaper to github. I think it will be pushed in next 48 hours.
Stay tuned.

[jwinterm]

It's not FUD. There's no fear, uncertainty, or doubt about it. More than half of all coins were mined when ducknote had a lower hashrate than any other Crytponote coin (except maybe quazar or fantomcoin which are dead/dying), even lower than the obvious scam bytecoin.

1. There is NO matter what hashrate was! The matter is the number of initial ordinary XDN workers and miners.

You're the one who brought up how the hashrate was to the moon/sky:

2. To be fair and honest and to avoid any misunderstandings XDN announce was at the same second as first block was generated. Being true it was a BIG surprise to see hashrate going to the sky, just after launch. XDN had more than 40 000 000 difficulty in first hours after launch.  Also first month we promoted XDN very active and asked people to mine it, we explained Economy and logic.

The hashrate didn't go to the sky and there wasn't a lot of miners, unless they were all mining at 1 h/s, which seems quite unlikely.

I said what i said man. XDN is the only CN coin with mass users, miners and traders joining since the first blocks.  

4 hours after an announce XDN had 250 000 H/s !
Good core i7 linux with CPU-miner multi gives ~ 230 h/s
Average windows PC or laptop gives you ~ 50 h/s
Let it be 140 h/s on average . So 250 000/ 150 = 1785 miners 4 hours after announce.
 
But it is hard to argue with you, because you can't hear the voices on multiple people, who mined and traded XDN long before our dispute.


EDIT: Even now We have more than 12% of mined coins on major exchanges on sell orders.

Since you want to keep arguing about it...I think you're probably aware that you can get 1+ kh/s on amazon ec2, or 600 h/s from a gpu instance which is almost 3x cheaper typically. This would be a few hundred instances on amazon, which for all we know could have been launched by one or several people. The fact is the hashrate was less than any other Cryptonote, and the emission is/was orders of magnitude faster. Also, the length of the ducknote ANN thread is far shorter than Boolberry or Monero (or even the scamtacular Bytecoin), indicating interest by fewer people. My point is that I'm not sure how lowest hashrate + fastest emission = best distribution, and I haven't really heard you give a satisfactory answer to this yet. So, if you want to keep responding, I'll be glad to keep arguing

[kkraus69]

We post XDN DarkNote RoadMap:
http://darknote.cc/roadmap
http://darknotetalk.org/index.php?topic=43
https://magic.piktochart.com/output/2889706-untitled-infographic

This roadmap looks exciting!
Energy efficient ARM mining implementation and especially a mobile wallet, will be huge! There are so many other points touched on as well... There is so much to come. dMote and the XDN team are an asset to the cryptonote community and the crypto community in general.
Good job and great work!

[tjc]

We post XDN DarkNote RoadMap:

A few mistakes in that graphic that you'll want to correct:

- merchatns (on the first image, on the bottom right)
- XDN massives (not sure what you wanted to say here ?)
- to your or your -> to you or your
- implementstions -> implementations (or even without the final s)
- interraction -> interaction
- scratching -> not sure what you wanted to say here either, it sounds weird :p
- proved spending -> I think "provable" is better here, but subjective
- messanging -> messaging
- ask you questions -> ask your questions
- spread xdn infromation -> spread xdn information
- tell your friend -> tell your friends


Well done on all the impressive work!    _o<

uuups,  Done, sorry for inconvenience.

When you say "Freedom and Liberty is a heart of XDN" do you mean "Freedom and liberty are at the heart of XDN."?

"DarkNote is going to be the most powerful POW privacy protected cryptocurrency and anonymous  services base layer."
Maybe try "DarkNote is on track to become the most powerful POW privacy protected cryptocurrency and anonymous  services base layer."

MULTISIGS - "Collective" addresses are the Doors of New Economy

I agree, impressive work!

[bearishtrader]

Can anyone help with this Ubuntu 14.04 LTS compile error?  Previously I had no problems compiling ducknote (just had to tweak CMakeLists.txt, to support gcc 4.9.x instead of 4.8.x)
Now though I get this bug:

/usr/local/darknote# make
mkdir -p build/release
cd build/release && cmake -D CMAKE_BUILD_TYPE=Release ../..
-- Boost version: 1.55.0
-- Found the following Boost libraries:
--   system
--   filesystem
--   thread
--   date_time
--   chrono
--   regex
--   serialization
--   program_options
-- Found Git: /usr/bin/git
-- Could NOT find Threads (missing:  Threads_FOUND)
-- Configuring done
-- Generating done
-- Build files have been written to: /usr/local/darknote/build/release
cd build/release && make
make[1]: Entering directory `/usr/local/darknote/build/release'
make[2]: Entering directory `/usr/local/darknote/build/release'
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
make[3]: Entering directory `/usr/local/darknote/build/release'
fatal: No names found, cannot describe anything.
CMake Warning at src/version.cmake:3 (message):
  Cannot determine current revision.  Make sure that you are building either
  from a Git working tree or from a source archive.


make[3]: Leaving directory `/usr/local/darknote/build/release'
[  0%] Built target version
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[  2%] Built target epee
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 13%] Built target upnpc-static
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 17%] Built target common
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 32%] Built target crypto
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 43%] Built target cryptonote_core
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 44%] Built target connectivity_tool
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 45%] Built target rpc
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 46%] Built target daemon
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 48%] Built target node_rpc_proxy
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 49%] Built target simpleminer
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 58%] Built target wallet
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 60%] Built target simplewallet
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 60%] Built target TestGenerator
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 61%] Built target core_proxy
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 71%] Built target coretests
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 76%] Built target crypto-tests
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
make[3]: Entering directory `/usr/local/darknote/build/release'
Linking CXX executable difficulty-tests
/tmp/ccfBwXlX.ltrans0.ltrans.o: In function `cryptonote::construct_tx(cryptonote::account_keys const&, std::vector<cryptonote::tx_source_entry, std::allocator<cryptonote::tx_source_entry> > const&, std::vector<cryptonote::tx_destination_entry, std::allocator<cryptonote::tx_destination_entry> > const&, std::vector<unsigned char, std::allocator<unsigned char> >, cryptonote::Transaction&, unsigned long)':
ccfBwXlX.ltrans0.o:(.text+0x12a): undefined reference to `crypto::crypto_ops::generate_keys(crypto::public_key&, crypto::secret_key&)'
ccfBwXlX.ltrans0.o:(.text+0x60e): undefined reference to `epee::log_space::log_singletone::get_prefix_entry()'
ccfBwXlX.ltrans0.o:(.text+0x6de): undefined reference to `epee::log_space::log_singletone::do_log_message(std::string const&, int, int, bool, char const*)'
ccfBwXlX.ltrans0.o:(.text+0x6ff): undefined reference to `epee::log_space::log_singletone::get_set_err_count(bool, unsigned long)'
ccfBwXlX.ltrans0.o:(.text+0x70d): undefined reference to `epee::log_space::log_singletone::get_set_err_count(bool, unsigned long)'
ccfBwXlX.ltrans0.o:(.text+0xa9b): undefined reference to `crypto::crypto_ops::generate_key_derivation(crypto::public_key const&, crypto::secret_key const&, crypto::key_derivation&)'
ccfBwXlX.ltrans0.o:(.text+0xac4): undefined reference to `crypto::crypto_ops::derive_public_key(crypto::key_derivation const&, unsigned long, crypto::public_key const&, crypto::public_key&)'
...
Thanks in advance! 

[zigpumper]

I am interested...

[MoneroMooo]

Pool owners should update the pool software (or at least merge the relevant patch). There's an exploit that's been fixed, where a miner can send duplicate shares that aren't detected. Relevant patch is c5e7aefc1ff6d5ed082dabc727f77f7676dbc1c2 from https://github.com/zone117x/node-cryptonote-pool.git.

This is "just" a pool exploit and has no other impact on darknote/ducknote in any way.

An exploit has been found in the pool code, which means that some miners are submitting duplicate shares to the pools. Pool owners should update to latest code, pools that have been patched include minexmr.com, hashinvest.net and monero.crypto-pool.fr. Other pools are currently being exploited, including moneropool.com, which means if you are mining there you will recieve ~40% xmr less than you should.

PS this is not related to the recent BCX stuff

[33reg]

Pool owners should update the pool software (or at least merge the relevant patch). There's an exploit that's been fixed, where a miner can send duplicate shares that aren't detected. Relevant patch is c5e7aefc1ff6d5ed082dabc727f77f7676dbc1c2 from https://github.com/zone117x/node-cryptonote-pool.git.

This is "just" a pool exploit and has no other impact on darknote/ducknote in any way.

An exploit has been found in the pool code, which means that some miners are submitting duplicate shares to the pools. Pool owners should update to latest code, pools that have been patched include minexmr.com, hashinvest.net and monero.crypto-pool.fr. Other pools are currently being exploited, including moneropool.com, which means if you are mining there you will recieve ~40% xmr less than you should.

PS this is not related to the recent BCX stuff

Is it related version: https://github.com/fancoder/cryptonote-universal-pool
?

[Digithusiast]

Is there/will there be a XDN richlist?

[sandor111]

We post XDN DarkNote RoadMap:
http://darknote.cc/roadmap
http://darknotetalk.org/index.php?topic=43
https://magic.piktochart.com/output/2889706-untitled-infographic

This roadmap looks exciting!
Energy efficient ARM mining implementation and especially a mobile wallet, will be huge! There are so many other points touched on as well... There is so much to come. dMote and the XDN team are an asset to the cryptonote community and the crypto community in general.
Good job and great work!

GUI looks great... when is it coming out?

[joewills]

Is there/will there be a XDN richlist?

I think we need It.

[bOSsmarie]

is XDN ducknote = XDN Darknote?

i have XDN ducknote on Bittrex can i transfer it in my Darknote wallet in my PC?

are they the same coin, i am not getting all of this T_T

[jwinterm]

Is there/will there be a XDN richlist?

I think we need It.

Do you guys not understand how Cryptonote works at all? Have you tried to check your balance on a block explorer? At best you can try and get some self-reporting survey and just trust that you can get all richest people to tell the truth...which is another argument why cryptonotes in particular should have longer, slower emission curve.

[kkraus69]

Yes, same coin.

[MoneroMooo]

Pool owners should update the pool software (or at least merge the relevant patch). There's an exploit that's

Is it related version: https://github.com/fancoder/cryptonote-universal-pool
?

This one appears to be derived from the one I linked, so it would have the same flaw, and would need the fix too.

[arnuschky]

We are happy to announce v 0.97beta of DarkNote GUI client. MAC version included!
Lots of small improvements and fixes, and the main work was about MAC mining.
Please, test it.

DarkNote GUI Windows 64 Client

http://darknote.cc/sites/darknote.cc/files/darknotewallet_64.exe
Mirror Mega - https://mega.co.nz/#!rpBzVBpJ!TmLIBpBJHn8fSISwCliYoxBJNATRa45LjQIQEByj9OM

DarkNote GUI Windows 32 Client

http://darknote.cc/sites/darknote.cc/files/darknotewallet_32.exe
Mirror Mega - https://mega.co.nz/#!v1JEzAAA!_fRZrhEQMspO4WoLCh6_YzIwq_opoBYYNOrVOGc6nh0

DarkNote Client GUI for MAC

http://darknote.cc/sites/darknote.cc/files/darknotewallet.zip
Mirror Mega - https://mega.co.nz/#!L8xkSIJK!tge6Cb19kHTp8mjndNXJWnnMrIZ9Uf7qM_p80hWjH_k

Is this still all closed-source?

not all at all

We understand your confusion, but all software that we upload to open source source should be tested and verified multiple times, to avoid any issues.

Currently we pushed "reinvented" DarkNote code to github (new updated DarkNoted daemon + Simplewallet):
https://github.com/ducknote/darknote/commit/7c60affd32065eb0a8704e7a7f862a260869d5a9

Please, be careful, commit is SO big, that your browser can stuck 

Indeed.

[dNote]

GUI looks great... when is it coming out?

It is under active development, i hope you will see it in next 5-10 days.

Cryptography tests are almost done and cryptography that is described in DarkNote whitepaper, will be public very soon.
 

[dNote]

Please, post your feature requests for the new DarkNote client here. I will make a features and improvements list here:

http://darknotetalk.org/index.php?board=27.0