October 15, 2024, 12:33:31 AM

Welcome, Guest

News: Latest Bitcoin Core release: 28.0 [Torrent]

Bitcoin Forum>Alternate cryptocurrencies>Announcements (Altcoins)

Pages:

Author

Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 620. (Read 4670673 times)

vvrroomm

newbie

Activity: 53

Merit: 0

Quote from: dEBRUYNE on March 25, 2016, 07:52:52 PM

Quote from: vvrroomm on March 25, 2016, 07:46:33 PM

Quote from: smooth on March 25, 2016, 07:41:55 PM

Quote from: vvrroomm on March 25, 2016, 07:40:51 PM

Quote from: damashup on March 25, 2016, 07:26:03 PM

Quote from: smooth on March 25, 2016, 07:09:44 PM

Quote from: luigi1111 on March 25, 2016, 07:06:30 PM

Quote from: damashup on March 25, 2016, 02:47:16 PM

Quote from: luigi1111 on March 25, 2016, 02:30:44 PM

Quote from: damashup on March 25, 2016, 02:13:21 PM

Changing the mixin hasn't helped. Still getting the same error. Could there be another issue?

Can you set your daemon log level to 1 and try again? It should give more details.

Thanks. According to the log the tx has "used already spent key images".

I'm going to follow the steps set out here (assuming they are still valid):

Quote from: smooth on March 31, 2015, 03:34:44 PM

1. Delete poolstate.bin and restart node (also move/rename wallet .bin file again)
2. Make sure you have the current version
3. Make sure you are connected to the network with print_cn (daemon command)
4. Wait 24 hours and try again

Ok, so you may need to run "rescan_spent" in simplewallet as well as the above steps.

Yes to clarify a bit the above "try again" had some context which included rescanning the wallet.

Great thanks this worked. Only I refreshed the wallet, rather than rescanned. Didn't wait 24hrs though (life's too short).

This is good that there is a process for fixing these issues, please make an effort to have a place for Monero owners to find out how to fix problems like this. Yes, I know it is on bitcointalk.org message board now in this post, but shouldn't it have been somewhere for someone to find before now?

Quick question also: When I ran simplewallet on earlier versions, it went through a process after synching the daemon, where it would go through the blocks. Mine doesn't do that anymore on the latest version. My balance does show ok. Is this normal? It's hard to tell if everything is working ok if you don't send monero very often.

The scanning is in the background now. You don't have to wait for it, but newly received coins won't appear right away, until the scan reaches them.

This is good to know. I know you guys are really busy coding and everything, sorry to be a bit of a nag on the documentation, I like to know how to do something, before I know I need to know how to do something.

The bug is inherent to the 9.1 version of Hydrogen Helix and is patched in 9.3 already. Therefore, I think it's a bit redundant to include it in the documentation.

Ok, I thought this was just the new way the simplewallet worked, I didn't know it was a bug that was fixed, so you are right. I need to upgrade to 9.3.

dEBRUYNE

legendary

Legendary level

Activity: 2268

Merit: 1141

Quote from: vvrroomm on March 25, 2016, 07:46:33 PM

Quote from: smooth on March 25, 2016, 07:41:55 PM

Quote from: vvrroomm on March 25, 2016, 07:40:51 PM

Quote from: damashup on March 25, 2016, 07:26:03 PM

Quote from: smooth on March 25, 2016, 07:09:44 PM

Quote from: luigi1111 on March 25, 2016, 07:06:30 PM

Quote from: damashup on March 25, 2016, 02:47:16 PM

Quote from: luigi1111 on March 25, 2016, 02:30:44 PM

Quote from: damashup on March 25, 2016, 02:13:21 PM

Changing the mixin hasn't helped. Still getting the same error. Could there be another issue?

Can you set your daemon log level to 1 and try again? It should give more details.

Thanks. According to the log the tx has "used already spent key images".

I'm going to follow the steps set out here (assuming they are still valid):

