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

[Chicken_76]

zero
I think I may know the issue. The monero-wallet-cli.exe always starts by asking the name of the wallet. At the time I created the wallet (months ago), I recorded the 25 word seed. I didn't know the wallet name mattered. So, when I give it a name, it's not the correct name and then it wants to create a new wallet.

Now the question: Is there a way to recover without having the wallet name?

Look in that folder for files ending in .keys
Those are what you need to access your funds.
For example, if there's a file abc123.keys, you would load the wallet like this:

Code:

monero-wallet-cli.exe --wallet-file abc123

Do this for every .keys file you find and check their balance until you find in which wallet your funds are.

[rickgejr]

Anybody know if this is legitimate?

http://www.pop-coin.co

Not secure. Hidden.

Another XMR Website miner?

[luksbit]

At the moment, investing in XMR is better than bitcoin. There are so many types of bitcoin and it makes investors confused.

What would be your justification for such a statement? I still believe that Bitcoin is still the most reliable investment medium

[TheFuzzStone]

Coглaceн Moнepo oчeнь пepcпeктивнaя мoнeткa, и eё нyжнo имeть в cвoём пopтфeлe

Этo aнглoязычнaя вeткa.

So please go here. If you need additional info in russian language, check our local forum.

[revelacaogr]

warning

PSA: LocalMonero.com has been acquired by a competitor and the competitor is now using it to redirect all traffic to their own site. This is unethical and almost certainly illegal. We've attempted to rectify this situation peacefully but the competitor is refusing to cooperate. Details inside.
by Alex_LocalMoneroLocalMonero Staff

EDIT: We will no longer be replying to this thread, we need to get back to work on the site. Thanks for all the support!
Who are you?

LocalMonero! We've been around for about 3 months and position ourselves to be the Monero equivalent of LocalBitcoins. Many members of the Monero community here on reddit have had experiences with us and so far most people seem to think we're OK.
Can you give me some background on this situation?

