Quote from: ArticMine on May 03, 2018, 02:43:52 PM

Quote from: mnemonicsoup on May 03, 2018, 09:26:45 AM

Quote from: ArticMine on May 03, 2018, 01:27:37 AM

In this case I find the "short", selling XMV from the air drop, even more appealing since MoneroV goes against something I hold very dear in Monero.

So, claiming the MoneroVs in order to dump them is not potentially reducing the privacy of Monero anymore?

One has to use the mitigations provided in version 0.12.x of Monero. https://monero.stackexchange.com/questions/7826/how-can-individuals-safeguard-themselves-and-the-community-against-a-key-reusing/ The objective in both cases is to have at least 6 identical pre fork fake outputs when spending on both chains. There are two cases here.

1) MoneroV XMV
MoneroV will, according to the Monerov developers be supporting the mitigations and have replay protection. So to claim the MoneroV one first spends one Monero to another Monero Wallet one controls, and this is very important, using

Quote

segregate-pre-fork-outputs in monero-wallet-cli or "I will spend on a key reusing fork" in monero-wallet-gui, ensures that spending a pre-fork output only uses pre-fork fake outputs, since spending on both blockchains will moot post-fork outputs.

One should verify the that rings are using pre fork fake outputs before making the spend. Make sure to set the MoneroV fork block to 1564965. Now if one installs the MoneroV software over the now empty Monero wallet it should recognize the shared RingDB; however since the MoneroV software is not available at this point this cannot be verified. There is no rush at this point with claiming the MoneroV. I would wait until one understands how the MoneroV software works before claiming the MoneroV.

2) Monero Original / Classic XMO / XMC
This does not support the mitigation nor does it have replay protection. There is a limited replay protection on the Monero side because of the increase in ring size from 5 to 7. On the other hand because it used the existing version 0.11.x of Monero there is no risk of a malicious back door introduced by the XMO / XMC developers. In this case one has to spend the Monero Original / Classic first. It is imperative that this be done only to a wallet one controls because of the risk of a replay attack on the Monero chain. Furthermore in order to generate the minimum common pre fork outputs I ended up using a large ring size on the Monero Original / Classic. One then has to enter the rings by hand in to the V0.12.x version of Monero and then spend the Monero to a wallet one controls. This locks out the replay attack. One can then spend the Monero Original / Classic.

Thanks for the stackexchange link. Just started reading it, will take time to digest.
I'm getting ready to send some xmr to an exchange. In the event that I decide to claim the monerov later, are there precautions I need to take now with this transaction? My initial impression is that I can go ahead and make the transaction, and that if I need to deal with print_ring and so forth, that comes later.