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

[aiwe]

Supposedly this is a 5-qubit bitslice processor, hence scalable, although not yet proven by scaling in practice: http://arxiv.org/abs/1603.04512

QC is coming, gradually at first, then quite suddenly.  It really is time to panic, before the suddenly phase.

What effect does quantum computing have on ECDSA and EdDSA is the question.

Both will be broken by it as far as I know. Interestingly, since Satoshi's pubkey is revealed, he has to move this coins in order to "protect" them (i.e. quantum computing will make it possible to steal them).

Since they are traceable, how moving them will protect them?

He will have to move them into Monero of course.

That's what I wanted to hear

[1714202861]

1714202861

[1714202861]

1714202861

[1714202861]

1714202861

[hudd]

I keep seeing similar messages like this, does it mean those connected nodes were not upgraded for the hard fork ?

Code:

Sync data returned unknown top block: 1012266 -> 1009962 [2304 blocks (-1 days) ahead] 

[nioc]

I keep seeing similar messages like this, does it mean those connected nodes were not upgraded for the hard fork ?

Code:

Sync data returned unknown top block: 1012266 -> 1009962 [2304 blocks (-1 days) ahead] 

As I understand it yes.

Those messages usually go away after I get a message that a particular node has been blocked.  6 different IPs have been blocked since I restarted my node 11 hours ago.  Last one was blocked 7 minutes ago.

[smooth]

I keep seeing similar messages like this, does it mean those connected nodes were not upgraded for the hard fork ?

Code:

Sync data returned unknown top block: 1012266 -> 1009962 [2304 blocks (-1 days) ahead] 

As I understand it yes.

Those messages usually go away after I get a message that a particular node has been blocked.  6 different IPs have been blocked since I restarted my node 11 hours ago.  Last one was blocked 7 minutes ago.

Correct.

[smooth]

Protect them from being stolen. If the pubkey is revealed quantum computing is able to steal his coins. If you move them to a new address it won't reveal the pubkey of that address, unless you reuse it.

OK, I went and read about it. So, they can't break new 'unused' address, but still they will know that money were moved and now lay at that address. Am I right?

Yes that's right. Also the protection only exists while the address are sitting unspent on the blockchain. When you try to spend you have to reveal the public key so QC could still be used to break it during the interval until it is confirmed. That greatly narrows the time window (from years to minutes) and would require a faster QC to be effective.

The comments about moving to Monero (maybe in jest?) are off-base. Monero would also be broken by QC and we don't have the protection of publishing hashes of public keys either.

[ShapeShift.io]

UPDATE! Monero is back up on ShapeShift. So sorry for the delay. Buy or sell XMR instantly with ShapeShift: https://shapeshift.io/?pair=btc_xmr

[mathgal23]

UPDATE! Monero is back up on ShapeShift. So sorry for the delay. Buy or sell XMR instantly with ShapeShift: https://shapeshift.io/?pair=btc_xmr

Thank you for the update. Please consider adding more CryptoNote coins soon to provide an alternative to the XMR trading pair markets at Poloniex (which is still missing AEON arguable the 2nd most active CryptoNote community after XMR).

I would suggest AEON, BBR and DSH as the 3 XMR trading pairs likely to receive the most interest from the XMR community.

[dEBRUYNE]

Protect them from being stolen. If the pubkey is revealed quantum computing is able to steal his coins. If you move them to a new address it won't reveal the pubkey of that address, unless you reuse it.

OK, I went and read about it. So, they can't break new 'unused' address, but still they will know that money were moved and now lay at that address. Am I right?

Yes that's right. Also the protection only exists while the address are sitting unspent on the blockchain. When you try to spend you have to reveal the public key so QC could still be used to break it during the interval until it is confirmed. That greatly narrows the time window (from years to minutes) and would require a faster QC to be effective.

The comments about moving to Monero (maybe in jest?) are off-base. Monero would also be broken by QC and we don't have the protection of publishing hashes of public keys either.

Interestingly, Zcash notes a few quantum resistant possibilities (cryptography wise) that will still preserve your privacy. In the case that QC breaks Monero we could always switch to such cryptography. Quantum resistant cryptography usually has some trade-offs too, like huge transaction size and very inefficient transactions if I recall correctly.

[dEBRUYNE]

on my wallet i tried sweep_dust and transfer 100xmr all failed.

There is a known issue with sweep_dust sometimes not working. That is being addressed in a future update.

As far as the other, we're taking a look at your log file, but GingerAle's suggestion about going on IRC is a good one. Sometimes it is best to be able to ask questions and try things in real time.

I have a wallet that has been around for a long time and have synced every once in a while.  I received an error when I first ran the bc_height command, but the second time I tried it, it ran and went through all the blocks and that was good to see. But now I have the dust fee problem.

I tried to sweep a small bit of dust from my wallet, it seems that it did not go through, so now there is a 0.02 fee that is stuck in outgoing. Is there a way to remove it or will it go away? I also tried to sweep it again because it showed dust still there, but it errored. Does it even matter?  It's just there in outgoing now for hours.

Also the 0.9.3 doesn't refresh automatically or in the background that I could see, but typing refresh does it. Can it auto refresh? kind of a good thing, like it did before with previous versions it is good to see it sync and then check your balance.

As far as I know 0.9.3 should auto refresh. As far as asking a bunch of specific questions about your wallet the best bet is to jump onto freenode IRC #monero and ask on there.

There are definitely some known issues with sweep dust. In most cases, I would suggest waiting for an update.

This board is available to search and documents the answers, so why ask to go to #monero? 

0.9.3 doesn't refresh, so why is that?  This could be a problem where your coins are stolen and since it doesn't refresh, you may think they are still there, right? Is there a bug or is there a problem with my wallet?

I can live with the dust problem. Can someone answer my question about the stuck fee for dust?

Will this fix it?

Sometimes, your funds will become stuck - you will have some locked funds that never become unlocked. This is how you fix it.

Load your wallet in simplewallet.

Type

seed

into the command prompt. Write down your 25 word seed, if you haven't already. This is the best way to make sure you don't loose access to your funds.
Close simplewallet by typing

exit

Backup all of your wallet related files. These include:

yourwalletname.bin
yourwalletname.bin.keys
yourwalletname.bin.address.txt

This can be done by copying the files to a new folder.

Sometimes, when creating your wallet, you might have named it something without the .bin part. In that case, the wallet file will be called yourwalletname without the .bin at the end.

Delete yourwallet.bin


Load simplewallet, type in the name of the wallet you just deleted


Enter password. The wallet will now refresh and hopefully your locked funds will now become unlocked.

Like I said, the bug was introduced in 9.1 and subsequently patched in 9.3. However, if you incurred the bug in 9.1 it will still be present in 9.3, because the daemon will still think some of the key images are already spent and therefore you cannot spend the funds. This requires a rescan to fix. I am not sure why we need documentary for this. Bear in mind that most of the people working on Monero are volunteers and in my personal opinion the time that would be needed for this could be spend better.

Regarding refresh, autorefresh should work in 9.3. However, in case it doesn't work what is wrong with just typing refresh?

[vvrroomm]

Concerning sweep_dust errors, it can be due to tiny inputs for which there is no enough inputs to mixin with.

Trying to sweep_dust, daemon says: 

Code:

Tx <...> has too low mixin (0), and more than one mixable input with unmixable inputs.

For example, when I am trying to send some xmr that left on my hot wallet, most of which consists of dust gives me an error:

Code:

Error: not enough outputs for specified mixin_count = 4:
output amount = 0.003811120000, found outputs to mix = 1
output amount = 0.007507490000, found outputs to mix = 1
output amount = 0.007723640000, found outputs to mix = 1
output amount = 0.003594340000, found outputs to mix = 2
output amount = 0.003064900000, found outputs to mix = 1
........  and so on....

Ok thanks for the information. 

I thought my fee of 0.02 was stuck, but it appears it went through. Looking further into what was being displayed in the command show_transfers, it appears that I incurred a 0.02 transfer fee for the attempt to sweep_dust, but my dust did not get swept, because I had too little. I thought it was stuck or maybe would return to my wallet since the sweep didn't work, but show_transfers  displays the in and out of your wallet. With all the mixing it appears that my dust was too low and couldn't be done and I still got charged the fee.  Oh well, I guess I should just make a note to leave the dust alone until it builds up quite a bit so it can make the transfer. Chalk it up as a part of the cost of the security that is in Monero.

[vvrroomm]

on my wallet i tried sweep_dust and transfer 100xmr all failed.

There is a known issue with sweep_dust sometimes not working. That is being addressed in a future update.

As far as the other, we're taking a look at your log file, but GingerAle's suggestion about going on IRC is a good one. Sometimes it is best to be able to ask questions and try things in real time.

I have a wallet that has been around for a long time and have synced every once in a while.  I received an error when I first ran the bc_height command, but the second time I tried it, it ran and went through all the blocks and that was good to see. But now I have the dust fee problem.

I tried to sweep a small bit of dust from my wallet, it seems that it did not go through, so now there is a 0.02 fee that is stuck in outgoing. Is there a way to remove it or will it go away? I also tried to sweep it again because it showed dust still there, but it errored. Does it even matter?  It's just there in outgoing now for hours.

Also the 0.9.3 doesn't refresh automatically or in the background that I could see, but typing refresh does it. Can it auto refresh? kind of a good thing, like it did before with previous versions it is good to see it sync and then check your balance.

As far as I know 0.9.3 should auto refresh. As far as asking a bunch of specific questions about your wallet the best bet is to jump onto freenode IRC #monero and ask on there.

There are definitely some known issues with sweep dust. In most cases, I would suggest waiting for an update.

This board is available to search and documents the answers, so why ask to go to #monero? 

0.9.3 doesn't refresh, so why is that?  This could be a problem where your coins are stolen and since it doesn't refresh, you may think they are still there, right? Is there a bug or is there a problem with my wallet?

I can live with the dust problem. Can someone answer my question about the stuck fee for dust?

Will this fix it?

Sometimes, your funds will become stuck - you will have some locked funds that never become unlocked. This is how you fix it.

Load your wallet in simplewallet.

