Topic: [XDN] DarkNote. Anonymous 100% PoW CPU+Untraceable Crypto Messages+GUI Client! - page 45. (Read 113737 times)

Indeed.

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

Yes, same coin.

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.

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

I think we need It.

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

Is there/will there be a XDN richlist?

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

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.

I am interested...

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 > const&, std::vector > const&, std::vector >, 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! 

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!

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!

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

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.

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.

Thank you, please post your request here http://darknotetalk.org

@dNote

In a new wallet version, could you please change the order in which the transactions are shown in History? It is much better if the latest transactions are at the top, instead of at the bottom of the list. Thanks.