Dear users, We are sorry for the delay. Much apologies. But due to the major work we are doing and lots of tests we are running, "magic" event is delayed. Announce date is 17 September 2014 to 19 September 2014. You will be happy to see our work, please, be patient.
|
|
|
I understand your impatience, but we should be patient, we were waiting for so long, so we can wait a few more days. Probably we will announce all news at the end of this week.
|
|
|
Hint about next week news "... 11. Bg5 Na4 12. Qa3 Nxc3 13. bxc3 Nxe4 14. Bxe7 Qb6 15. Bc4 Nxc3 16. Bc5 Rfe8 17. Kf1 Be6 18. Bxb6 Bxc4 19. Kg1 Ne2 20. Kf1 Nxd4 ..."
|
|
|
~80% duckNotes mined in the first year. =6 900 000 000 It has been mined. 6 000 000 00 now.
True statements, some counts, just for notice: Block 35422 - XDN in circulation 6,063,162,001 Current block reward = 40 000 XDN 44000 is a reward halving block. (44000 - 35422)*40000 = 343,120,000 So in the end on current 4th month there will be ~ 6,063,162,001+343,120,000=6,406,282,001 XDN in circulation, that is about 74,5%. Next periods: 44000-55000 - 11000 blocks*20000 XDN block reward = 220,000,000 XDN 5 month 55000-66000 - 11000 blocks*10000 XDN block reward = 110,000,000 XDN 6 month 66000-77000 - 11000 blocks*5000 XDN block reward = 55,000,000 XDN 7 month 77000-88000 - 11000 blocks*2500 XDN block reward = 27,500,000 XDN 8 month 88000-99000 - 11000 blocks*1250 XDN block reward = 13,750,000 XDN 9 month 99000-11000 - 11000 blocks*625 XDN block reward = 6,875,000 XDN 10 month 110000-121000 - 11000 blocks*312.5 XDN block reward = 3,437,500 XDN 11 month 121000-132000 - 11000 blocks*156.25 XDN block reward = 1,718,750 XDN 12 month So: 6,406,282,001+220,000,000+110,000,000+55,000,000+27,500,000+13,750,000+6,875,000+3,437,500+1,718,750=6,844,563,251 6,844,563,251/8,589,869,056*100 = 79,68%
|
|
|
What day next week? ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) Close to the end of next week, but probably earlier
|
|
|
All XDN team is hardly working for the next week announce. Yes, wallet will be updated, but our news is not about wallet update.
|
|
|
Has the Block 122 bug been fixed on the mac wallet?
Wallet works fine and tested on latest MAC OS version.
|
|
|
dNote is English your first language? I mean no offence just trying to understand whats going on.
Me is Privacy Protected:) Ok fair enough, just to be clear before the fix you released could XDN have been attacked the same way as XMR. We know XDN was not attacked but it has been widely spread that all cryptonotes had the same flaw. I will be brief as usual D< : 1. This vulnerability is a double spend vulnerability. 2. This vulnerability is possible only if blockchain split occurs. Can call it fork. 3. Split or fork is possible with long attack preparation and that preparation is visible to those who watch the blockchain. 4. XDN devs watch blockchain 24/7 to avoid that kind of issues. 5. 1->2->3->4-> XDN IS and WAS invulnerable P.S. XDN devs fixed any related issues, and were first team who did that. https://github.com/ducknote/ducknote/commit/e9dcc9825601f5a7b209c78e3a61169ba4f31fbcYou guys are extremely clueless or just full of shit. XDN has a much higher default median size (32000) and also has a high background level of transactions (likely due to the ongoing pump). It woould have been extremely easy to increases the median size to around 35-40k where the attack becomes possible. If done carefully it would likely be indisinguishable from normal activity. In fact I wouldn't be surprised if the XDN median has already reached that level due to normal fluctutation without any "attack preparation" at all. In that case an attacker would merely need to lay in wait for the appropriate conditions to occur, and no about of "24/7" would prevent it. Summary is that XDN was more vulnerable, not invulnerable. Furthermore XDN was not the first team to fix the exploit. Not by a wide margin. Sure, now Monero devs can only offer excuses, because of the goal missed in their gates. Truly XMR devs and supporters are not quite adequate. They hate everyone. Very strange community.
|
|
|
Just starting with the XDN GUI wallet, have a question: Received 2 transactions, sum of both shows in pending balance, after 1/2hr still 0 in actual balance. Is it safe to send immature coins right now to an exchange?
1. Use transactions with smaller amounts. If you need big amount, make 2-3-4 transactions. 2. Check your transactions in blockchain. http://chainradar.com/xdn/blocks3. Pending is a balance that is not confirmed yet. 4. You can send only actual balance. 5. First, try small amounts when deposit on exchange. P.S. Always Backup your .wallet or .keys. via Backup feature.
|
|
|
Next week a very major XDN news will be announced.
|
|
|
dNote is English your first language? I mean no offence just trying to understand whats going on.
Me is Privacy Protected:) Ok fair enough, just to be clear before the fix you released could XDN have been attacked the same way as XMR. We know XDN was not attacked but it has been widely spread that all cryptonotes had the same flaw. I will be brief as usual D< : 1. This vulnerability is a double spend vulnerability. 2. This vulnerability is possible only if blockchain split occurs. Can call it fork. 3. Split or fork is possible with long attack preparation and that preparation is visible to those who watch the blockchain. 4. XDN devs watch blockchain 24/7 to avoid that kind of issues. 5. 1->2->3->4-> XDN IS and WAS invulnerable P.S. XDN devs fixed any related issues, and were first team who did that. https://github.com/ducknote/ducknote/commit/e9dcc9825601f5a7b209c78e3a61169ba4f31fbc
|
|
|
dNote is English your first language? I mean no offence just trying to understand whats going on.
Me is Privacy Protected:)
|
|
|
Why would you need fixes? Earlier today you told us you were "not vulnerable." What happened? XDN is not vulnerable like XMR, due to high developers professionalism.
duckNote is not vulnerable for double spend attack, because XDN do not have any blockchain split, but Monero has it for more than 10 hours, that is why: Monero is still vulnerable for double spend attack! ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) Also duckNote devs "fixed" this Monero-Bug more than 2 hours ago.
|
|
|
#XMR #Monero is under massive blockchain attack,that cause unwanted Monero fork. While #Monero devs do not know what is the reason of fault.
The bigger they are, the harder they fall (and the more boring their price gets). We use Big letters to show that our statement important. And Yes you are right, Monero was big, now it is getting smaller. Just announced the fact, and can make it even more smaller for you #XMR #Monero is under massive blockchain attack,that cause unwanted Monero fork. While #Monero devs do not know what is the reason of fault.
|
|
|
#XMR #Monero is under massive blockchain attack,that cause unwanted Monero fork. While #Monero devs do not know what is the reason of fault.
|
|
|
please update the 'CPU only' on the title,Claymore CryptoNote GPU Miner can mine XDN with AMD GPUs.
Done, thank you.
|
|
|
duckNote Network and blockchain works perfect, like a Swiss clockwork. XDN is not vulnerable like XMR, due to high developers professionalism. Also features, that we will announce next week, will be a "killer features" for all cryptocurrency market. All mentioned above will be immediately implemented in new GUI duckNoteWallet.
|
|
|
|