Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 678. (Read 4670673 times)
February 12, 2016, 02:44:04 PM
Who is Peter Todd: http://www.coindesk.com/video-core-developer-peter-todd-bitcoins-future/ (Bitcoin core developer)
February 12, 2016, 09:54:52 AM
Deserves a crosspost:
Shoutout from Peter Todd on the only altcoin he uses, for privacy reasons of course.
Posted yesterday in bitcoincore slack channel.
Shoutout from Peter Todd on the only altcoin he uses, for privacy reasons of course.
Posted yesterday in bitcoincore slack channel.
February 12, 2016, 04:32:33 AM
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?
Thank you for clarifying. We are looking into it.
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.
February 11, 2016, 09:49:36 PM
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
https://www.youtube.com/watch?v=-FHeXrY65V4
Nice to see you out there Fluffy.
February 11, 2016, 07:11:20 PM
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. February 11, 2016, 05:33:00 PM
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.
SSL Labs says the mentioned website supports HSTS (HTTP Strict Transport Security) as well protection against downgrade protocol attacks and gives an A+ grade.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:
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.
February 11, 2016, 05:27:45 PM
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?
Thank you for clarifying. We are looking into it.
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.
February 11, 2016, 05:05:09 PM
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
https://www.youtube.com/watch?v=-FHeXrY65V4
February 11, 2016, 04:59:22 PM
$ simplewallet --generate-from-view-key 49bPEMu2NiJCDPAvzDDTJCfcRKcdSmB5P3XFbMbw7m1rJt7cotJeFJEZVhTFguYeQ4TNEvPwAbtF5Ps JQ9iEKz8mH2WmQo3:794d99ba442931954d00de76218f62a85692fbffd544590a0f5d913149fed0a:lookwallet
February 11, 2016, 04:54:15 PM
I have synched with blockchain. I am trying to create a watch only wallet to simlplewallet by this command.
It is like
But only this happens.
What should be done?
Quote
--generate-from-view-key 49bPEMu2NiJCDPAvzDDTJCfcRKcdSmB5P3XFbMbw7m1rJt7cotJeFJEZVhTFguYeQ4TNEvPwAbtF5Ps JQ9iEKz8mH2WmQo3:794d99ba442931954d00de76218f62a85692fbffd544590a0f5d913149fed0a:lookwallet
It is like
Quote
--generate-from-view-key address:viewkey:filename
But only this happens.
Quote
[wallet 4AT4qA]: --generate-from-view-key 49bPEMu2NiJCDPAvzDDTJCfcRKcdSmB5P3XFbMbw7m1rJt7cotJeFJEZVhTFguYeQ4TNEvPwAbtF5Ps JQ9iEKz8mH2WmQo3:794d99ba442931954d00de76218f62a85692fbffd544590a0f5d913149fed0a:lookwallet
unknown command: --generate-from-view-key 49bPEMu2NiJCDPAvzDDTJCfcRKcdSmB5P3XFbMbw7m1rJt7cotJeFJEZVhTFguYeQ4TNEvPwAbtF5Ps JQ9iEKz8mH2WmQo3:794d99ba442931954d00de76218f62a85692fbffd544590a0f5d913149fed0a:lookwallet
[wallet 4AT4qA]:
unknown command: --generate-from-view-key 49bPEMu2NiJCDPAvzDDTJCfcRKcdSmB5P3XFbMbw7m1rJt7cotJeFJEZVhTFguYeQ4TNEvPwAbtF5Ps JQ9iEKz8mH2WmQo3:794d99ba442931954d00de76218f62a85692fbffd544590a0f5d913149fed0a:lookwallet
[wallet 4AT4qA]:
What should be done?
February 11, 2016, 01:58:00 PM
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?
Thank you for clarifying. We are looking into it.
February 11, 2016, 09:56:56 AM
** MONERO MISSIVE SPECIAL EDITION - 2015 YEAR IN REVIEW **
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
February 11, 2016, 07:49:24 AM
** MONERO MISSIVE SPECIAL EDITION - 2015 YEAR IN REVIEW **
Super Missive gents. A big thank you to all Core contributors, both past and present ones!
February 11, 2016, 07:42:24 AM
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).
https://shnoe.wordpress.com/2016/02/11/de-anonymizing-shadowcash-and-oz-coin/
Credits to NobleSir (Shen Noether).
February 11, 2016, 07:36:00 AM
Update from Shen Noether regarding Ring CT implementation for Monero. I have to admit I spotted this one a bit late:
Quote
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 )
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:
Quote
I've been working on some other fun stuff this week like multisig, and this https://github.com/ShenNoether/ge_fromfe_writeup
February 10, 2016, 11:29:11 PM
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.
Quote
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.
February 10, 2016, 07:08:14 PM
Peter Todd acknowledging the value of a tail emission:
https://twitter.com/petertoddbtc/status/697532042553065472
EDIT: One should also read the whole conversation, it is an interesting one.
https://twitter.com/petertoddbtc/status/697532042553065472
EDIT: One should also read the whole conversation, it is an interesting one.
February 10, 2016, 06:48:56 PM
Update from Shen Noether regarding Ring CT implementation for Monero. I have to admit I spotted this one a bit late:
Quote
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 )
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 )
February 10, 2016, 05:52:00 PM
Has this been noted?
https://github.com/LMDB/lmdb/commit/fcac8d07742891cedcf94b982e5094315132f62a
Also a Question for Howard Chu, After looking at your code I'm wondering if you had a hand in the original cryptonote code?
BTW, Congrats luigi1111 and ArticMine!!! Your contributions have been immense.
https://github.com/LMDB/lmdb/commit/fcac8d07742891cedcf94b982e5094315132f62a
Also a Question for Howard Chu, After looking at your code I'm wondering if you had a hand in the original cryptonote code?
BTW, Congrats luigi1111 and ArticMine!!! Your contributions have been immense.
February 10, 2016, 11:46:22 AM
** MONERO MISSIVE SPECIAL EDITION - 2015 YEAR IN REVIEW **
Best missive yet IMHO. Great update, and great work from the devs. I'm sure other will join me in saying thanks to David and eizh, and congratulations to luigi1111 and ArticMine. The project is in good hands.
In for the long haul.
Q
Jump to: