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

[MirkoIta]

Why people sell XMR when bitcoin up?

Because people sell every alts and even their mothers and children when bitcoin goes up lol

[1713970027]

1713970027

[1713970027]

1713970027

[1713970027]

1713970027

[1713970027]

1713970027

[Hueristic]

when i want to install thei windows 64bit GUI wallet it crashes (that means it stops the current step with the result that no wallet is installed) always in different installation steps. Anyone has the same problem?

Are you overclocking? Sounds like you have an unstable system. BTW There is no install for the x64 release so maybe you downloaded a virus? Did you check the hash?

[visdude]

Initial questions:

1. Is the wallet name shown somewhere on the GUI?
2. Is there a way to determine the corresponding mixin# for each of the privacy levels on the GUI?

I most likely have more questions but I'll wait until after I get the chance to explore it thoroughly (still in the midst of syncing). Otherwise, it's a very nice interface. Kudos to the devs/contributors.

[dEBRUYNE]

Initial questions:

1. Is the wallet name shown somewhere on the GUI?
2. Is there a way to determine the corresponding mixin# for each of the privacy levels on the GUI?

I most likely have more questions but I'll wait until after I get the chance to explore it thoroughly (still in the midst of syncing). Otherwise, it's a very nice interface. Kudos to the devs/contributors.

[1] Only in the wizard as far as I know.

[2] Mixin levels are as follows:

4,5,6,7,8,9,10,11,12,13,14,15,20,25

Where 4 = low, 8 = medium, and 25 = high.

[CryptoRambler]

Initial questions:

1. Is the wallet name shown somewhere on the GUI?
2. Is there a way to determine the corresponding mixin# for each of the privacy levels on the GUI?

I most likely have more questions but I'll wait until after I get the chance to explore it thoroughly (still in the midst of syncing). Otherwise, it's a very nice interface. Kudos to the devs/contributors.

[1] Only in the wizard as far as I know.

[2] Mixin levels are as follows:

4,5,6,7,8,9,10,11,12,13,14,15,20,25

Where 4 = low, 8 = medium, and 25 = high.

Thanks dEBRUYNE, is 4 the forced minimum mixin for every transaction?

I thought that a forced mixin of 2 makes input "completely" unlinkable/untraceable.. Thanks

[dEBRUYNE]

Initial questions:

1. Is the wallet name shown somewhere on the GUI?
2. Is there a way to determine the corresponding mixin# for each of the privacy levels on the GUI?

I most likely have more questions but I'll wait until after I get the chance to explore it thoroughly (still in the midst of syncing). Otherwise, it's a very nice interface. Kudos to the devs/contributors.

[1] Only in the wizard as far as I know.

[2] Mixin levels are as follows:

4,5,6,7,8,9,10,11,12,13,14,15,20,25

Where 4 = low, 8 = medium, and 25 = high.

Thanks dEBRUYNE, is 4 the forced minimum mixin for every transaction?

I thought that a forced mixin of 2 makes input "completely" unlinkable/untraceable.. Thanks

2 is the minimum enforced mixin, but monero-wallet-cli and monero-wallet-gui use 4 as minimum. The Monero Research Lab recommends 4, but also recommend a bump in increments (0 -> 2 -> 4). A minimum enforced mixin of 2 prevents chain reactions (with respect to traceability). in Monero that are detrimental to privacy. See:

https://lab.getmonero.org/pubs/MRL-0001.pdf

Note that Monero is cryptographically untraceable and unlinkable.

[novag]

Tell me please what a commission when sending 500 Monero, from the exchange on the wallet, and again on the stock exchange?

[BobBarker]

I posted a short video on YouTube of me clicking around the beta 1 GUI release. It's not any sort of comprehensive review, just an example to show people if they wanted to see the GUI in action: https://www.youtube.com/watch?v=S45yZMcvQvo

[CryptoRambler]

I posted a short video on YouTube of me clicking around the beta 1 GUI release. It's not any sort of comprehensive review, just an example to show people if they wanted to see the GUI in action: https://www.youtube.com/watch?v=S45yZMcvQvo

Nice job with the video BobBarker! I haven't tried the wallet yet. It it looks fast, glad to hear with full command line functionality from the get go.

With daemon running in the background, did you have to wait to sync blockchain when opening up GUI?

Thanks again, XMR making strides to compete in digital world 😁

[MoneroMooo]

To all pool operators:

