Upbit delisted Monero(XMR), Dash(DASH), ZCASH(ZEC), Haven(XHV), BitTube(TUBE), PIVX(PIVX) as well end of september which means companies and institution under regulation can't service anonymous cryptocurrencies. If the trends will keep then during the next bubble will be hard to increase price significantly. Maybe some institution don't want to have anonymous coins due to lack of control the customers.
Pasting my reddit comment:
The FATF guidance does not even prevent privacy coins from being listed on an exchange, as long as the exchange enforces KYC/AML for the users. I ascribe the recent events to an overzealous and erroneous interpretation of the guidance by the compliance department of the exchange in question. It further should be noted that, for instance, Binance and Kraken still cater to Korean users. Additionally, see a relevant comment of mine below:
My response to the following article: OKEx Korea delisting all privacy coins, including Monero, Zcash and Dash, as these ‘violate’ FATF’s 'travel rule' - The Block
as these ‘violate’ FATF’s 'travel rule' I don't think this is the case actually. As long as they enforce KYC/AML for each account, they should be able to tie deposits and withdrawals to a certain person. In addition, they can send this information to another service (which is essentially what the travel rule is about) in case a direct withdrawal (i.e. a withdrawal to another service) is made. People should also bear in mind that FATF merely makes recommendations:Importantly, FATF doesn't have *any* regulatory authority of its own. FATF makes recommendations, not laws.
Member countries can adopt all, some, or none of FATF's recommendations. There are basically no repercussions for not adopting (or for violating) FATF recommendations. The U.S. based exchanges will most likely follow FinCEN's guidanceAs you might expect, the United States doesn't really like having its regulatory policy dictated to it by other countries.
FinCEN (the US regulator in charge of AML/CFT regulation) certainly does consider FATF's recommendations, but rarely adopts them wholesale. Which was positive for privacy coins: People often like to purport that Monero will inevitably get banned. However, the new FinCEN guidance is basically inconsistent with that notion. From the CoinCenter article: Section 4.5.3 states that exchanges are not per se banned from using privacy-preserving cryptocurrencies but will need to comply with the same BSA regulations they comply with for typical cryptocurrencies. We believe that this is possible. Exchanges need to know their customers but they do not have a black letter law requirement to know the customers of their customers. In other words, a bank needs to know who you are but they are not obligated to know the name and address of people that you pay using cash you withdraw from your account. https://coincenter.org/entry/fincen-s-new-cryptocurrency-guidance-matches-coin-center-recommendationsThe full twitter thread on FATF's guidance can be read here: https://twitter.com/jchervinsky/status/1142578858589347840EDIT: To add a few more things: [1] Monero is private by default and optionally transparent. There are plenty of tools available in Monero that allow one to be compliant with an auditor. https://monero.stackexchange.com/questions/tagged/auditing[2] Tari Labs is working on an open source framework for listing Monero. https://twitter.com/fluffypony/status/1172832896727638017[3] CoinCenter confirmed in the MoneroKon regulatory panel that almost all exchanges are already mostly compliant with the FATF guidance (because they enforce KYC/AML for each user). [4] Monero is listed on a lot of U.S. based regulated exchages, services, and OTC desks. I made an overview here: https://np.reddit.com/r/xmrtrader/comments/c1zkfu/daily_discussion_tuesday_june_18th/ergqhzs/[5] This only concerns *Korean* users of OKEx.
This subject was also extensively discussed in yesterday's Monero Coffee Chat. I highly recommend watching it: https://www.youtube.com/watch?v=1y0YeTLbYEc |
|
|
|
I haven't really been following the mobile wallet scene. That said, is there currently one (preferably FOSS for Android) that's capable of importing a view-only wallet from monero-gui for primarily montoring incoming transactions/balances in real time while I'm out and about?
 https://www.monerujo.io/Thanks. I'll check it out. I actually installed one of the early releases of Monerujo and explored it a little bit but never got to use it. I don't think the view-only wallet feature was implemented back then. BTW, is a local node option something being considered to be implemented sometime on Monerujo? I mean, Micro SD cards are so cheap nowadays. USB OTG card readers are dirt-cheap as well and very compact nowadays. For the life of me, I just couldn't get my node at home to work (unable to remotely connect); and I've played around with it quite a bit. What kind of error did you incur? |