Quote from: smooth on March 31, 2015, 03:34:44 PM

1. Delete poolstate.bin and restart node (also move/rename wallet .bin file again)
2. Make sure you have the current version
3. Make sure you are connected to the network with print_cn (daemon command)
4. Wait 24 hours and try again

Ok, so you may need to run "rescan_spent" in simplewallet as well as the above steps.

Yes to clarify a bit the above "try again" had some context which included rescanning the wallet.

Great thanks this worked. Only I refreshed the wallet, rather than rescanned. Didn't wait 24hrs though (life's too short).

This is good that there is a process for fixing these issues, please make an effort to have a place for Monero owners to find out how to fix problems like this. Yes, I know it is on bitcointalk.org message board now in this post, but shouldn't it have been somewhere for someone to find before now?

Quick question also: When I ran simplewallet on earlier versions, it went through a process after synching the daemon, where it would go through the blocks. Mine doesn't do that anymore on the latest version. My balance does show ok. Is this normal? It's hard to tell if everything is working ok if you don't send monero very often.

The scanning is in the background now. You don't have to wait for it, but newly received coins won't appear right away, until the scan reaches them.

This is good to know. I know you guys are really busy coding and everything, sorry to be a bit of a nag on the documentation, I like to know how to do something, before I know I need to know how to do something.

The bug is inherent to the 9.1 version of Hydrogen Helix and is patched in 9.3 already. Therefore, I think it's a bit redundant to include it in the documentation.

vvrroomm

newbie

Activity: 53

Merit: 0

Quote from: smooth on March 25, 2016, 07:41:55 PM

Quote from: vvrroomm on March 25, 2016, 07:40:51 PM

Quote from: damashup on March 25, 2016, 07:26:03 PM

Quote from: smooth on March 25, 2016, 07:09:44 PM

Quote from: luigi1111 on March 25, 2016, 07:06:30 PM

Quote from: damashup on March 25, 2016, 02:47:16 PM

Quote from: luigi1111 on March 25, 2016, 02:30:44 PM

Quote from: damashup on March 25, 2016, 02:13:21 PM

Changing the mixin hasn't helped. Still getting the same error. Could there be another issue?

Can you set your daemon log level to 1 and try again? It should give more details.

Thanks. According to the log the tx has "used already spent key images".

I'm going to follow the steps set out here (assuming they are still valid):

Quote from: smooth on March 31, 2015, 03:34:44 PM

1. Delete poolstate.bin and restart node (also move/rename wallet .bin file again)
2. Make sure you have the current version
3. Make sure you are connected to the network with print_cn (daemon command)
4. Wait 24 hours and try again

Ok, so you may need to run "rescan_spent" in simplewallet as well as the above steps.

Yes to clarify a bit the above "try again" had some context which included rescanning the wallet.

Great thanks this worked. Only I refreshed the wallet, rather than rescanned. Didn't wait 24hrs though (life's too short).

This is good that there is a process for fixing these issues, please make an effort to have a place for Monero owners to find out how to fix problems like this. Yes, I know it is on bitcointalk.org message board now in this post, but shouldn't it have been somewhere for someone to find before now?

Quick question also: When I ran simplewallet on earlier versions, it went through a process after synching the daemon, where it would go through the blocks. Mine doesn't do that anymore on the latest version. My balance does show ok. Is this normal? It's hard to tell if everything is working ok if you don't send monero very often.

The scanning is in the background now. You don't have to wait for it, but newly received coins won't appear right away, until the scan reaches them.

This is good to know. I know you guys are really busy coding and everything, sorry to be a bit of a nag on the documentation, I like to know how to do something, before I know I need to know how to do something.

smooth

legendary

Legendary level

Activity: 2968

Merit: 1198

Quote from: vvrroomm on March 25, 2016, 07:40:51 PM

Quote from: damashup on March 25, 2016, 07:26:03 PM

