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

[sergey777]

People, please help!!!
How can you pull coins out of the purse with a lost password???
wallet.bin and wallet.bin.keys were created using monero-client-v0.29.0-x64 from here https://github.com/Jojatekok/MoneroGui.Net/releases
Launched this version the other day, tried a bunch of options, eventually found that the password was scored on the Russian keyboard layout, because after driving this combination, the window with password prompt no longer POPs up. BUT in term of ADDRESS hanging sign INITIALIZING... even after a complete download of the blockchain. In the end, no coins to get....

Downloaded the latest purse from off site, downloaded the blockchain in the new format, but the password on the Russian keyboard layout is not taken, writes that the password is not correct.

I am tried to throw up new simplewallet.exe and bitmonerod.exe in the directory monero-client-v0.29.0-x64, client is launched, writes that synchronization is normal, but does not prompt for the password and in the ADDRESS bar, same thing - INITIALIZING...

In the end, the issues:
Is there a problem with the new wallet with the password in Russian layout?
If Yes, how to solve it?
If not, then I still forgot the password. And how to get the coins without knowing the password??

[1714199728]

1714199728

[explorer]

Curious observation:

Block reward seems to stick for 3 or 4 blocks before reducing (c 1011075 level), and is far less dusty than before (round to 4 decimal places).  Is that by design?  Should help with dust accumulation in wallets, I imagine.

edit:
back to 12 decimal dust for one block, then back to rounding and repeating...

[Quicken]

sergey777, is this any help:
https://getmonero.org/knowledge-base/user-guides/restore_account
Do you have the mnemonic seed?
Q

[nioc]

Curious observation:

Block reward seems to stick for 3 or 4 blocks before reducing (c 1011075 level), and is far less dusty than before (round to 4 decimal places).  Is that by design?  Should help with dust accumulation in wallets, I imagine.

edit:
back to 12 decimal dust for one block, then back to rounding and repeating...

Possibly the following explains it.....

3. Minimum mixin requirement on all transactions (with some special exceptions for existing "dust")

4. No new "dust" allowed.

Where can I find the definition of "dust"?

Mostly in the code.

The idea is anything not conforming to N * 10^M where N is 1-9 and M is an integer.

Since these values are limited in number within the range of plausible amounts (a total of 181 are currently possible but some of these are implausible) there will always be available outputs of the same size to mix with, in turn allowing mixing to be required.

Unfortunately there were a few edge cases not handled correctly and some new dust will be created in some cases, but the amount will be vastly reduced. This will need to be cleaned up in the next fork.

The other definition, of amounts that are simply "small" (such as 10^-12) we are allowing to be handled on an economic level for now. For example, miners are allowed to claim less than the full reward if they like, which means they can exclude the very small outputs. This makes their coinbase transaction smaller, which means it will verify and propagate faster (and of course leaves more room for fee-paying transactions). By default this is cutoff at 10^-5 but that is not forced, if miners disagree with that value they can change it.

[sergey777]

sergey777, is this any help:
https://getmonero.org/knowledge-base/user-guides/restore_account
Do you have the mnemonic seed?
Q

Unfortunately this phrase of words was not the graphic version monero-client-v0.29.0-x64
There are only the files:
wallet.bin
wallet.bin.keys
wallet.bin.address.txt

[explorer]

Curious observation:

Block reward seems to stick for 3 or 4 blocks before reducing (c 1011075 level), and is far less dusty than before (round to 4 decimal places).  Is that by design?  Should help with dust accumulation in wallets, I imagine.

edit:
back to 12 decimal dust for one block, then back to rounding and repeating...

Possibly the following explains it.....

3. Minimum mixin requirement on all transactions (with some special exceptions for existing "dust")

4. No new "dust" allowed.

Where can I find the definition of "dust"?

Mostly in the code.

The idea is anything not conforming to N * 10^M where N is 1-9 and M is an integer.

Since these values are limited in number within the range of plausible amounts (a total of 181 are currently possible but some of these are implausible) there will always be available outputs of the same size to mix with, in turn allowing mixing to be required.

Unfortunately there were a few edge cases not handled correctly and some new dust will be created in some cases, but the amount will be vastly reduced. This will need to be cleaned up in the next fork.

The other definition, of amounts that are simply "small" (such as 10^-12) we are allowing to be handled on an economic level for now. For example, miners are allowed to claim less than the full reward if they like, which means they can exclude the very small outputs. This makes their coinbase transaction smaller, which means it will verify and propagate faster (and of course leaves more room for fee-paying transactions). By default this is cutoff at 10^-5 but that is not forced, if miners disagree with that value they can change it.

And if I was paying attention, I would have remembered that.  Thanks 

[equipoise]

