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

Silly question but is that file there in the folder and of that name ?

bitmonero wallet v0.8.8.1()
password: *******
Error: failed to load wallet: file not found "wallet.bin.keys"


+
bitmonero wallet v0.8.8.1()
password: *******
Error: failed to load wallet: failed to read file "wallet"

if it worked before it should work now. I have no other explination than that, and no, noone can hack a wallet, humans dont currently have the technology to do so.

are you 100% sure you have the correct wallet data in your file folder? i have a few different wallets that i use across 3 machines and sometimes i type the password for wallet 1 into wallet 2 and freak out before quickly realizing i am the one at fault lol. try the typo thing. the daemon did not make a mistake or forget your password so it must be some other error. did you do the 24 seed word thing by any chance?

youre not being a dick at all lol thanks for helping in what ever way... i will try it, however i restore 5 previous versions all say i have same password since it was created... that same password worked.. is there any way i can hack my own wallet??

That's propaganda language.  We all know what is actually happening.  Calling it stealing is a way to smear the value judgments of others in an area where precedent is thin and vocabularies thinner.  I consider Claymore's miner a threat to Monero.  Because it is just a miner, it is a relatively low grade threat, but it is still a threat.  He chose to release it freely, with no license for download.  What we do with it is up to us.  There is almost no similarity to stealing. although I admit some tenuous analogy does exist.

In a gallic cultural context, where les droits d'auteur are more of a category in themselves, Claymore's claims would be stronger than in a albionic context of Franklinite copyright.  In a sinic context they would essentially vanish.

IDK man i find it really hard to believe. the cryptonote protocol doesn't just forget your passwords. i don't mean to be a dick but it is 99% likely that you are at fault here. If you wrote the password down correctly, and it is coming back as incorrect, you probably made a typo when you typed it into the daemon. it doesn't ask you to repeat the password when you generate a wallet, and it reads as ******** so there is no way to see if you made a type or not. my advice would be to try the password again in the daemon with all the likely typos, example if f is the first letter of your password, try it with all the keys surrounding f instead (c,d,r,t,g,v) and do that for all the other letters and i bet you will get it after a few tries.

again, not to be a dick, but I would bet 100 xmr you are the one at fault here not the daemon lol.

+1. Guys see my post above with step-by-step instructions to correctly migrate to clean 64-bit Monero installation.

I would say the "invalid signature" error is your problem, I recall someone else having the same thing and a full reinstall (including wiping their %appdata%) fixed it. Make sure you backup your wallet.bin.keys file first though, just in case!

You're asking the pool operators to steal from Claymore?

Right.  As I hope superresistant realized when he very briefly posted that his pool was going to do this, the result would simply be that the closed-source miners would no longer be able to connect to his pool (or, worse, would submit shares but eat actual blocks found).

This is a very bad idea, and as a miner developer, it would make me stay the heck away from the entire coin.  Let's not go there - XMR has benefitted enormously from having open source contributions that moved it away from its deliberately-slowed-down bytecoin base, and will continue to benefit from improvements to verification speed, ease of mining, etc.

I have a better suggestion:  A large bounty for an open source AMD OpenCL miner.  

If you make it large enough, perhaps Claymore will open source his.  If it's interesting enough, it'll draw other authors into the competition.  And if it's not, then you'll learn that people prefer to pay for quality software by paying a dev fee -- and what's wrong with that?