Quote from: smooth on March 25, 2016, 07:09:44 PM

Quote from: luigi1111 on March 25, 2016, 07:06:30 PM

Quote from: damashup on March 25, 2016, 02:47:16 PM

Quote from: luigi1111 on March 25, 2016, 02:30:44 PM

Quote from: damashup on March 25, 2016, 02:13:21 PM

Changing the mixin hasn't helped. Still getting the same error. Could there be another issue?

Can you set your daemon log level to 1 and try again? It should give more details.

Thanks. According to the log the tx has "used already spent key images".

I'm going to follow the steps set out here (assuming they are still valid):

Quote from: smooth on March 31, 2015, 03:34:44 PM

1. Delete poolstate.bin and restart node (also move/rename wallet .bin file again)
2. Make sure you have the current version
3. Make sure you are connected to the network with print_cn (daemon command)
4. Wait 24 hours and try again

Ok, so you may need to run "rescan_spent" in simplewallet as well as the above steps.

Yes to clarify a bit the above "try again" had some context which included rescanning the wallet.

Great thanks this worked. Only I refreshed the wallet, rather than rescanned. Didn't wait 24hrs though (life's too short).

This is good that there is a process for fixing these issues, please make an effort to have a place for Monero owners to find out how to fix problems like this. Yes, I know it is on bitcointalk.org message board now in this post, but shouldn't it have been somewhere for someone to find before now?

Quick question also: When I ran simplewallet on earlier versions, it went through a process after synching the daemon, where it would go through the blocks. Mine doesn't do that anymore on the latest version. My balance does show ok. Is this normal? It's hard to tell if everything is working ok if you don't send monero very often.

The scanning is in the background now. You don't have to wait for it, but newly received coins won't appear right away, until the scan reaches them.

vvrroomm

newbie

Activity: 53

Merit: 0

Quote from: damashup on March 25, 2016, 07:26:03 PM

Quote from: smooth on March 25, 2016, 07:09:44 PM

Quote from: luigi1111 on March 25, 2016, 07:06:30 PM

Quote from: damashup on March 25, 2016, 02:47:16 PM

Quote from: luigi1111 on March 25, 2016, 02:30:44 PM

Quote from: damashup on March 25, 2016, 02:13:21 PM

Changing the mixin hasn't helped. Still getting the same error. Could there be another issue?

Can you set your daemon log level to 1 and try again? It should give more details.

Thanks. According to the log the tx has "used already spent key images".

I'm going to follow the steps set out here (assuming they are still valid):

Quote from: smooth on March 31, 2015, 03:34:44 PM

1. Delete poolstate.bin and restart node (also move/rename wallet .bin file again)
2. Make sure you have the current version
3. Make sure you are connected to the network with print_cn (daemon command)
4. Wait 24 hours and try again

Ok, so you may need to run "rescan_spent" in simplewallet as well as the above steps.

Yes to clarify a bit the above "try again" had some context which included rescanning the wallet.

Great thanks this worked. Only I refreshed the wallet, rather than rescanned. Didn't wait 24hrs though (life's too short).

This is good that there is a process for fixing these issues, please make an effort to have a place for Monero owners to find out how to fix problems like this. Yes, I know it is on bitcointalk.org message board now in this post, but shouldn't it have been somewhere for someone to find before now?

Quick question also: When I ran simplewallet on earlier versions, it went through a process after synching the daemon, where it would go through the blocks. Mine doesn't do that anymore on the latest version. My balance does show ok. Is this normal? It's hard to tell if everything is working ok if you don't send monero very often.

damashup

sr. member

Activity: 259

Merit: 250

Quote from: smooth on March 25, 2016, 07:09:44 PM

Quote from: luigi1111 on March 25, 2016, 07:06:30 PM

Quote from: damashup on March 25, 2016, 02:47:16 PM

Quote from: luigi1111 on March 25, 2016, 02:30:44 PM

