[XMR] Monero - A secure, private, untraceable cryptocurrency

[hyc]

Has this been noted?

https://github.com/LMDB/lmdb/commit/fcac8d07742891cedcf94b982e5094315132f62a

Not really significant. In testing, we were never even able to construct an invalid pathname that would fail the utf8_to_utf16 function, so in practice that error branch can never get executed. And even if it did, in Monero code the program would just quit - it can't run without a valid DB pathname.

Also a Question for Howard Chu, After looking at your code I'm wondering if you had a hand in the original cryptonote code?

Nope. Besides, unlike original cryptonote, my code is actually documented.

[1713421261]

1713421261

[1713421261]

1713421261

[1713421261]

1713421261

[1713421261]

1713421261

[dEBRUYNE]

Update from Shen Noether regarding Ring CT implementation for Monero. I have to admit I spotted this one a bit late:

edit 2/3/2016:

Python version of all checkpoints: https://github.com/ShenNoether/MiniNero/blob/master/RingCT2.py

(You can run this with https://github.com/ShenNoether/MiniNero/blob/master/RCTUnitTests.py )

C++ version of all checkpoints:

https://github.com/ShenNoether/RingCT/blob/master/rctSigs.cpp

(You can run this with https://github.com/ShenNoether/RingCT/blob/master/Test.cpp )

In addition, Shen Noether posted this on reddit:

I've been working on some other fun stuff this week like multisig, and this https://github.com/ShenNoether/ge_fromfe_writeup

[dEBRUYNE]

Broken Crypto in Shadowcash and OZ-coin:

https://shnoe.wordpress.com/2016/02/11/de-anonymizing-shadowcash-and-oz-coin/

Credits to NobleSir (Shen Noether).

[myagui]

** MONERO MISSIVE SPECIAL EDITION - 2015 YEAR IN REVIEW **

https://getmonero.org/2016/02/10/monero-missive-2015-year-in-review.html

Super Missive gents. A big thank you to all Core contributors, both past and present ones!

[silencesilence]

** MONERO MISSIVE SPECIAL EDITION - 2015 YEAR IN REVIEW **

https://getmonero.org/2016/02/10/monero-missive-2015-year-in-review.html

Super Missive gents. A big thank you to all Core contributors, both past and present ones!

and the price rises because of old monero-missive 2015 is here ..... no logic for me he he he 

[equipoise]

My blockchain got corrupted when the electricity stopped. I resynced from scratch and it took about 24 hours. Previously I resynced from scratch a few times on the same machine on the same USB3 external hdd and on the same internet connection for 1-3 hours (it was on bitmonerod 0.9.0 tagged and before tagged, not 0.9.1). What could be the issue with the slow sync this time?

I'm not sure I'm understanding. Are you using the same version as before?

What CPU do you have?

I'm using 0.9.1 now. Previous times I was using 0.9.0 tagged and previous version (0.9.0 before tagged). Windows 7 64x. Mobile Core I7 (4 cores, 8 logical cores, 6 MB cash, with AES-NI).

Thank you for clarifying. We are looking into it.

I ran 0.9.1 again and it got to block 135000 in 43 minutes and block 270000 in 2 hours and 25 minutes. Then i checked my .bat file and the "--db-sync-mode fastest:async:10000" option was missing (fastest:async:1000 is the default and I'm using 10000, but it seems I deleted it by mistake). Then I started it again with the option added and it got to 135000 in 17 minutes and to 646069 in 2 hours and 25 minutes. That was the speed I experienced with 0.9 beta2. I hope I didn't alerted all the dev team. Great missive and great dev team. Congratulations to the new members. Keep the good work going.

[pönde]

I have synched with blockchain. I am trying to create a watch only wallet to simlplewallet by this command.

--generate-from-view-key 49bPEMu2NiJCDPAvzDDTJCfcRKcdSmB5P3XFbMbw7m1rJt7cotJeFJEZVhTFguYeQ4TNEvPwAbtF5Ps JQ9iEKz8mH2WmQo3:794d99ba442931954d00de76218f62a85692fbffd544590a0f5d913149fed0a:lookwallet

It is like

--generate-from-view-key address:viewkey:filename

But only this happens.

[wallet 4AT4qA]: --generate-from-view-key 49bPEMu2NiJCDPAvzDDTJCfcRKcdSmB5P3XFbMbw7m1rJt7cotJeFJEZVhTFguYeQ4TNEvPwAbtF5Ps JQ9iEKz8mH2WmQo3:794d99ba442931954d00de76218f62a85692fbffd544590a0f5d913149fed0a:lookwallet
unknown command: --generate-from-view-key 49bPEMu2NiJCDPAvzDDTJCfcRKcdSmB5P3XFbMbw7m1rJt7cotJeFJEZVhTFguYeQ4TNEvPwAbtF5Ps JQ9iEKz8mH2WmQo3:794d99ba442931954d00de76218f62a85692fbffd544590a0f5d913149fed0a:lookwallet
[wallet 4AT4qA]:

What should be done?

[smooth]

$ simplewallet --generate-from-view-key 49bPEMu2NiJCDPAvzDDTJCfcRKcdSmB5P3XFbMbw7m1rJt7cotJeFJEZVhTFguYeQ4TNEvPwAbtF5Ps JQ9iEKz8mH2WmQo3:794d99ba442931954d00de76218f62a85692fbffd544590a0f5d913149fed0a:lookwallet

[dEBRUYNE]

Monero: Moving Ever-Nearer Perfect Privacy - A brief interview with core-team member fluffypony: (by the Daily Decrypt)

https://www.youtube.com/watch?v=-FHeXrY65V4

[smooth]

My blockchain got corrupted when the electricity stopped. I resynced from scratch and it took about 24 hours. Previously I resynced from scratch a few times on the same machine on the same USB3 external hdd and on the same internet connection for 1-3 hours (it was on bitmonerod 0.9.0 tagged and before tagged, not 0.9.1). What could be the issue with the slow sync this time?

I'm not sure I'm understanding. Are you using the same version as before?

What CPU do you have?

I'm using 0.9.1 now. Previous times I was using 0.9.0 tagged and previous version (0.9.0 before tagged). Windows 7 64x. Mobile Core I7 (4 cores, 8 logical cores, 6 MB cash, with AES-NI).

Thank you for clarifying. We are looking into it.

I ran 0.9.1 again and it got to block 135000 in 43 minutes and block 270000 in 2 hours and 25 minutes. Then i checked my .bat file and the "--db-sync-mode fastest:async:10000" option was missing (fastest:async:1000 is the default and I'm using 10000, but it seems I deleted it by mistake). Then I started it again with the option added and it got to 135000 in 17 minutes and to 646069 in 2 hours and 25 minutes. That was the speed I experienced with 0.9 beta2. I hope I didn't alerted all the dev team. Great missive and great dev team. Congratulations to the new members. Keep the good work going.

Thank you for the follow up. We're going to take a look at whether there is a better default for the parameter, although higher numbers increase memory usage, so it may not be best for everyone to increase it.

[nachoig]

WARNING: Always check you're using https when connecting to xmr.to, a malicious TOR exit node made a victim already.

Somebody was recently scammed of a significant amount of XMRs when he tried to use XMR.TO over TOR.
After a little investigation, we found out what happened: the TOR exit node was malicious, and created an order going to a different address than that requested by the victim. The victim payed the XMR, but never got the BTC, as they were sent by XMR.TO to the scammer address. XMR.TO had no way to know something wrong was going on.
This type of man-in-the-middle attack is not possible when you use https connection. What the exit node did is to downgrade the connection to a normal http, and sadly the victim must not have noticed the lack of secured connection in his browser.

The malicious exit node has the IP 109.201.154.186.

Be safe: ALWAYS check within your browser that your connection is secure when you connect to XMR.TO. If it's just http, that's a phishing version and you're not talking to XMR.TO directly.

This should always look like this:

SSL Labs says the mentioned website supports HSTS (HTTP Strict Transport Security) as well protection against downgrade protocol attacks and gives an A+ grade.

However, it isn't on the HTTPS Everywhere list ( https://www.eff.org/https-everywhere/atlas/?xmr.to ). Probably it would be a good idea to add that as well other Monero related websites. Since Tor Browser has this extension built-in, this could be helpful to avoid this type of incident again.

[binaryFate]

SSL Labs says the mentioned website supports HSTS (HTTP Strict Transport Security) as well protection against downgrade protocol attacks and gives an A+ grade.

Thank you for the check and report. It's always welcome, we really take privacy seriously.

However, it isn't on the HTTPS Everywhere list ( https://www.eff.org/https-everywhere/atlas/?xmr.to ). Probably it would be a good idea to add that as well other Monero related websites. Since Tor Browser has this extension built-in, this could be helpful to avoid this type of incident again.

Right. We're right now applying to the various pre-loaded HSTS lists. However, realistically it will take probably several months before being visible in production  browsers.

[Hueristic]

Monero: Moving Ever-Nearer Perfect Privacy - A brief interview with core-team member fluffypony: (by the Daily Decrypt)

https://www.youtube.com/watch?v=-FHeXrY65V4

Nice to see you out there Fluffy. 

[equipoise]

My blockchain got corrupted when the electricity stopped. I resynced from scratch and it took about 24 hours. Previously I resynced from scratch a few times on the same machine on the same USB3 external hdd and on the same internet connection for 1-3 hours (it was on bitmonerod 0.9.0 tagged and before tagged, not 0.9.1). What could be the issue with the slow sync this time?

I'm not sure I'm understanding. Are you using the same version as before?

What CPU do you have?

I'm using 0.9.1 now. Previous times I was using 0.9.0 tagged and previous version (0.9.0 before tagged). Windows 7 64x. Mobile Core I7 (4 cores, 8 logical cores, 6 MB cash, with AES-NI).

Thank you for clarifying. We are looking into it.

I ran 0.9.1 again and it got to block 135000 in 43 minutes and block 270000 in 2 hours and 25 minutes. Then i checked my .bat file and the "--db-sync-mode fastest:async:10000" option was missing (fastest:async:1000 is the default and I'm using 10000, but it seems I deleted it by mistake). Then I started it again with the option added and it got to 135000 in 17 minutes and to 646069 in 2 hours and 25 minutes. That was the speed I experienced with 0.9 beta2. I hope I didn't alerted all the dev team. Great missive and great dev team. Congratulations to the new members. Keep the good work going.

Thank you for the follow up. We're going to take a look at whether there is a better default for the parameter, although higher numbers increase memory usage, so it may not be best for everyone to increase it.

That's what I expected too, but trying with 1000, 10000, 25000 and 100000 I can't see overall difference in RAM usage on my 16GB RAM system. It's using about 1 GB RAM on my system during sync with each option and most of it is shareable. After sync it's using 500 MB. The private working set (not shareable) is just 36-50 MB on my system. Also on my system there is a good speed improvement between 1000 and 10000, but going to 25000 and 100000 doesn't improve the speed more and it stays the same.

[dEBRUYNE]

Deserves a crosspost:

Shoutout from Peter Todd on the only altcoin he uses, for privacy reasons of course.

Posted yesterday in bitcoincore slack channel.

[Wekkel]

Who is Peter Todd: http://www.coindesk.com/video-core-developer-peter-todd-bitcoins-future/ (Bitcoin core developer)

[iCEBREAKER]

Deserves a crosspost:

Shoutout from Peter Todd on the only altcoin he uses, for privacy reasons of course.

Posted yesterday in bitcoincore slack channel.

Heh, that's nice.  Good to see The Todd refuting the Gavinista's "u just want Bitcoin to die because u hav so many Evil VIA" canard.

How did hostfat react to the mention of Monero?

I hope he took it badly.   

[canth]

Deserves a crosspost:

Shoutout from Peter Todd on the only altcoin he uses, for privacy reasons of course.

Posted yesterday in bitcoincore slack channel.

Heh, that's nice.  Good to see The Todd refuting the Gavinista's "u just want Bitcoin to die because u hav so many Evil VIA" canard.

How did hostfat react to the mention of Monero?

I hope he took it badly.  

Ha - no response to the Monero mention. I think we all like Bitcoin and have high hopes that eventually it gains some level of privacy, but given the size of confidential transactions and the willingness of the community to add new semi-controversial features, it's not likely to compete with Monero anytime soon. No matter our opinions on the roadmap, there's a fuckload of work needing to be done on SW, LN, sidechains, eventual block size increase, etc. They've got a ton on their plate and that's without tackling mining centralization and privacy.

[dEBRUYNE]

A new subreddit, I think the intention is to make it somewhat similiar to r/bitcoinmarkets:

https://www.reddit.com/r/moneromarket/

[Bagatell]

Bitco.in forum has also just started a new sub. Monero just made the cut at 17 out of 18 cyrptos deemed worthy of attention.

https://bitco.in/forum/threads/alternative-cryptocurrency-discussion.882/