LocalMonero is operating from the domain localmonero.co, since we weren't able to acquire the localmonero.com due to being unable to reach the owner of that domain at that time. At that point in time (and even after our August 25 launch) that page had no content, it was parked or squatted by someone.
On August 25th, 2017, LocalMonero officially launched, and this is considered to be the date of establishment in commercial use, protecting our trademark in common law jurisdictions.
On September 5th, 2017 (10 days after our launch), we've noticed that localmonero.com now put up an pre-announcement page, inviting people to leave their email to be notified on localmonero.com's launch. Here's that page archived.
Obviously, we got worried, and so we immediately also applied for an EU trademark just in case (since EU isn't common law, and in EU trademark law the first to apply are the ones who get the trademark protection, and not the ones who first establish a brand in commercial use). Thankfully, we were the first to apply, no other "LocalMonero" trademark existed when we submitted our application. We've also attempted to contact the owners of localmonero.com once again, to no avail.
On November 16th, 2017 (~2.5 months after our launch), localmonero.com's registration updated, possibly indicating a new owner..........

https://np.reddit.com/r/Monero/comments/7g5vhi/psa_localmonerocom_has_been_acquired_by_a/

[pönde]

I am using monero v0.11.1.0 on Linux Ubuntu


I created a full wallet with CLI. It took about 4 minutes to sync with remote node.

I created a view only wallet with CLI. It will take maybe an hour to sync with remote node.

I created a full wallet with GUI. It took about 7 minutes to sync with remote node.

I created a view only wallet with GUI it will take maybe many hours to sync with remote node.


Why there is such a huge difference sync time?


Anyway when I sync any of those wallets to localhost, to the blockchain on my own laptop, the sync seems to be very fast. Just a few minutes. Then only the blockchain sync to other nodes takes time, but it has to be done from scratch only once.

[Kanahide]

At the moment, investing in XMR is better than bitcoin. There are so many types of bitcoin and it makes investors confused.

Why not invest in both?
I like the reality of bitcoin reaching 100k or even more than that.
Its always good to have just one bitcoin, im always amazed at the new All time highs its reaching.
This shows us that we are at the very begining, more people realize the potential of the cryptoworld. Im really interessed in what highs monero, bitcoin and deeponion will reach.
Those are my maincoins. i hope they will explode even more
regards

[Coindgr]

This is all temporary. Kovri is under heavy development and once released will make all of this obsolete.

                           
Is the Kovri going to run under TOR? or does it have a different method?

[Andretti83]

This is all temporary. Kovri is under heavy development and once released will make all of this obsolete.

                           
Is the Kovri going to run under TOR? or does it have a different method?

I2P

[sgjenks01]

zero
I think I may know the issue. The monero-wallet-cli.exe always starts by asking the name of the wallet. At the time I created the wallet (months ago), I recorded the 25 word seed. I didn't know the wallet name mattered. So, when I give it a name, it's not the correct name and then it wants to create a new wallet.

Now the question: Is there a way to recover without having the wallet name?

For example, if there's a file abc123.keys, you would load the wallet like this:

Code:

monero-wallet-cli.exe --wallet-file abc123

Do this for every .keys file you find and check their balance until you find in which wallet your funds are.

I found a .keys file with a date stamp from May, which is when I would have set up the wallet. When I used the wallet name to start wallet-cli, it asked for a password and I gave it the password I had used in May and the wallet opened, showing no balance. I tried rescan_bc and it came back with zero balance.

Unless you have another idea, I think I'm sunk.

[Hueristic]

This is all temporary. Kovri is under heavy development and once released will make all of this obsolete.

                           
Is the Kovri going to run under TOR? or does it have a different method?

From what I understand the Korvi devs are working directly with I2P dev team and are contributing to both. Thats a pretty good feeling if your worried about the end result.

[Anon136]

This is all temporary. Kovri is under heavy development and once released will make all of this obsolete.

                         
Is the Kovri going to run under TOR? or does it have a different method?

Garlic routing:  is a variant of Onion routing that encrypts multiple messages together to make it more difficult for attackers to perform traffic analysis. To protect the identity of the sender, messages are encrypted multiple times with the public keys of selected nodes on the network. To be delivered the encrypted packets must be received by routers selected by the sender, in the order specified by the sender. Differently from Onion routing an encrypted packet ("onion") can contain multiple packets ("cloves") with different destinations, and the sender is not required to specify a return path for the message.

Garlic routing is a modest improvement over onion routing but it will probably always be difficult to achieve high levels of privacy in a network where messages must ultimately, at some point, be location addressed. To really truly get private networks we will probably need breakthroughs in physics not computer science. But hey you know, if privacy is really really important to you, you can always make sure your location doesn't identify you personally. The proverbial don't shit where you eat.

[Hueristic]

This is all temporary. Kovri is under heavy development and once released will make all of this obsolete.

                         
Is the Kovri going to run under TOR? or does it have a different method?

From what I understand the Korvi devs are working directly with I2P dev team and are contributing to both. Thats a pretty good feeling if your worried about the end result.

Garlic routing:  is a variant of Onion routing that encrypts multiple messages together to make it more difficult for attackers to perform traffic analysis. To protect the identity of the sender, messages are encrypted multiple times with the public keys of selected nodes on the network. To be delivered the encrypted packets must be received by routers selected by the sender, in the order specified by the sender. Differently from Onion routing an encrypted packet ("onion") can contain multiple packets ("cloves") with different destinations, and the sender is not required to specify a return path for the message.

Garlic routing is a modest improvement over onion routing but it will probably always be difficult to achieve privacy in a network where messages must ultimately, at some point, be location addressed. To really truly get private networks we will probably need breakthroughs in physics not computer science.

Security through obscurity has always been a poor choice but in some systems without a complete rewrite at the base layer there really isn't that much of a choice. There are projects doing that but I haven't kept up on them for over 10 years or so, there was a Swedish team (IIRC) that had written a base protocol but I'm not sure of the adoption.

[Anon136]

This is all temporary. Kovri is under heavy development and once released will make all of this obsolete.

                         
Is the Kovri going to run under TOR? or does it have a different method?

From what I understand the Korvi devs are working directly with I2P dev team and are contributing to both. Thats a pretty good feeling if your worried about the end result.

Garlic routing:  is a variant of Onion routing that encrypts multiple messages together to make it more difficult for attackers to perform traffic analysis. To protect the identity of the sender, messages are encrypted multiple times with the public keys of selected nodes on the network. To be delivered the encrypted packets must be received by routers selected by the sender, in the order specified by the sender. Differently from Onion routing an encrypted packet ("onion") can contain multiple packets ("cloves") with different destinations, and the sender is not required to specify a return path for the message.

Garlic routing is a modest improvement over onion routing but it will probably always be difficult to achieve privacy in a network where messages must ultimately, at some point, be location addressed. To really truly get private networks we will probably need breakthroughs in physics not computer science.

Security through obscurity has always been a poor choice but in some systems without a complete rewrite at the base layer there really isn't that much of a choice. There are projects doing that but I haven't kept up on them for over 10 years or so, there was a Swedish team (IIRC) that had written a base protocol but I'm not sure of the adoption.

I think kovri plus sending sensitive transactions from a public wifi and not your home will be all the security any normal person needs. Good enough for government work.

Do let me know if you come up with the name of that project. Interested.

[Hueristic]

This is all temporary. Kovri is under heavy development and once released will make all of this obsolete.

                         
Is the Kovri going to run under TOR? or does it have a different method?

From what I understand the Korvi devs are working directly with I2P dev team and are contributing to both. Thats a pretty good feeling if your worried about the end result.

Garlic routing:  is a variant of Onion routing that encrypts multiple messages together to make it more difficult for attackers to perform traffic analysis. To protect the identity of the sender, messages are encrypted multiple times with the public keys of selected nodes on the network. To be delivered the encrypted packets must be received by routers selected by the sender, in the order specified by the sender. Differently from Onion routing an encrypted packet ("onion") can contain multiple packets ("cloves") with different destinations, and the sender is not required to specify a return path for the message.

Garlic routing is a modest improvement over onion routing but it will probably always be difficult to achieve privacy in a network where messages must ultimately, at some point, be location addressed. To really truly get private networks we will probably need breakthroughs in physics not computer science.

Security through obscurity has always been a poor choice but in some systems without a complete rewrite at the base layer there really isn't that much of a choice. There are projects doing that but I haven't kept up on them for over 10 years or so, there was a Swedish team (IIRC) that had written a base protocol but I'm not sure of the adoption.

I think kovri plus sending sensitive transactions from a public wifi and not your home will be all the security any normal person needs. Good enough for government work.

Do let me know if you come up with the name of that project. Interested.

Will do, sometimes things will just randomly pop back up in my memory. Lol

I found this on a quick search but it's not the one I was referring to.

https://www.cisco.com/c/en/us/about/press/internet-protocol-journal/back-issues/table-contents-53/143-trill.html

It sits on the LLC/ODI layer but might be on the NDIS and replaces the LLC layer, I'll search more later.

Edit: dammit getting sidetracked lol.

[Globb0]

This is all temporary. Kovri is under heavy development and once released will make all of this obsolete.

                         
Is the Kovri going to run under TOR? or does it have a different method?

Garlic routing:  is a variant of Onion routing that encrypts multiple messages together to make it more difficult for attackers to perform traffic analysis. To protect the identity of the sender, messages are encrypted multiple times with the public keys of selected nodes on the network. To be delivered the encrypted packets must be received by routers selected by the sender, in the order specified by the sender. Differently from Onion routing an encrypted packet ("onion") can contain multiple packets ("cloves") with different destinations, and the sender is not required to specify a return path for the message.

Garlic routing is a modest improvement over onion routing but it will probably always be difficult to achieve high levels of privacy in a network where messages must ultimately, at some point, be location addressed. To really truly get private networks we will probably need breakthroughs in physics not computer science. But hey you know, if privacy is really really important to you, you can always make sure your location doesn't identify you personally. The proverbial don't shit where you eat.

Some interesting ideas and stuff like peer to peer networks that appear and disappear between close together devices, like mobile phones. Data that hop to and from the destination never seeing a "core" network could be interesting.

[Hueristic]

This is all temporary. Kovri is under heavy development and once released will make all of this obsolete.

                         
Is the Kovri going to run under TOR? or does it have a different method?

Garlic routing:  is a variant of Onion routing that encrypts multiple messages together to make it more difficult for attackers to perform traffic analysis. To protect the identity of the sender, messages are encrypted multiple times with the public keys of selected nodes on the network. To be delivered the encrypted packets must be received by routers selected by the sender, in the order specified by the sender. Differently from Onion routing an encrypted packet ("onion") can contain multiple packets ("cloves") with different destinations, and the sender is not required to specify a return path for the message.

Garlic routing is a modest improvement over onion routing but it will probably always be difficult to achieve high levels of privacy in a network where messages must ultimately, at some point, be location addressed. To really truly get private networks we will probably need breakthroughs in physics not computer science. But hey you know, if privacy is really really important to you, you can always make sure your location doesn't identify you personally. The proverbial don't shit where you eat.

Some interesting ideas and stuff like peer to peer networks that appear and disappear between close together devices, like mobile phones. Data that hop to and from the destination never seeing a "core" network could be interesting.

I don't think that is possible. LLC/ODI is pretty mandatory but could be enhanced I guess. I haven't thought of this stuff since the 90/s

Edited because I'm an idiot that forgets the layer structure and forgets ODI and substitutes OSI.

[Chicken_76]

I found a .keys file with a date stamp from May, which is when I would have set up the wallet. When I used the wallet name to start wallet-cli, it asked for a password and I gave it the password I had used in May and the wallet opened, showing no balance. I tried rescan_bc and it came back with zero balance.

Unless you have another idea, I think I'm sunk.

OK, here are some theories of what might have happened:

1. Maybe someone got hold of your wallet file or seed and withdrew your monero from your wallet. (people get hacked from time to time)
When you typed rescan_bc, did you see funds coming in and then going out? Each transaction will be listed one per line, with incoming funds as green and outgoing funds as purple. Each line will have the block number, from which you can tell when that transaction took place.

2. Maybe you have another wallet, that's saved in a different folder. Issue a search in all your drives for .keys files (and don't forget to include hidden folders in the search)