Quote from: damashup on March 25, 2016, 02:13:21 PM

Changing the mixin hasn't helped. Still getting the same error. Could there be another issue?

Can you set your daemon log level to 1 and try again? It should give more details.

Thanks. According to the log the tx has "used already spent key images".

I'm going to follow the steps set out here (assuming they are still valid):

Quote from: smooth on March 31, 2015, 03:34:44 PM

1. Delete poolstate.bin and restart node (also move/rename wallet .bin file again)
2. Make sure you have the current version
3. Make sure you are connected to the network with print_cn (daemon command)
4. Wait 24 hours and try again

Ok, so you may need to run "rescan_spent" in simplewallet as well as the above steps.

Yes to clarify a bit the above "try again" had some context which included rescanning the wallet.

Great thanks this worked. Only I refreshed the wallet, rather than rescanned. Didn't wait 24hrs though (life's too short).

smooth

legendary

Legendary level

Activity: 2968

Merit: 1198

Quote from: luigi1111 on March 25, 2016, 07:06:30 PM

Quote from: damashup on March 25, 2016, 02:47:16 PM

Quote from: luigi1111 on March 25, 2016, 02:30:44 PM

Quote from: damashup on March 25, 2016, 02:13:21 PM

Changing the mixin hasn't helped. Still getting the same error. Could there be another issue?

Can you set your daemon log level to 1 and try again? It should give more details.

Thanks. According to the log the tx has "used already spent key images".

I'm going to follow the steps set out here (assuming they are still valid):

Quote from: smooth on March 31, 2015, 03:34:44 PM

1. Delete poolstate.bin and restart node (also move/rename wallet .bin file again)
2. Make sure you have the current version
3. Make sure you are connected to the network with print_cn (daemon command)
4. Wait 24 hours and try again

Ok, so you may need to run "rescan_spent" in simplewallet as well as the above steps.

Yes to clarify a bit the above "try again" had some context which included rescanning the wallet.

luigi1111

legendary

Legendary level

Activity: 1105

Merit: 1000

Quote from: damashup on March 25, 2016, 02:47:16 PM

Quote from: luigi1111 on March 25, 2016, 02:30:44 PM

Quote from: damashup on March 25, 2016, 02:13:21 PM

Changing the mixin hasn't helped. Still getting the same error. Could there be another issue?

Can you set your daemon log level to 1 and try again? It should give more details.

Thanks. According to the log the tx has "used already spent key images".

I'm going to follow the steps set out here (assuming they are still valid):

Quote from: smooth on March 31, 2015, 03:34:44 PM

1. Delete poolstate.bin and restart node (also move/rename wallet .bin file again)
2. Make sure you have the current version
3. Make sure you are connected to the network with print_cn (daemon command)
4. Wait 24 hours and try again

Ok, so you may need to run "rescan_spent" in simplewallet as well as the above steps. I'd recommend just running "flush_txpool" in the daemon console first (and resending the transaction) before trying any of the above.

damashup

sr. member

Activity: 259

Merit: 250

Quote from: LucyLovesCrypto on March 25, 2016, 03:28:21 PM

Quote from: damashup on March 25, 2016, 03:04:09 PM

Quote from: smfuser on March 25, 2016, 02:52:12 PM

Quote from: damashup on March 25, 2016, 02:47:16 PM

Silly question but where can the wallet .bin file be found on Mac OS X? There is a file with the same name as the wallet in the user/[username] directory however the file doesn't have an extension. Should I be moving/ renaming this?

I think the wallet file name won't have a .bin extension unless you specify it when creating it.