You could now get 3 months of KVM Linux VPS Service for 1$ per month (the price is valid for the first 3 months and after that period the price is $11.69 per month, so you should disable recurring payment if you want to keep the node just for the first 3 months). I just bought one for a Monero node and Monero is now compiling. 20 GB Disk Space, 300 GB Traffic, 1024 MB RAM, 1 CPU Core(s), CentOS/Debian/Ubuntu 64 bit. You could order it from here: moonero.duoservers.com (go to VPS Servers -> KVM VPS Servers. For hostname you could enter any valid domain or sub-domain and it's not even needed to be a domain over your control). I won't get anything from those 3$, but any other services ordered from there will bring me varying % profit from the sell. 50% of profits from there (if any) will go to Monero development.

Wait I'm a little bit confused.. 1) can you pay with XMR? (Maybe through XMR.to?) 2) why do you need to provide some random domain when you are going to be personally using it for your node?

Edit: also I see it says ~$4 a month

You could send me in XMR (and some extra for the setting time and monitoring) and I could set the node for you and give you the node IP to monitor it if it's working as a full node next 3 months. On the site you could only pay with USD - it's 3.00$ + 20% VAT = 3.60$ for the full 3 months promo period - you'll have full ssh access to the node, but you should set it yourself. I'm not sure why they need the random domain, but that's the way it's working.

Note: If you set it yourself you should first sync with "./bitmonerod --db-sync-mode fastest:sync:12000 --add-exclusive-node xxx.xxx.xxx.xxx:18080 --p2p-bind-ip 127.0.0.1" to save some bandwidth during the initial sync. Then you should restart the node normally (with --detach) after sync and maybe set upload limit to be sure you won't hit the 300 GB Traffic limit. You could monitor the traffic with "vnstat" to see if upload limit is needed.

My new node works great. Full sync with --add-exclusive-node in 24 hours, but this may vary depending on the exclusive-node of your choice. I didn't set an upload limit yet and the traffic seems a fit for now. Still I'm monitoring the traffic, because it vary a lot during the day and it could easily grow a lot. Solo mining with 14.5 h/s.

[smooth]

Curious observation:

Block reward seems to stick for 3 or 4 blocks before reducing (c 1011075 level), and is far less dusty than before (round to 4 decimal places).  Is that by design?  Should help with dust accumulation in wallets, I imagine.

As explained in the post you quoted

back to 12 decimal dust for one block, then back to rounding and repeating...

Yes, there is a bug that fees don't get truncated properly, only the base amount. So if the fees end up including very small amounts then the block reward will too. Should be fixed in an update.

[Mineotaur]

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 <f46693c336ba66659404c750724d18278dc778f429bebb22995aae8d6e775bf3> was rejected by daemon with status: Failed

Using latest 64bit Windows wallet.

[jwinterm]

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 <f46693c336ba66659404c750724d18278dc778f429bebb22995aae8d6e775bf3> 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.

[Mineotaur]

status
Height: 1010798/1010798 (100.0%) on mainnet, not mining, net hash 11.97 MH/s, v2, up to date, 5+22 connections
2016-Mar-25 10:09:10.190833 [P2P2][80.251.137.218:34728 INC]Sync data returned unknown top block: 1010798 -> 1009932 [866 blocks (0 days) ahead]
SYNCHRONIZATION started
2016-Mar-25 10:09:16.911951 [P2P2][212.36.13.6:64954 INC]Sync data returned unknown top block: 1010798 -> 1009932 [866 blocks (0 days) ahead]
SYNCHRONIZATION started
    i have synced with the network, but there must be something wrong.
    when i transfer my coins got this error
    Error: transaction <365b9fc57722ce1b5cf5bbbc0a43a58995513d7adcf054ddc5da00115fa27b1a> was rejected by daemon with status: Failed
    2016-Mar-25 10:11:15.687045 [RPC1][on_send_raw_tx]: Failed to process tx

I'm having the same problem. I cannot get onto IRC to discuss this. If you find a solution could you post it here please?

My log, 4 times i tried and it's always failing:


2016-Mar-25 11:14:49.811606 [P2P7][178.165.42.37:18080 OUT]Sync data returned unknown top block: 1011115 -> 1009961 [1154 blocks (-1 days) ahead]
SYNCHRONIZATION started
2016-Mar-25 11:45:52.674156 [P2P9]WARNING: no two valid MoneroPulse DNS checkpoint records were received
2016-Mar-25 11:50:48.234061 [P2P4][86.181.175.140:18080 OUT]Synced 1011142/1011142
2016-Mar-25 11:50:48.234061 [P2P4][86.181.175.140:18080 OUT] SYNCHRONIZED OK
2016-Mar-25 11:50:53.421358 [P2P1][13.92.120.87:18080 OUT] SYNCHRONIZED OK
2016-Mar-25 11:50:53.422358 [P2P7][94.12.92.32:18080 OUT] SYNCHRONIZED OK
2016-Mar-25 11:50:53.422358 [P2P4][167.114.49.139:18080 OUT] SYNCHRONIZED OK
2016-Mar-25 11:50:53.422358 [P2P6][5.196.88.9:18080 OUT] SYNCHRONIZED OK
2016-Mar-25 12:01:38.487253 [P2P6][14.149.112.171:18080 OUT]Sync data returned unknown top block: 1011150 -> 1009961 [1189 blocks (-1 days) ahead]
SYNCHRONIZATION started
2016-Mar-25 12:21:32.916571 [RPC1][on_send_raw_tx]: Failed to process tx
2016-Mar-25 12:21:43.011148 [RPC0][on_send_raw_tx]: Failed to process tx
2016-Mar-25 12:22:48.639902 [RPC0][on_send_raw_tx]: Failed to process tx
2016-Mar-25 12:26:00.671885 [RPC0][on_send_raw_tx]: Failed to process tx
2016-Mar-25 12:26:54.255950 [node] Stop signal sent
2016-Mar-25 12:26:54.307953 [SRV_MAIN]net_service loop stopped.
2016-Mar-25 12:26:54.308953 [SRV_MAIN]p2p net loop stopped
2016-Mar-25 12:26:54.311954 [node] Stop signal sent
2016-Mar-25 12:26:54.311954 [SRV_MAIN]Stopping core rpc server...
2016-Mar-25 12:26:54.317954 [SRV_MAIN]Node stopped.
2016-Mar-25 12:26:54.319954 [SRV_MAIN]Deinitializing rpc server...
2016-Mar-25 12:26:54.322954 [SRV_MAIN]Deinitializing p2p...
2016-Mar-25 12:26:54.449961 [SRV_MAIN]Deinitializing core...
2016-Mar-25 12:26:54.485963 [SRV_MAIN]Closing IO Service.
2016-Mar-25 12:26:54.929989 [SRV_MAIN]Deinitializing cryptonote_protocol...

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 <f46693c336ba66659404c750724d18278dc778f429bebb22995aae8d6e775bf3> 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.

[Mineotaur]

2016-Mar-25 12:50:09.019726 [P2P6][167.114.49.139:18080 OUT] SYNCHRONIZED OK
2016-Mar-25 12:50:09.020726 [P2P3][13.92.120.87:18080 OUT] SYNCHRONIZED OK
2016-Mar-25 13:26:22.865063 [RPC1][on_send_raw_tx]: Failed to process tx
2016-Mar-25 13:28:38.495821 [P2P1]----- BLOCK ADDED AS ALTERNATIVE ON HEIGHT 1011205
id:   <2751c8d20290689fb4d34f407505cebb262e6759b07bf9d43507b95282cf92a9>
PoW:   <ad9408c38b5f6f6b1ab3e4ff08edc1cac18dd6f919d6c865349610b102000000>
difficulty:   1417382386

[damashup]

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 <f46693c336ba66659404c750724d18278dc778f429bebb22995aae8d6e775bf3> 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.

[MoneroMooo]

2016-Mar-25 12:50:09.019726 [P2P6][167.114.49.139:18080 OUT] SYNCHRONIZED OK
2016-Mar-25 12:50:09.020726 [P2P3][13.92.120.87:18080 OUT] SYNCHRONIZED OK
2016-Mar-25 13:26:22.865063 [RPC1][on_send_raw_tx]: Failed to process tx
2016-Mar-25 13:28:38.495821 [P2P1]----- BLOCK ADDED AS ALTERNATIVE ON HEIGHT 1011205
id:   <2751c8d20290689fb4d34f407505cebb262e6759b07bf9d43507b95282cf92a9>
PoW:   <ad9408c38b5f6f6b1ab3e4ff08edc1cac18dd6f919d6c865349610b102000000>
difficulty:   1417382386

When this error happens, it's very likely there is a log level 1 message before it that gives more info.
So, in the daemon: set_log 1
Then try again. You should see a message. It's likely telling you're double spending, but possibly another error.
Double spending can happen if the wallet's idea of spend coins goes out of sync with the daemon.

[magico]

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 <f46693c336ba66659404c750724d18278dc778f429bebb22995aae8d6e775bf3> 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 <adr> <amount>

Or:
transfer_new 3 <adr> <amount>

[Mineotaur]

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 <f46693c336ba66659404c750724d18278dc778f429bebb22995aae8d6e775bf3> 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 <adr> <amount>

Or:
transfer_new 3 <adr> <amount>

"transfer 3 <adr> <amount>" worked. Thankyou!

[Quicken]

Mixin must be at least 3

Try:
transfer 3 <adr> <amount>

Or:
transfer_new 3 <adr> <amount>

Nice catch magico, and a good reminder for everyone.

[QuantumQrack]

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 <f46693c336ba66659404c750724d18278dc778f429bebb22995aae8d6e775bf3> 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 <adr> <amount>

Or:
transfer_new 3 <adr> <amount>

Mixin must be 2 or greater.

[Ayers]

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

[damashup]

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 <f46693c336ba66659404c750724d18278dc778f429bebb22995aae8d6e775bf3> 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 <adr> <amount>

Or:
transfer_new 3 <adr> <amount>

Mixin must be 2 or greater.

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