If you haven't already, you will need to update the node-cryptonote-util software in order for your pool to cross the january fork. I think many of the pool ops have done so already, but for those who are not in #monero-pools, you will need this patch: https://paste.fedoraproject.org/506116/17116821/

This applies to zone117x's version of the pool. There is a version of this ported to clintar's fork, which I don't have handy right now, but I will post it when I do is here: https://github.com/M5M400/node-cryptonote-util/commit/37f50f9b535f0258c3a1c6f7247a891b4c211ff3.

If you're not running this when the fork happens, you will be forked off.

For pool miners, you may want to check with your pool op that they're running the patch a few days before the fork, and switch to a known good pool otherwise. Please prefer smaller pools when doing so.

[visdude]

I think for XMR to gain significant traction/adoption, a user-friendly, secure mobile wallet app in addition to the upcoming GUI release is a must. This will allow users to transact on-the-go (retail payments, P2P trading/exchange, etc.). It would also be valuable to be able to run a local node with it (though I could never get the current Android node PoC to work on my device) or at least the ability to connect to a private and secure "personal" remote node (i.e. running at home).

Jaxx mobile wallet is being worked on. https://twitter.com/jaxx_io/status/808352133129113600

But it's proprietary and connects to a remote node that they control, no?

[visdude]

Initial questions:

1. Is the wallet name shown somewhere on the GUI?
2. Is there a way to determine the corresponding mixin# for each of the privacy levels on the GUI?

I most likely have more questions but I'll wait until after I get the chance to explore it thoroughly (still in the midst of syncing). Otherwise, it's a very nice interface. Kudos to the devs/contributors.

[1] Only in the wizard as far as I know.

[2] Mixin levels are as follows:

4,5,6,7,8,9,10,11,12,13,14,15,20,25

Where 4 = low, 8 = medium, and 25 = high.

Thanks for the reply and info:

[1] It would be nice to have the current/active wallet or account name on the GUI though as most users most likely maintain more than one wallet/account. It just makes sense.

[2] Again, it would be nice to correlate each privacy level/steps with the corresponding mixin count on the GUI to eliminate guesswork and for the sake of user-friendliness.

[visdude]

2 is the minimum enforced mixin, but monero-wallet-cli and monero-wallet-gui use 4 as minimum. The Monero Research Lab recommends 4, but also recommend a bump in increments (0 -> 2 -> 4). A minimum enforced mixin of 2 prevents chain reactions (with respect to traceability). in Monero that are detrimental to privacy. See:

https://lab.getmonero.org/pubs/MRL-0001.pdf

Note that Monero is cryptographically untraceable and unlinkable.

Currently, monero-wallet-cli allows 2 in contrast with the GUI's minimum of 4 (the slider cannot go below 4 or "low"). If a minimum mixin of 4 is going to be enforced moving forward for obvious reasons and eventually do away with 2, then I can understand.

[MoneroMooo]

Currently, monero-wallet-cli allows 2 in contrast with the GUI's minimum of 4 (the slider cannot go below 4 or "low"). If a minimum mixin of 4 is going to be enforced moving forward for obvious reasons and eventually do away with 2, then I can understand.

In the september fork, the minimum mixin will increase to 4.

[dEBRUYNE]

2 is the minimum enforced mixin, but monero-wallet-cli and monero-wallet-gui use 4 as minimum. The Monero Research Lab recommends 4, but also recommend a bump in increments (0 -> 2 -> 4). A minimum enforced mixin of 2 prevents chain reactions (with respect to traceability). in Monero that are detrimental to privacy. See:

https://lab.getmonero.org/pubs/MRL-0001.pdf

Note that Monero is cryptographically untraceable and unlinkable.

Currently, monero-wallet-cli allows 2 in contrast with the GUI's minimum of 4 (the slider cannot go below 4 or "low"). If a minimum mixin of 4 is going to be enforced moving forward for obvious reasons and eventually do away with 2, then I can understand.

Only via RPC as far as I know. It uses 4 by default (should have said that instead of minimum).

[dEBRUYNE]

Initial questions:

1. Is the wallet name shown somewhere on the GUI?
2. Is there a way to determine the corresponding mixin# for each of the privacy levels on the GUI?

I most likely have more questions but I'll wait until after I get the chance to explore it thoroughly (still in the midst of syncing). Otherwise, it's a very nice interface. Kudos to the devs/contributors.

[1] Only in the wizard as far as I know.

[2] Mixin levels are as follows:

4,5,6,7,8,9,10,11,12,13,14,15,20,25

Where 4 = low, 8 = medium, and 25 = high.

Thanks for the reply and info:

[1] It would be nice to have the current/active wallet or account name on the GUI though as most users most likely maintain more than one wallet/account. It just makes sense.

[2] Again, it would be nice to correlate each privacy level/steps with the corresponding mixin count on the GUI to eliminate guesswork and for the sake of user-friendliness.

[1] Agreed, I'll open an issue for it on Github later.

[2] That may look the slider a bit too crowded. Additionally, the mixin # is already shown in the confirmation window.

[dEBRUYNE]

PSA: Users, (solo)miners, exchanges/merchants, and pool operators must be on v0.10.1 in advance of the hardfork otherwise you will get forked/booted off the network. Miners, please contact your pool operator to ask them if they have upgraded

https://www.reddit.com/r/Monero/comments/5ke2y2/psa_users_solominers_exchangesmerchants_and_pool/

[visdude]

Initial questions:

1. Is the wallet name shown somewhere on the GUI?
2. Is there a way to determine the corresponding mixin# for each of the privacy levels on the GUI?

I most likely have more questions but I'll wait until after I get the chance to explore it thoroughly (still in the midst of syncing). Otherwise, it's a very nice interface. Kudos to the devs/contributors.

[1] Only in the wizard as far as I know.

[2] Mixin levels are as follows:

4,5,6,7,8,9,10,11,12,13,14,15,20,25

Where 4 = low, 8 = medium, and 25 = high.

Thanks for the reply and info:

[1] It would be nice to have the current/active wallet or account name on the GUI though as most users most likely maintain more than one wallet/account. It just makes sense.

[2] Again, it would be nice to correlate each privacy level/steps with the corresponding mixin count on the GUI to eliminate guesswork and for the sake of user-friendliness.

[1] Agreed, I'll open an issue for it on Github later.

[2] That may look the slider a bit too crowded. Additionally, the mixin # is already shown in the confirmation window.

[1] Thanks.

[2] If you meant a "confirmation window" just before sending a transaction, I wasn't aware of it as I haven't tried it yet but it's good to know that it allows one to review transaction details (including mixin count) before sending it out.


Edit (addendum):

Nevertheless, acting on or making a decision based on an actual data (mixin number) is more direct and positive than an abstraction of it (low, medium, high) which presents the actual data after the fact (confirmation window). But that's just me.

[visdude]

More observations, thoughts and questions regarding GUI.

When I opened an existing watch-only CLI "<walletname>.keys" file with its corresponding "<walletname>" cache file in GUI, all transactions up to the point when it was last synced in CLI showed up in GUI History (new ones after the import/switch to GUI showed up as well). This process also created an additional "<walletname>.unportable" file in the wallet folder. The release notes specifically stated that CLI wallet cache files are incompatible with GUI but it seems to be fine...unless I'm missing something.

Similarly, an existing DB created/synced with the CLI method (standalone monerod) that I opened in GUI also created an additional "p2pstate.bin.unportable" file in the DB folder.

[1] What are these additional ".unportable" files generated after opening existing CLI wallet/cache and DB files in GUI respectively? A wallet and DB created/synced fresh from scratch within GUI do not generate such ".unportable" files. Just curious.

[2] In what way is an existing CLI wallet cache file incompatible with GUI per release notes (considering that transaction history did show up in GUI as I stated above)? I am a bit confused.

Though I used a "watch-only" wallet for this test, I couldn't find any indication of it on the GUI whatsoever (no wallet name and/or status). The only way I was able to sort of verify that it's indeed a watch-only wallet was by clicking on "Show seed" (password protected) in Settings which did not display the mnemonic seed. It would be very helpful to show the name and status or type of the active/current wallet on the GUI.

[3] Will the cold/offline wallet creation be incorporated into the GUI and simplified for the not-so-tech-savvy users or will that remain a relatively complicated CLI function?

[4] Will there eventually be an offline transaction signing functionality in conjunction with the cold/offline wallet feature (as in Armory, etc.)? Otherwise, it defeats the purpose of having a cold/offline wallet in the first place only to eventually make it "hot" (put online) to be able to spend from it (and consequently moving the remaining balance to a new unexposed cold wallet), thereby making it vulnerable to attacks. It's such a complicated procedure that can be alleviated with an offline transaction signing feature.

[ku4eto]

Seems like CPU mining Monero supports only SSE2 and AES, there doesn't seem to be support yet for AVX, AVX2 or SSE4.1. Are they planned or not?