Ah yes thanks... I remember now (it's been almost two years since I last created one!)

Nice to see you posting here. It seems like many former BBR supporters are not getting more involved with XMR and or AEON. Are you still working on popboolr? Any way you could adapt something like that for Monero?

Less of the 'former'... I'm still very much behind Boolberry. Been away from Crypto as I've recently found out my wife is expecting another little one, so everything else has been put on the back burner.

I've always held a little stash of Monero... even if getting my hands on it can prove tricky at times!

Good to see both XMR and BBR joining the 'rise of the alts'!

vvrroomm

newbie

Activity: 53

Merit: 0

Quote from: damashup on March 25, 2016, 02:47:16 PM

Quote from: luigi1111 on March 25, 2016, 02:30:44 PM

Quote from: damashup on March 25, 2016, 02:13:21 PM

Changing the mixin hasn't helped. Still getting the same error. Could there be another issue?

Can you set your daemon log level to 1 and try again? It should give more details.

Thanks. According to the log the tx has "used already spent key images".

I'm going to follow the steps set out here (assuming they are still valid):

Quote from: smooth on March 31, 2015, 03:34:44 PM

1. Delete poolstate.bin and restart node (also move/rename wallet .bin file again)
2. Make sure you have the current version
3. Make sure you are connected to the network with print_cn (daemon command)
4. Wait 24 hours and try again

This is nearly as bad as if you find out some douchebag lawyer or government goon has put a hold on your bank account. I would like to request that Monero include this information in an easy to find place, say in a readme file with the client download, or prominently displayed in the first post of this thread. Also, it would be nice to know what if anything a person that has in a wallet for the previous version needs to do or doesn't need to do to make their wallet work with the new version. A couple of times it seemed ridiculous to even find anything telling you anything.

Also it seems that the daemon does not want to close sometimes. If you are synching and trying to close before the synching finishes, it hangs there and you don't have a clue what is going on. If you type exit again it takes a while and does close.

Also, it would be nice to know that your coins are good without having to send them to another wallet or some other strange way to just see if the new code has destroyed your coins. Some of us don't like to have to babysit the coins in a way that you have to do it just to see if you could even send them.

I hope monero goes to $20,000 per coin so I can be rich.

Just my .02 Moneros.

LucyLovesCrypto

sr. member

Activity: 414

Merit: 251

Quote from: damashup on March 25, 2016, 03:04:09 PM

Quote from: smfuser on March 25, 2016, 02:52:12 PM

Quote from: damashup on March 25, 2016, 02:47:16 PM

Silly question but where can the wallet .bin file be found on Mac OS X? There is a file with the same name as the wallet in the user/[username] directory however the file doesn't have an extension. Should I be moving/ renaming this?

I think the wallet file name won't have a .bin extension unless you specify it when creating it.

Ah yes thanks... I remember now (it's been almost two years since I last created one!)

Nice to see you posting here. It seems like many former BBR supporters are not getting more involved with XMR and or AEON. Are you still working on popboolr? Any way you could adapt something like that for Monero?

damashup

sr. member

Activity: 259

Merit: 250

Quote from: smfuser on March 25, 2016, 02:52:12 PM

Quote from: damashup on March 25, 2016, 02:47:16 PM

Silly question but where can the wallet .bin file be found on Mac OS X? There is a file with the same name as the wallet in the user/[username] directory however the file doesn't have an extension. Should I be moving/ renaming this?

I think the wallet file name won't have a .bin extension unless you specify it when creating it.

Ah yes thanks... I remember now (it's been almost two years since I last created one!)

smfuser

member

Activity: 82

Merit: 10

Quote from: damashup on March 25, 2016, 02:47:16 PM

Silly question but where can the wallet .bin file be found on Mac OS X? There is a file with the same name as the wallet in the user/[username] directory however the file doesn't have an extension. Should I be moving/ renaming this?

I think the wallet file name won't have a .bin extension unless you specify it when creating it.

damashup

sr. member

Activity: 259

Merit: 250

Quote from: luigi1111 on March 25, 2016, 02:30:44 PM

Quote from: damashup on March 25, 2016, 02:13:21 PM

Changing the mixin hasn't helped. Still getting the same error. Could there be another issue?

Can you set your daemon log level to 1 and try again? It should give more details.

Thanks. According to the log the tx has "used already spent key images".

I'm going to follow the steps set out here (assuming they are still valid):

Quote from: smooth on March 31, 2015, 03:34:44 PM

1. Delete poolstate.bin and restart node (also move/rename wallet .bin file again)
2. Make sure you have the current version
3. Make sure you are connected to the network with print_cn (daemon command)
4. Wait 24 hours and try again

Silly question but where can the wallet .bin file be found on Mac OS X? There is a file with the same name as the wallet in the user/[username] directory however the file doesn't have an extension. Should I be moving/ renaming this?

Hueristic

legendary

Legendary level

Activity: 3836

Merit: 4969

Doomed to see the future and unable to prevent it

Quote from: Ayers on March 25, 2016, 03:35:26 AM

Quote from: smooth on March 24, 2016, 04:01:25 AM

Quote from: Ayers on March 24, 2016, 03:46:47 AM

what services are coming, or features to monero that may increase its usage? the value seems stagnant for long time already

Please stop sigspamming.

it was a legit question but since you think it was spam, i'll post this again in one week without the sig, i'm curious about your answer

What a stupid post, you were spamming don't try to weasel out of it. Be a man, admit it and move on. There is ZERO chance you have no clue what has been going on if you even read ten posts of any XMR thread ANYWHERE.

Quote from: Ayers on March 25, 2016, 01:49:00 PM

Quote from: smooth on March 25, 2016, 04:12:27 AM

Quote from: Ayers on March 25, 2016, 03:35:26 AM

Quote from: smooth on March 24, 2016, 04:01:25 AM

Quote from: Ayers on March 24, 2016, 03:46:47 AM

what services are coming, or features to monero that may increase its usage? the value seems stagnant for long time already

Please stop sigspamming.

it was a legit question but since you think it was spam, i'll post this again in one week without the sig, i'm curious about your answer

Your 'legit' question makes no sense when the 'stagnant' value has increased 300% in a few months and has regular daily double digit swings.

So I'm giving you the benefit of the doubt that you are sigspamming and not merely stupid. Please go away.

In case anyone else is interested, here are the design and development goals: http://getmonero.org/design-goals/

how the value is increase by 300% if it was 500k satoshi at the beginning, with a nearly 900k satoshi for the all time high? i'm not talking about a returning to the main situation, that's not an increase for me, a pump after a dump is not an increase, a real increase is when you float above your ath, everything else is only a p&d which lead to stagnation

Which part of the bolded were you unable to comprehend? Looks like your just a troll that was sig spamming and is now in attack mode when called out on it. Why don't you just crawl back under that rock? Or do what I said in the above quote.

luigi1111

legendary

Legendary level

Activity: 1105

Merit: 1000

Quote from: damashup on March 25, 2016, 02:13:21 PM

Quote from: QuantumQrack on March 25, 2016, 01:22:53 PM

Quote from: magico on March 25, 2016, 10:16:27 AM

Quote from: damashup on March 25, 2016, 09:38:17 AM

Quote from: Mineotaur on March 25, 2016, 09:27:27 AM

Quote from: jwinterm on March 25, 2016, 09:23:40 AM

Quote from: Mineotaur on March 25, 2016, 08:52:41 AM

Why can't I send any coins? I've tried 4 times, every time I get this error.

2016-Mar-25 12:22:48.643902 Error: transaction was rejected by daemon with status: Failed

Using latest 64bit Windows wallet.

Try to use the "transfer_new" command, which uses a different algorithm to construct the transaction, and also try to send in smaller amounts.

I've just tried this, I get the same error. I've tried different amounts, right down to 1 coin. Won't work.

I'm getting the same error using the latest Mac OS X wallet.

Mixin must be at least 3

Try:
transfer 3

Or:
transfer_new 3

Mixin must be 2 or greater.

Changing the mixin hasn't helped. Still getting the same error. Could there be another issue?

Can you set your daemon log level to 1 and try again? It should give more details.

damashup

sr. member

Activity: 259

Merit: 250

Quote from: QuantumQrack on March 25, 2016, 01:22:53 PM

Quote from: magico on March 25, 2016, 10:16:27 AM

Quote from: damashup on March 25, 2016, 09:38:17 AM

Quote from: Mineotaur on March 25, 2016, 09:27:27 AM

Quote from: jwinterm on March 25, 2016, 09:23:40 AM

Quote from: Mineotaur on March 25, 2016, 08:52:41 AM

Why can't I send any coins? I've tried 4 times, every time I get this error.

2016-Mar-25 12:22:48.643902 Error: transaction was rejected by daemon with status: Failed

Using latest 64bit Windows wallet.

Try to use the "transfer_new" command, which uses a different algorithm to construct the transaction, and also try to send in smaller amounts.

I've just tried this, I get the same error. I've tried different amounts, right down to 1 coin. Won't work.

I'm getting the same error using the latest Mac OS X wallet.

Mixin must be at least 3

Try:
transfer 3

Or:
transfer_new 3

Mixin must be 2 or greater.

Changing the mixin hasn't helped. Still getting the same error. Could there be another issue?

Ayers

legendary

Legendary level

Activity: 2590

Merit: 1022

Leading Crypto Sports Betting & Casino Platform

Quote from: smooth on March 25, 2016, 04:12:27 AM

Quote from: Ayers on March 25, 2016, 03:35:26 AM

Quote from: smooth on March 24, 2016, 04:01:25 AM

Quote from: Ayers on March 24, 2016, 03:46:47 AM

what services are coming, or features to monero that may increase its usage? the value seems stagnant for long time already

Please stop sigspamming.

it was a legit question but since you think it was spam, i'll post this again in one week without the sig, i'm curious about your answer

Your 'legit' question makes no sense when the 'stagnant' value has increased 300% in a few months and has regular daily double digit swings.

So I'm giving you the benefit of the doubt that you are sigspamming and not merely stupid. Please go away.

In case anyone else is interested, here are the design and development goals: http://getmonero.org/design-goals/

how the value is increase by 300% if it was 500k satoshi at the beginning, with a nearly 900k satoshi for the all time high? i'm not talking about a returning to the main situation, that's not an increase for me, a pump after a dump is not an increase, a real increase is when you float above your ath, everything else is only a p&d which lead to stagnation

QuantumQrack

sr. member

Activity: 337

Merit: 250

Quote from: magico on March 25, 2016, 10:16:27 AM

Quote from: damashup on March 25, 2016, 09:38:17 AM

Quote from: Mineotaur on March 25, 2016, 09:27:27 AM

Quote from: jwinterm on March 25, 2016, 09:23:40 AM

Quote from: Mineotaur on March 25, 2016, 08:52:41 AM

Why can't I send any coins? I've tried 4 times, every time I get this error.

2016-Mar-25 12:22:48.643902 Error: transaction was rejected by daemon with status: Failed

Using latest 64bit Windows wallet.

Try to use the "transfer_new" command, which uses a different algorithm to construct the transaction, and also try to send in smaller amounts.

I've just tried this, I get the same error. I've tried different amounts, right down to 1 coin. Won't work.

I'm getting the same error using the latest Mac OS X wallet.

Mixin must be at least 3

Try:
transfer 3

Or:
transfer_new 3

Mixin must be 2 or greater.

Quicken

sr. member

Activity: 280

Merit: 250

Quote from: magico on March 25, 2016, 10:16:27 AM

Mixin must be at least 3

Try:
transfer 3

Or:
transfer_new 3

Nice catch magico, and a good reminder for everyone.

Pages:

Bitcoin Forum>Alternate cryptocurrencies>Announcements (Altcoins)

Jump to: