...
Hey dNote. What kind of plans do you have for duckNote in August? 1. first GUI binary at least for Windows users 2. Marketing phase: interviewing about duckNote, massive community building, coin promotion, etc 3. Keep working on XDN network features and improvements. |
|
|
|
the total are so big?
Do you mean total duckNote supply? = 8 589 869 056 XDN
1. That is a 6th perfect number, discovered by Cataldi. In number theory, a perfect number is a positive integer that is equal to the sum of its proper positive divisors, that is, the sum of its positive divisors excluding the number itself (also known as its aliquot sum). Equivalently, a perfect number is a number that is half the sum of all of its positive divisors (including itself) i.e. σ1(n) = 2n. http://en.wikipedia.org/wiki/Perfect_number2. That perfect number will avoid current Bitcoin alike denomination, imagine ~8bln Bitcoin market with ~8bln supply coin, like duckNote. 3. With duckNote supply curve ~79% of ever generated XDN will be emitted ~after 1 year since first block generation. 4. Also recently world population reached 7 bln people. Imagine, 1 person will own 1 XDN. |
|
|
|
|
Please use 64 bit OS version and try to avoid 32-bit version it is buggy.
We are working on OS - independent wallet. It may take some time, but result will be ducksome. Stay tuned.
|
|
|
|
|
Hey, recently duckNote [XDN] was added to HitBTC, please add new XDN exchange to coinmarketcap. Thank you.
|
|
|
|
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. |
|
|
|
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. |
|
|
|
... but nobody has lost anything.
Wrong! False Untrue statement. |
|
|
|
-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.cc2. Click Getting Started link  http://monero.cc/getting-started/index.html3. Click http://monero.cc/getting-started/index.html#install_source4. Here we can read: git clone git://github.com/monero-project/bitmonero && cd bitmonero && make5. Go to the suggested code, master branch -> commits: https://github.com/monero-project/bitmonero/commits/master6. Find that commit https://github.com/monero-project/bitmonero/commit/d433a696e527a01c1cbef48495652335140f0bb2 on master branch7. 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. |
|
|
|
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/d433a696e527a01c1cbef48495652335140f0bb2With "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. |
|
|
|
Just checked again, aaand r u kidding me? Payment ID was implemented in duckNote since the Initial commit! So that feature was made by Bytecoin developers, here is the commit: https://github.com/amjuarez/bytecoin/commit/57cf53625817223733bdaf2f4e518ebae978713e - April 29
So, backward pass to you, can monero devs credit Bytecoin devs, at least at that case. P.S. never looked at side of monero before, checked, lots of anger there, bad emotions, duck like peace, rabbit runs from war. D< Quack |
|
|
|
"the very many changes we've made that they've merged down" - many changes merged from XMR to duckNote - really? Please count down again. I guess there is the only one merged change mentioned by you, maybe there was another one. No. duckNote has its own way. Actually we (devs) absolutely do not care about monero, since we do not see any innovation there. XMR is just a direct fork of Bytecoin, with some cosmetic changes and unprecedented speculative activity. I mean we are not against or with monero, we just do not care and that coin do not attract our interest at all. Good luck with your fork developing, but pacify megalomania  Quack D< That was a bit meandering but I'm wondering what is your specific objection to crediting the source of patches you use. No objections, Sir, We used payment ID patch to provide better integration with HTML GUI. If all monero community, or just a single developer was hurt (if it is their very first use of that patch - we just did not know that), much apologies, overtures and pas. Any way GUI HTML wallet is a temporary solution, and now we are working on multiple native duckNote GUI, as well as working on coin itself. |
|
|
|
"the very many changes we've made that they've merged down" - many changes merged from XMR to duckNote - really? Please count down again. I guess there is the only one merged change mentioned by you, maybe there was another one. No. duckNote has its own way. Actually we (devs) absolutely do not care about monero, since we do not see any innovation there. XMR is just a direct fork of Bytecoin, with some cosmetic changes and unprecedented speculative activity. I mean we are not against or with monero, we just do not care and that coin do not attract our interest at all. Good luck with your fork developing, but pacify megalomania Quack D< |
|
|
|
A new ducknote exchange that supports 3 decimal places past a satoshi, to aid in fixing the earlier discussed problem of there not being more decimals in the price. More info will be in its separate thread here: https://bitcointalk.org/index.php?topic=688632I put the thread where I thought it should go, but I do not have as much experience on bitcointalk as others. If there is a better place to put the thread please let me know. Thanks! Thank you for your support! Is it a working exchange, or just an announce before launch? |
|
|
|
Hi guys! I think a lot of bounties are tired of waiting, so I decided to take matters into their own hands and help develop the community. So I decided to redistribute free coins, 250 XDN everyone who wants to. The first 100 people - by 250 XDNSecond 200 people - by 100 XDNThirds of 300 people - by 50 XDNCome, 4fun http://www.ducknotetalk.org/index.php?/topic/5-bounties-xdn-4fun/in the future to continue the promotion of development and forward interesting proposals on the forum. Super forum, thank you, will support it! provide your address for duckNote tips! |
|
|
|
xdn...just change the max coin ?
No, XDN is not only the MAX coin change. The whole coin supply logic differs from any other cryptonote coin. Block time is 4min, Max block without penalty is bigger than any other cryptonote coin. Difficulty window is different CORS support MIN_Block reward in XDN Etc, Look at main website for explanations and read this thread to know more about XDN. |
|
|
|
|
Show Posts