Type

seed

into the command prompt. Write down your 25 word seed, if you haven't already. This is the best way to make sure you don't loose access to your funds.
Close simplewallet by typing

exit

Backup all of your wallet related files. These include:

yourwalletname.bin
yourwalletname.bin.keys
yourwalletname.bin.address.txt

This can be done by copying the files to a new folder.

Sometimes, when creating your wallet, you might have named it something without the .bin part. In that case, the wallet file will be called yourwalletname without the .bin at the end.

Delete yourwallet.bin


Load simplewallet, type in the name of the wallet you just deleted


Enter password. The wallet will now refresh and hopefully your locked funds will now become unlocked.

Like I said, the bug was introduced in 9.1 and subsequently patched in 9.3. However, if you incurred the bug in 9.1 it will still be present in 9.3, because the daemon will still think some of the key images are already spent and therefore you cannot spend the funds. This requires a rescan to fix. I am not sure why we need documentary for this. Bear in mind that most of the people working on Monero are volunteers and in my personal opinion the time that would be needed for this could be spend better.

Regarding refresh, autorefresh should work in 9.3. However, in case it doesn't work what is wrong with just typing refresh?

In trying to find out about what happened in my sweep_dust, I did a rescan and everything in my wallet appears good.  I have made a note to run the refresh every time I open my wallet now, an auto refresh would be nice, not a big deal.  I don't open the 'ol wallet too much I'm going to hold and pray it hits out of the solar system, I have a feeling secure money is smart money.

[saddambitcoin]

Easy way to change your payment ID via API for increased privacy.

poloniex-new-address
https://github.com/PsychicCat/poloniex-new-address

[qgmurugan007]

Easy way to change your payment ID via API for increased privacy.

poloniex-new-address
https://github.com/PsychicCat/poloniex-new-address

Nice tool. Will be using it.Thanks.

[LucyLovesCrypto]

Easy way to change your payment ID via API for increased privacy.

poloniex-new-address
https://github.com/PsychicCat/poloniex-new-address

Nice tool. Will be using it.Thanks.

Thank you. This is indeed helpful but it is a shame that Poloniex forces users to use an API to accomplish this simple task

[smooth]

Easy way to change your payment ID via API for increased privacy.

poloniex-new-address
https://github.com/PsychicCat/poloniex-new-address

Nice tool. Will be using it.Thanks.

Thank you. This is indeed helpful but it is a shame that Poloniex forces users to use an API to accomplish this simple task

Please politely ask poloniex to support integrated addresses which are automatically encrypted on the blockchain (and would reduce their support costs from people forgetting to use a payment ID)

[GingerAle]

Monerodo For Sale.

250 XMR + shipping. 250 hashes / sec. Runs monero core, monero pool server, nvidia mining software. 1 tb HDD.

Upgrade available done at market price (for example, SSD). International shipping available.

https://forum.getmonero.org/3/merchants-and-marketplace/2518/monerodo-2-taffeta-model

[aiwe]

Protect them from being stolen. If the pubkey is revealed quantum computing is able to steal his coins. If you move them to a new address it won't reveal the pubkey of that address, unless you reuse it.

OK, I went and read about it. So, they can't break new 'unused' address, but still they will know that money were moved and now lay at that address. Am I right?

Yes that's right. Also the protection only exists while the address are sitting unspent on the blockchain. When you try to spend you have to reveal the public key so QC could still be used to break it during the interval until it is confirmed. That greatly narrows the time window (from years to minutes) and would require a faster QC to be effective.

The comments about moving to Monero (maybe in jest?) are off-base. Monero would also be broken by QC and we don't have the protection of publishing hashes of public keys either.

Of course we were jocking.  I read an article by Vitalik Buterin concerning QC and there were mentioned Lamport Signatures as a solution.

And thank you for explanation! I wonder how do you guys have so much time and patience answering all this and that here and on reddit and elsewhere. That's amazing.

[dEBRUYNE]

Protect them from being stolen. If the pubkey is revealed quantum computing is able to steal his coins. If you move them to a new address it won't reveal the pubkey of that address, unless you reuse it.

OK, I went and read about it. So, they can't break new 'unused' address, but still they will know that money were moved and now lay at that address. Am I right?

Yes that's right. Also the protection only exists while the address are sitting unspent on the blockchain. When you try to spend you have to reveal the public key so QC could still be used to break it during the interval until it is confirmed. That greatly narrows the time window (from years to minutes) and would require a faster QC to be effective.

The comments about moving to Monero (maybe in jest?) are off-base. Monero would also be broken by QC and we don't have the protection of publishing hashes of public keys either.

Of course we were jocking.  I read an article by Vitalik Buterin concerning QC and there were mentioned Lamport Signatures as a solution.

Alternatively winterwitz signatures, both are really inefficient at the moment though.

[dEBRUYNE]

Monero added to Cryptopia:

https://www.cryptopia.co.nz/Exchange/?market=XMR_BTC

[elrippo]

Monero added to Cryptopia:

https://www.cryptopia.co.nz/Exchange/?market=XMR_BTC

Yeeeeeaaaahhhhhhh