[XDN] duckNote [ANN]. Anonymous, CPU-efficient, Smart Economy

[nopedope89]

Fees became lower on Minergate.com!

Guys, now fees for cryptonote coins are 1.5% PPS and 1% PPLNS

2-step verification

I implemented 2 step verification, so you can protect your account with both your password and your phone. To enable it go to Dashboard - > Profile

Enjoy!

[1714749600]

1714749600

[Xmining]

I sell many XDN at 6 satoshi and buy more XDN at 5 satoshi.
How great it is!

Look everybody! We got ourselves an entrepreneur!

[joewills]

I sell many XDN at 6 satoshi and buy more XDN at 5 satoshi.
How great it is!

Look everybody! We got ourselves an entrepreneur!

Thx. I just need more XDN.

[dNote]

I understand that there are lots of altcoins launched with barely a nod to ethical behaviour, but it would be greatly appreciated if Ducknote credited us for the very many changes we've made that they've merged down and claimed to be their own.

eg.

https://github.com/ducknote/ducknote/commit/e4a36e6af1ed89e13857f7d61a7aa3616c578b34 committed on July 4th

was originally added by us :

https://github.com/monero-project/bitmonero/commit/117393d562fc9782efed0e1b25f6470d9f8102b2 committed on June 2nd

monero devs seems to be absolutely beginners - your accusations and anger touched us, here is a result of 10 min research of your kiddy coding, concerning Payments ID and games with your kiddy coin wallet:
Second chapter of any average "Beginners in C++ guide" says that arguments can be passed to parameters either by value or by reference.
Looks like monero devs did not noticed that, when they recently read that kind of books.

Lets look at this playground:
https://github.com/monero-project/bitmonero/commit/d433a696e527a01c1cbef48495652335140f0bb2

With "Monero golden ampersand bug" made by monero devs, monero devs missed some &, wuuups:

bool validate_transfer(const std::list<wallet_rpc::transfer_destination> destinations, const std::string payment_id, std::vector<cryptonote::tx_destination_entry>& dsts, std::vector<uint8_t>& extra, epee::json_rpc::error& er);

bool wallet_rpc_server::validate_transfer(const std::list<wallet_rpc::transfer_destination> destinations, const std::string payment_id, std::vector<cryptonote::tx_destination_entry>& dsts, std::vector<uint8_t>& extra, epee::json_rpc::error& er)


Affects: Monero simplewallet since at least June 18 just lose all Payment ID data, so people can lost their money if they use your so called monero RPC "features". Again - all transfers in monero network made with JSON-RPC Payment ID, EG from Poloniex exchange to Bittrex exchange was made wrong if they use monero latest main kiddy code, or may be just lost. Qua, qua, qua ...

Users, be careful with kiddy coders.

[MoneroMooo]

Please, there's no need for that.
It'd be nice to credit people where possible, keeping commit messages and authorship where appropriate, whether or not this particular patch was from (I've not looked). There really is no need to go find fault in other code, we all have something we're not too proud of anyway, hidden in some old commit
Please take it as a good occasion to code something nice that Monero devs will then want to use (with credit of course). We all gain when this happens.

   _o<

[fluffypony]

-snip-

Well, I'll cut-and-paste my reply to you from Github:

@ducknote Please don't act stupid, you're better than this.

1. You're conflating - that was pulled into the code long before there were any Monero developers: https://github.com/monero-project/bitmonero/commit/333f975760c156727dd7408f87e937af856d8bf1. We have not failed to credit the CryptoNote developers, and where there is code that is merged from other CryptoNote projects we ALWAYS credit the source. For example, we have credited Boolberry on more than one occasion: https://github.com/monero-project/bitmonero/commit/c050ff43bf5a8310b18081c5cd3d9bcd123416b8, https://github.com/monero-project/bitmonero/commit/3bc16dc0e6bd38fbec51a054e640bacdb17a9a82. Similarly, Boolberry have credited us on more than one occasion: https://github.com/cryptozoidberg/boolberry/commit/f7a019683a2ecc1954b761ac7094d588644ecf1c, https://github.com/cryptozoidberg/boolberry/commit/88bfcbf6d067a3f15f3d22a87dcb54211dc11f17, and https://github.com/cryptozoidberg/boolberry/commit/0ae9a2f24757e7229cf63776b5897c5b408c065e.

2. I've never heard of a "golden ampersand" bug, and neither has Google. Either you're outrightly lying, or you're using the wrong term entirely. Regardless, your ad hominem attack is nothing more than a straw man argument to try and detract from your despicable failure to credit the authors of the code you have merged down.

To be specific, again, this functionality (the payment ID being available in the JSON RPC transfer call) is not something you wrote. It is something we wrote. I have already linked you to the commit where it was merged on June 2nd. Don't worry - you're not the only one that has failed to credit Monero, Bytecoin also added the change on June 25th, stripped the code comments, and failed to credit us.

If you wish to remain honourable it would be appropriate for you not to insult me or any of the contributors to Monero, and to credit us where you have used our code. Of course, if there is anything you write that we use we will most definitely credit you, just as we have done with Boolberry.

Code gets committed to staging so it can be tested. The piece of code you're referring to is not in the 0.8.8 tagged release, and is thus not finalised. Thanks for pointing out the error, but nobody has lost anything.

[Jojatekok]

I understand that there are lots of altcoins launched with barely a nod to ethical behaviour, but it would be greatly appreciated if Ducknote credited us for the very many changes we've made that they've merged down and claimed to be their own.

eg.

https://github.com/ducknote/ducknote/commit/e4a36e6af1ed89e13857f7d61a7aa3616c578b34 committed on July 4th

was originally added by us :

https://github.com/monero-project/bitmonero/commit/117393d562fc9782efed0e1b25f6470d9f8102b2 committed on June 2nd

monero devs seems to be absolutely beginners - your accusations and anger touched us, here is a result of 10 min research of your kiddy coding, concerning Payments ID and games with your kiddy coin wallet:
Second chapter of any average "Beginners in C++ guide" says that arguments can be passed to parameters either by value or by reference.
Looks like monero devs did not noticed that, when they recently read that kind of books.

Lets look at this playground:
https://github.com/monero-project/bitmonero/commit/d433a696e527a01c1cbef48495652335140f0bb2

With "Monero golden ampersand bug" made by monero devs, monero devs missed some &, wuuups:

bool validate_transfer(const std::list<wallet_rpc::transfer_destination> destinations, const std::string payment_id, std::vector<cryptonote::tx_destination_entry>& dsts, std::vector<uint8_t>& extra, epee::json_rpc::error& er);

bool wallet_rpc_server::validate_transfer(const std::list<wallet_rpc::transfer_destination> destinations, const std::string payment_id, std::vector<cryptonote::tx_destination_entry>& dsts, std::vector<uint8_t>& extra, epee::json_rpc::error& er)


Affects: Monero simplewallet since at least June 18 just lose all Payment ID data, so people can lost their money if they use your so called monero RPC "features". Again - all transfers in monero network made with JSON-RPC Payment ID, EG from Poloniex exchange to Bittrex exchange was made wrong if they use monero latest main kiddy code, or may be just lost. Qua, qua, qua ...

Users, be careful with kiddy coders.

Remember the good old game Duck Hunt? Well, it's time for some nostalgia by clarifying some things.

First of all, you seem to forget the main point of cryptocurrency by trying to "fight" other coins for your own profit. That's just simply unacceptable, period.

Also, test releases - surprisingly - mean that they are not ready for real-world use, and may cause harm for the brave man who take time trying to improve software by using it and notifying the developers about errors. On the other hand, can you explain the reason behind plagiarizing Monero's repositories without letting anyone know? You've just tried to evade Fluffypony's question, but I'll make sure you answer it here and now, in front of your own fans. Public apologies are welcome and accepted.

[fluffypony]

Incidentally, this was fixed 8 days ago, but this branch is not ready to merge into master yet: https://github.com/tewinget/bitmonero/commit/e7a3bd19f61d047f3daa49910e0d7da41ef47a8b

I guess that's what happens when you have an entire group of people contributing to a project instead of just one.

[dNote]

-snip-

Well, I'll cut-and-paste my reply to you from Github:

@ducknote Please don't act stupid, you're better than this.