3. Maybe there's something wrong with your daemon or your blockchain copy. In the monerod window type 'diff' and post here the number it outputs for BH.

You said earlier something about a mnemonic seed. Do you still have it?

[dEBRUYNE]

I found a .keys file with a date stamp from May, which is when I would have set up the wallet. When I used the wallet name to start wallet-cli, it asked for a password and I gave it the password I had used in May and the wallet opened, showing no balance. I tried rescan_bc and it came back with zero balance.

Unless you have another idea, I think I'm sunk.

OK, here are some theories of what might have happened:

1. Maybe someone got hold of your wallet file or seed and withdrew your monero from your wallet. (people get hacked from time to time)
When you typed rescan_bc, did you see funds coming in and then going out? Each transaction will be listed one per line, with incoming funds as green and outgoing funds as purple. Each line will have the block number, from which you can tell when that transaction took place.

2. Maybe you have another wallet, that's saved in a different folder. Issue a search in all your drives for .keys files (and don't forget to include hidden folders in the search)

3. Maybe there's something wrong with your daemon or your blockchain copy. In the monerod window type 'diff' and post here the number it outputs for BH.

You said earlier something about a mnemonic seed. Do you still have it?

To add, you can use show_transfers in monero-wallet-cli to get a list of your incoming and outgoing transactions.

[darasinmi4show]

How did window related to you project?