(20 BTC and it's done.  That's about the same amount that it took to bribe vote Mintpal into listing XMR, so it's not an insane amount.

*WINDOWS USERS* (I think Linux users may do very very the same)

In case of any problem you have encountered with Monero:

1. Backup your wallet.* files.
2. Delete ALL Monero files from your computer.
3. Download 64-bit Monero zip & blockchain.bin from 1st sticky page of this thread.
4. Unzip & place all the files downloaded above to the directory: "C:\Users\\AppData\Roaming\bitmonero".
5. From the backup made at step 1, place wallet.* files ||| EXCEPT wallet.bin ||| into directory at step 4.
6. Start bitmonerod.exe and wait for it to sync with the net.
7. Start simplewallet by the commad prompt: "simplewallet --wallet-file wallet.bin" (name of file that must NOT exist in directory at step 4).
8. When you want to stop any monero executables - ALWAYS type "exit" & be patient.

simplewallet re-creates correct version of wallet.bin for you.

Since you migrate to 64-bit Monero by CORRECT WAY mentioned above - you will never have any problem except being patient due to Monero is currently somewhat slow.

Monero developers are working hard to entirely fix the problem - you may choose either migrate the way I described above, or wait for developers to release a fix.

I "borrowed" crypto-pool.fr's efficiency code and ran it on my pool as well, came back with similar results, from 26th - 28th June we were easily outperforming the network difficulty  at 110%. Over the last day its dropped now to more like 105% which I would think is more within standard variance but is still a bit high, and if its the same across all the mining network what effect is that having? The difficulty has been up and down over the past few days so I don't think its down to it lagging behind hashrate increase, although need more data to be sure, interesting for the people who like statistics anyway.

i recently updated my cryptonote wallet as ive had XMR in cold storage for the past month and a half or so... as more updates came out i thought i should update... however i type my password i created on the old wallet and it now says invalid password and closes..

i have not forgotten my password as i saved it on a txt doc ... i checked 5 previously saved versions of the txt doc for the last 2 months to make sure nothing had changed....it says my password has remained the same since i created it, yet it is invalid using the updated simplewallet using my .keys file   ...

i dont have alot of money but i believe in xmr so i bought a lot for my budget... i could really do with your expertise in this matter

thankyou for your time and i appreciate your help

what wroong whit it? bitmonerood
2014-Jun-30 18:31:41.753972 bitmonero v0.8.8.1()
2014-Jun-30 18:31:41.755973 Module folder: C:\Users\Khatmau_sr\monero.win.x64.latest\bitmonerod.exe
2014-Jun-30 18:31:41.762979 Initializing p2p server...
2014-Jun-30 18:31:41.767982 ERROR c:\users\tom\documents\github\bitmonero\src\p2p\net_node.inl:82 Exception at [node_server::init_config], what=invalid signature
2014-Jun-30 18:31:41.776987 ERROR c:\users\tom\documents\github\bitmonero\src\p2p\net_node.inl:213 Failed to init config.
2014-Jun-30 18:31:41.783994 ERROR ..\..\src\daemon\daemon.cpp:148 Failed to initialize p2p server.
2014-Jun-30 18:31:41.789996 Mining has been stopped, 0 finished
2014-Jun-30 18:31:44.552825 bitmonero v0.8.8.1()
2014-Jun-30 18:31:44.560830 Module folder: C:\Users\Khatmau_sr\monero.win.x64.latest\bitmonerod.exe
2014-Jun-30 18:31:44.568837 Initializing p2p server...
2014-Jun-30 18:31:44.573839 ERROR c:\users\tom\documents\github\bitmonero\src\p2p\net_node.inl:82 Exception at [node_server::init_config], what=invalid signature
2014-Jun-30 18:31:44.582847 ERROR c:\users\tom\documents\github\bitmonero\src\p2p\net_node.inl:213 Failed to init config.
2014-Jun-30 18:31:44.589850 ERROR ..\..\src\daemon\daemon.cpp:148 Failed to initialize p2p server.
2014-Jun-30 18:31:44.597855 Mining has been stopped, 0 finished

Help with missing wallet purse number.



- Address: Initializing
- Status : Daemon ready, updating wallet.....

^Just send them to another wallet of yours. A fix is coming soon to split the transactions for you.

Hi Tacotime. Is there any way to consolidate dust transactions (<0.1 XMR) from pool mining within a wallet?

Could pool operators please direct their advertisement to the appropriate thread: https://bitcointalksearch.org/topic/xmr-monero-mining-653467
I get that you want to improve your pool's hash rate (I do too), but it's making this thread harder to read and honestly is a bit irritating. 

STOP THE FREE RIDE FEE

first pool have break the ice as blocking claymore fees for showing it can be done.
it is now only matter of time other pools to ban the fee, permanenty
you will soon see first good pool blocking fees rising with their hashrates to the roof.
whos pool will it be?

Hi! We see great opportunities in XMR coin. We think that coins such as XMR should have an additional chance to be added to hitbtc.com.
To add this coin we are searching for two Market Makers. We provide special, exclusive conditions for each Market Maker, so anyone interested should contact us at [email protected]
Also, you can continue voting to add the coin by numbers! 

I think you may be building on an architecture which doesn't have support for 128 bit wide types. Like something built without SSE.

If your hardware (or VM) does support SSE, maybe your compiler does not. Or you might need to add the right flags (eg, -msse or whatever, not sure what exactly).

Logs of configuration may also have error messages related to that, though I'd half expect the build to fail then if it can't find what it needs.