1. You're conflating - that was pulled into the code long before there were any Monero developers: https://github.com/monero-project/bitmonero/commit/333f975760c156727dd7408f87e937af856d8bf1. We have not failed to credit the CryptoNote developers, and where there is code that is merged from other CryptoNote projects we ALWAYS credit the source. For example, we have credited Boolberry on more than one occasion: https://github.com/monero-project/bitmonero/commit/c050ff43bf5a8310b18081c5cd3d9bcd123416b8, https://github.com/monero-project/bitmonero/commit/3bc16dc0e6bd38fbec51a054e640bacdb17a9a82. Similarly, Boolberry have credited us on more than one occasion: https://github.com/cryptozoidberg/boolberry/commit/f7a019683a2ecc1954b761ac7094d588644ecf1c, https://github.com/cryptozoidberg/boolberry/commit/88bfcbf6d067a3f15f3d22a87dcb54211dc11f17, and https://github.com/cryptozoidberg/boolberry/commit/0ae9a2f24757e7229cf63776b5897c5b408c065e.

2. I've never heard of a "golden ampersand" bug, and neither has Google. Either you're outrightly lying, or you're using the wrong term entirely. Regardless, your ad hominem attack is nothing more than a straw man argument to try and detract from your despicable failure to credit the authors of the code you have merged down.

To be specific, again, this functionality (the payment ID being available in the JSON RPC transfer call) is not something you wrote. It is something we wrote. I have already linked you to the commit where it was merged on June 2nd. Don't worry - you're not the only one that has failed to credit Monero, Bytecoin also added the change on June 25th, stripped the code comments, and failed to credit us.

If you wish to remain honourable it would be appropriate for you not to insult me or any of the contributors to Monero, and to credit us where you have used our code. Of course, if there is anything you write that we use we will most definitely credit you, just as we have done with Boolberry.

Code gets committed to staging so it can be tested. The piece of code you're referring to is not in the 0.8.8 tagged release, and is thus not finalised. Thanks for pointing out the error, but nobody has lost anything.

lolollol "golden ampersand" bug - is mine © - i call it golden because just one "&" can cause a lot of money loss by monero users.

Again - Transaction ID was implemented in Bytecoin long before monero made it - https://github.com/amjuarez/bytecoin/commit/57cf53625817223733bdaf2f4e518ebae978713e April 29.

Monero just made it in RPC call, that part of kiddy code was ok, but nothing special and nothing hard. and at least that part of monero code was ok.

AGAIN:

Code gets committed to staging so it can be tested. The piece of code you're referring to is not in the 0.8.8 tagged release, and is thus not finalised. Thanks for pointing out the error, but nobody has lost anything.

Lets do like that:
1. Go to http://monero.cc
2. Click Getting Started link http://monero.cc/getting-started/index.html
3. Click http://monero.cc/getting-started/index.html#install_source
4. Here we can read: git clone git://github.com/monero-project/bitmonero && cd bitmonero && make
5. Go to the suggested code, master branch -> commits: https://github.com/monero-project/bitmonero/commits/master
6. Find that commit https://github.com/monero-project/bitmonero/commit/d433a696e527a01c1cbef48495652335140f0bb2 on master branch
7. Profit! Monero got "golden ampersand" bug since that commit, means since June 18th. All exchanges and services that made source code compilation from monero master branch since June 18th  affected.   

[joewills]

Oh. foolish.Who?
The dev of XMR.

[fluffypony]

-snip-

We've never claimed we "made" payment ID. We added it to the JSON RPC call in the wallet. That's it. Simple.

And you used the code (as did Bytecoin) without crediting us. Simple.

As pointed out, we fixed that bug 8 days ago.

Also, exchanges and services are using stable releases, not compiling head.

[Rias]

I understand that there are lots of altcoins launched with barely a nod to ethical behaviour, but it would be greatly appreciated if Ducknote credited us for the very many changes we've made that they've merged down and claimed to be their own.

eg.

https://github.com/ducknote/ducknote/commit/e4a36e6af1ed89e13857f7d61a7aa3616c578b34 committed on July 4th

was originally added by us :

https://github.com/monero-project/bitmonero/commit/117393d562fc9782efed0e1b25f6470d9f8102b2 committed on June 2nd