|
|
|
I have restored my Ledger Nano S seeds on another device. When I try to open the GUI with the new device, I get the following error message after entering the password:
"Couldn't open wallet: Wrong Device Status : SW=6930 (EXPECT=9000, MASK=ffff)"
Why is that?
All works fine with the old device.
What version of the Ledger Monero app is running on the new device? v1.2.2 on the old device (working properly) v1.3.1 on the new device (with the error message) What is the version of the Monero GUI software? Monero GUI software is v0.14.0.0 So any ideas where the problem could come from? I have tried to restaure another old Ledger Nano S on the new Nano S and I have the same error message. Basically the GUI works fine with my two old Ledger but I cannot use the GUI after restauring any of them on my new Ledger. The Monero app version of both old Ledger is 1.2.2 and the version on the new is 1.3.1 (I cannot use the 1.2.2 on the new, because once I restaure the seed I have to install the Monero app through Ledger Manager, and only the last version is available). The Ledger Monero app is currently version sensitive, i.e., you can only run GUI v0.14.0.0 in conjunction with Ledger Monero app v1.2.2. Similarly, you can only run GUI v0.14.1.0 in conjunction with Ledger Monero app v1.3.1. Hopefully this helps. It does help. Thank you. You're welcome. |
|
|
|
I have restored my Ledger Nano S seeds on another device. When I try to open the GUI with the new device, I get the following error message after entering the password:
"Couldn't open wallet: Wrong Device Status : SW=6930 (EXPECT=9000, MASK=ffff)"
Why is that?
All works fine with the old device.
What version of the Ledger Monero app is running on the new device? v1.2.2 on the old device (working properly) v1.3.1 on the new device (with the error message) What is the version of the Monero GUI software? Monero GUI software is v0.14.0.0 So any ideas where the problem could come from? I have tried to restaure another old Ledger Nano S on the new Nano S and I have the same error message. Basically the GUI works fine with my two old Ledger but I cannot use the GUI after restauring any of them on my new Ledger. The Monero app version of both old Ledger is 1.2.2 and the version on the new is 1.3.1 (I cannot use the 1.2.2 on the new, because once I restaure the seed I have to install the Monero app through Ledger Manager, and only the last version is available). The Ledger Monero app is currently version sensitive, i.e., you can only run GUI v0.14.0.0 in conjunction with Ledger Monero app v1.2.2. Similarly, you can only run GUI v0.14.1.0 in conjunction with Ledger Monero app v1.3.1. Hopefully this helps. |
|
|
|
I have restored my Ledger Nano S seeds on another device. When I try to open the GUI with the new device, I get the following error message after entering the password:
"Couldn't open wallet: Wrong Device Status : SW=6930 (EXPECT=9000, MASK=ffff)"
Why is that?
All works fine with the old device.
What version of the Ledger Monero app is running on the new device? v1.2.2 on the old device (working properly) v1.3.1 on the new device (with the error message) What is the version of the Monero GUI software? |
|
|
|
I have restored my Ledger Nano S seeds on another device. When I try to open the GUI with the new device, I get the following error message after entering the password:
"Couldn't open wallet: Wrong Device Status : SW=6930 (EXPECT=9000, MASK=ffff)"
Why is that?
All works fine with the old device.
What version of the Ledger Monero app is running on the new device? |
|
|
|
tell please, why XMR wallet during synchronization, after a while, it ceases to be displayed in Windows, I do not see how many more blocks are left, I think this is not a normal situation  the white rectangle is the wallet window This may be due to the wallet locking. Can you check the wallet lock time on the Settings page? |
|
|
|
Is there a way for Ledger to integrate XMR into Ledger Live without having to store the viewkeys off all their users?
Because if they store them, then US gov agencies will ask them, and those agencies will be able to map a good chunk of XMR distribution.
Behind that lies this important question: is their a way for XMR to become more user friendly without sacrifing privacy? Or will the only way to ensure privacy be forever to run a full node oneself?
They could technically use the GUI's libwallet as library (Monerujo does this for instance), which would result in the wallet being able to connect to a remote node (and thus not having to send the private view key to a server to delegate scanning). I'd argue using a remote node is fairly user friendly. Lastly, note the subtle difference between a light server and a remote node. The former requires the private view key, whereas the latter does not. Are they (Ledger) aware of that? Are there discussions with their technical team and Monero core devs? Because I have talked with the Ledger's guy responsible for coin integration and he told me that they don't want to integrate XMR into Ledger Live because they don't want to store users viewkey. So maybe they don't know how to do it properly. I am not sure. I guess I could contact cslashm and have a chat about it. There have been discussions in the past as far as I know. |
|
|
|
In the OP it’s been said they’re moving away from this forum. Is this now only community based or is a team member still active on the thread as well? Privacy is key and Monero stands for privacy. Monero = key.
There are still developers as well as core-team members active here. Additionally, there's a large and vibrant community on reddit: https://www.reddit.com/r/Monero/Perhaps the OP of the thread requires an update. |
|
|
|
Is there a way for Ledger to integrate XMR into Ledger Live without having to store the viewkeys off all their users?
Because if they store them, then US gov agencies will ask them, and those agencies will be able to map a good chunk of XMR distribution.
Behind that lies this important question: is their a way for XMR to become more user friendly without sacrifing privacy? Or will the only way to ensure privacy be forever to run a full node oneself?
They could technically use the GUI's libwallet as library (Monerujo does this for instance), which would result in the wallet being able to connect to a remote node (and thus not having to send the private view key to a server to delegate scanning). I'd argue using a remote node is fairly user friendly. Lastly, note the subtle difference between a light server and a remote node. The former requires the private view key, whereas the latter does not. |
|
|
|
Hueristic, I respect you, but in recent weeks and months you've been frothing at the mouth.
+1, let's keep it civil. |
|
|
|
They plan to release a desktop version in the foreseeable future.
Do you know when exactly? There is an ETA? In short in 2020 or in 2025? They did not provide an ETA, but I am reasonably certain 2020 is way more likely than 2025 :-P Are you sure? In crypto 2025 is more likely than 2020 generally I deem it more likely that the desktop wallet is out in 2020 than 2025, yes. |
|
|
|
Can one still use this algo to install malware to run on a website so that website visitors mine XMR with the users CPU? Wasn't there any consideration to the algorithm that would negate this specific security issue with XMR and why is this not mentioned in the audit? thanks. Due to the random code generation part of the proof-of-work, a web miner is significantly more difficult to create (though definitely not impossible). Additionally, the 2GB RAM requirement somewhat mitigates the malware issue. |
|
|
|
When will RandomX become the new hashing algorithm?
October (conditional on the last audit successfully completing). |
|
|
|
|
Show Posts