monero devs seems to be absolutely beginners - your accusations and anger touched us, here is a result of 10 min research of your kiddy coding, concerning Payments ID and games with your kiddy coin wallet:
Second chapter of any average "Beginners in C++ guide" says that arguments can be passed to parameters either by value or by reference.
Looks like monero devs did not noticed that, when they recently read that kind of books.

Lets look at this playground:
https://github.com/monero-project/bitmonero/commit/d433a696e527a01c1cbef48495652335140f0bb2

With "Monero golden ampersand bug" made by monero devs, monero devs missed some &, wuuups:

bool validate_transfer(const std::list<wallet_rpc::transfer_destination> destinations, const std::string payment_id, std::vector<cryptonote::tx_destination_entry>& dsts, std::vector<uint8_t>& extra, epee::json_rpc::error& er);

bool wallet_rpc_server::validate_transfer(const std::list<wallet_rpc::transfer_destination> destinations, const std::string payment_id, std::vector<cryptonote::tx_destination_entry>& dsts, std::vector<uint8_t>& extra, epee::json_rpc::error& er)


Affects: Monero simplewallet since at least June 18 just lose all Payment ID data, so people can lost their money if they use your so called monero RPC "features". Again - all transfers in monero network made with JSON-RPC Payment ID, EG from Poloniex exchange to Bittrex exchange was made wrong if they use monero latest main kiddy code, or may be just lost. Qua, qua, qua ...

Users, be careful with kiddy coders.

Remember the good old game Duck Hunt? Well, it's time for some nostalgia by clarifying some things.

First of all, you seem to forget the main point of cryptocurrency by trying to "fight" other coins for your own profit. That's just simply unacceptable, period.

Also, test releases - surprisingly - mean that they are not ready for real-world use, and may cause harm for the brave man who take time trying to improve software by using it and notifying the developers about errors. On the other hand, can you explain the reason behind plagiarizing Monero's repositories without letting anyone know? You've just tried to evade Fluffypony's question, but I'll make sure you answer it here and now, in front of your own fans. Public apologies are welcome and accepted.

And could you explain the reason behind Monero plagiarizing from Bytecoin?

The original post on your subreddit was deleted:
http://www.reddit.com/r/Monero/comments/295mbh/monero_devs_are_copycats/

However, it had two following references:
https://github.com/amjuarez/bytecoin/commit/baaa3484271e11398790bbf01ee4d7b19c68e3bb#diff-74021cb60bde0670646eb96a91e4443cR707
https://github.com/monero-project/bitmonero/commit/3a3a8176782a4fa75b0607fba0393c9d4a1746be#diff-74021cb60bde0670646eb96a91e4443cR707

Your community members started to say that "it is fine" to plagiarize in open source. Quote from neozaru:

If you are not a troll, read this : http://en.wikipedia.org/wiki/Open_source#Society_and_culture
bitmonero itself was and will be forked too.

http://www.reddit.com/r/Monero/comments/295mbh/monero_devs_are_copycats/cihtkf7

Double standards monero?

[dNote]

... but nobody has lost anything.

Wrong! False Untrue statement. 

[dNote]

Also, exchanges and services are using stable releases, not compiling head.

re e e e eally? thats getting exciting. please, keep on, tell us some more jokes.

[joewills]

I understand that there are lots of altcoins launched with barely a nod to ethical behaviour, but it would be greatly appreciated if Ducknote credited us for the very many changes we've made that they've merged down and claimed to be their own.

eg.

https://github.com/ducknote/ducknote/commit/e4a36e6af1ed89e13857f7d61a7aa3616c578b34 committed on July 4th

was originally added by us :

https://github.com/monero-project/bitmonero/commit/117393d562fc9782efed0e1b25f6470d9f8102b2 committed on June 2nd

monero devs seems to be absolutely beginners - your accusations and anger touched us, here is a result of 10 min research of your kiddy coding, concerning Payments ID and games with your kiddy coin wallet:
Second chapter of any average "Beginners in C++ guide" says that arguments can be passed to parameters either by value or by reference.
Looks like monero devs did not noticed that, when they recently read that kind of books.

Lets look at this playground:
https://github.com/monero-project/bitmonero/commit/d433a696e527a01c1cbef48495652335140f0bb2

With "Monero golden ampersand bug" made by monero devs, monero devs missed some &, wuuups:

bool validate_transfer(const std::list<wallet_rpc::transfer_destination> destinations, const std::string payment_id, std::vector<cryptonote::tx_destination_entry>& dsts, std::vector<uint8_t>& extra, epee::json_rpc::error& er);

bool wallet_rpc_server::validate_transfer(const std::list<wallet_rpc::transfer_destination> destinations, const std::string payment_id, std::vector<cryptonote::tx_destination_entry>& dsts, std::vector<uint8_t>& extra, epee::json_rpc::error& er)


Affects: Monero simplewallet since at least June 18 just lose all Payment ID data, so people can lost their money if they use your so called monero RPC "features". Again - all transfers in monero network made with JSON-RPC Payment ID, EG from Poloniex exchange to Bittrex exchange was made wrong if they use monero latest main kiddy code, or may be just lost. Qua, qua, qua ...

Users, be careful with kiddy coders.

Remember the good old game Duck Hunt? Well, it's time for some nostalgia by clarifying some things.

First of all, you seem to forget the main point of cryptocurrency by trying to "fight" other coins for your own profit. That's just simply unacceptable, period.

Also, test releases - surprisingly - mean that they are not ready for real-world use, and may cause harm for the brave man who take time trying to improve software by using it and notifying the developers about errors. On the other hand, can you explain the reason behind plagiarizing Monero's repositories without letting anyone know? You've just tried to evade Fluffypony's question, but I'll make sure you answer it here and now, in front of your own fans. Public apologies are welcome and accepted.

And could you explain the reason behind Monero plagiarizing from Bytecoin?

The original post on your subreddit was deleted:
http://www.reddit.com/r/Monero/comments/295mbh/monero_devs_are_copycats/

However, it had two following references:
https://github.com/amjuarez/bytecoin/commit/baaa3484271e11398790bbf01ee4d7b19c68e3bb#diff-74021cb60bde0670646eb96a91e4443cR707
https://github.com/monero-project/bitmonero/commit/3a3a8176782a4fa75b0607fba0393c9d4a1746be#diff-74021cb60bde0670646eb96a91e4443cR707

Your community members started to say that "it is fine" to plagiarize in open source. Quote from neozaru:

If you are not a troll, read this : http://en.wikipedia.org/wiki/Open_source#Society_and_culture
bitmonero itself was and will be forked too.

http://www.reddit.com/r/Monero/comments/295mbh/monero_devs_are_copycats/cihtkf7

Double standards monero?

So foolish.
What do you think about copy? I think it's a normarl thing.
XMR is the copy of BCN. Right?
XiaoMi and Tencent . What do you know two company in China?
The company is famous for copying skill.They are great.Because people like the All advantage in a thing.
XMR is a good copy-coin of BCN.So many people like to accept it .So XMR is good.

Maybe XMR need to copy the success of XDN.

[joewills]

Also, exchanges and services are using stable releases, not compiling head.

re e e e eally? thats getting exciting. please, keep on, tell us some more jokes.

XMR just is a joke.
So many wrong thing with XMR.
why did the man not to check the code and to solove the wrong?
Ever,They choose come in to  make a joke.

[fluffypony]

Double standards monero?

Not at all. That merge is from May 25th, before there was a core team and any guidance with dealing with that and crediting authors. Which is precisely what I said if you read further up.

By exactly the same token, Bytecoin has merged changes from us (including the payment ID JSON RPC call changes that duckNote have ripped as well) and did not credit us, so there are some double standards for you.

[sdersdf2]

Hello - noob to this coin. Has there been some new development here recently, or is there something big around the corner?

[dNote]

Hello - noob to this coin. Has there been some new development here recently, or is there something big around the corner?

we make, we test, than we push to avoid bugs like recently discussed monero bug.
now we are working on native GUI wallets and on XDN improvements.

[Rew0k]

Hello - noob to this coin. Has there been some new development here recently, or is there something big around the corner?

and the community actively engaged in supporting the coin
the forum is a bounties, 250 XDN Free
http://www.ducknotetalk.org/index.php?/topic/5-bounties-xdn-4fun/
Come