Monero Client .NET v0.34.0 has been released!Download it from here!This release features mostly bug fixes, but plenty of them: - Fixed the crashes happening on safe shutdown
- Now there is a chance to restore wallets from '.keys' files
- Enhanced dialog management
Also, you will notice a little icon indicating the number of connections in the bottom-right corner.
|
|
|
|
Because i used this GUI wallet i lost my coins.
I sent coins to other address and the coins were gone from my balance and transaction were never made.
It's not the fault of the GUI, but the system simplewallet uses. Delete your 'wallet.bin' file, keeping 'wallet.bin.keys' intact, and then do the steps I have just mentioned above to re-index your wallet. Next time before sending a TX, please make sure that the fee is set to at least 0.005 XMR. |
|
|
|
Hello!
Sorry for the noobish question, but how can I access my old wallet?
As I see it I must replace wallet.keys and wallet.bin in a WalletData folder with my old ones.
But it gives me an error.
[17:27:49] bitmonero wallet v0.8.8.1()
[17:27:49] 2014-Jul-11 17:27:49.906676 Loading wallet...
[17:27:49] 2014-Jul-11 17:27:49.967680 ERROR c:\users\tom\documents\github\bitmonero\contrib\epee\include\storages\portable_storage.h:161 portable_storage: wrong binary format - signature missmatch
Am I doing something wrong?
Please help.
You may want to recreate your 'wallet.bin' file by only keeping the 'wallet.bin.keys' file in the 'WalletData' directory. From the next version, '.keys' files will automatically be identified, but - as discussed on IRC before with the devs - simplewallet's RPC is not yet capable of restoring those wallets because of the deamon being busy while refreshing. This issue may persist until the daemon's development team does not switch to use rocksDB for storing the blockchain. Until then, you can restore your wallet from the '.keys' file using command line: - First, make sure that your 'wallet.bin' and 'wallet.bin.keys' files are backed up, and then the '.bin' file is removed from the directory which contains the keys for your wallet
- Open 'bitmonerod.exe', and then 'simplewallet.exe'
- In the wallet terminal, select the desired file (probably 'wallet.bin' [even if it doesn't exist]), and then enter the passphrase for it
- Input "refresh", and then hit enter
- Execute the "save" command
|
|
|
|
GUI crash on start,say Monero client NET stopped working;
Log
The system cannot find the file specified
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at Jojatekok.MoneroAPI.ProcessManagers.BaseProcessManager.StartProcess(String[] arguments)
at Jojatekok.MoneroAPI.ProcessManagers.WalletManager.StartInternal()
at Jojatekok.MoneroGUI.Windows.MainWindow.StartWallet()
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
at System.Windows.Application.RunInternal(Window window)
at System.Windows.Application.Run()
at Jojatekok.MoneroGUI.App.Main()
I will add a check whether resource files exist. Anyway, this is not my fault. Please make sure that you extract everything in the zip file into the same folder, as the error means that files in "\Resources\Software\" don't exist. |
|
|
|
This is what's showing up so far in the crashlog file:
... Thanks for the submission! I definitely have an idea what may cause it. May I ask you to check in your task manager whether 'bitmonerod.exe' is running at the time of crashing? And does this happen only during shutdown, or also just randomly? EDIT #1: You don't need to answer these questions, I probably know the reason: The information-querying timers are disposed after killing the daemon (and wallet) process, thus, causing a crash when they are executed after the processes have been closed. EDIT #2: Also, when I switched to using the RPC version of simplewallet, I didn't realize that it does not support the 'exit' command (for safe shutdown), so the next release will contain a fix for this, too.  the wallet doesnt steal my moneros right ?
~CfA~
Right, I wouldn't be asking for donations if it did so.  You can check the source code, and even compile it for yourself if you wanted to be extra careful. |
|
|
|
Downloaded the wallet 0.33 last night and it took a good 5 hours to sync up. It crashed on Win 7 64bit 3 times while syncing, but I don't think it corrupted anything. When I try to exit it, it gives me the warning to be patient while it closes the databases, but then the icon sits there in my task bar and then it gives me the message that it crahed - so it seems something is having trouble shutting down.
I guess the option to change the wallet password is also greyed out for now.
If the application crashes, it exports a log about the case to 'CrashLogs.txt' in the application's main directory. Please send that log to me, so I can take a look at the issue! |
|
|
|
Do I need to add anything anywhere?
I opened the wallet about 15 minutes now and it still says Address: initializing and 0 connections in bottom right.
No, everything should just run well out of the box. Just extract your files into a directory, and simply run 'MoneroClient.Net.exe'. Make sure that you: - Don't have multiple instances of bitmonerod or simplewallet running at the same time
- Are running the application from a 64-bit system
- Have Microsoft .NET Framework 4.5 (or higher) installed
If your problem persists, please try deleting your 'bitmonero' directory at '%AppData%', and then try using the client software again. Please let me know about the results! |
|
|
|
Monero Client .NET v0.33.0 has been released!Download it from here!This release finally introduces switching to integral data types instead of using floating point for coin values. The precisity and reliability has been increased a lot by this change. Also, I have added a little spinning pictogram indicating the synchronization of the blockchain to the bottom-left corner.
|
|
|
|
I have this loaded up on my computer but before I send coins to it can someone tell me where the private key is located?
By default, the wallet.bin.keys file is located in the application's WalletData directory. You can relocate your wallet files from the Options menu, though.  |
|
|
|
Cool - you got a bitcoin address for a tip? One where you hold the private key (It's an airdrop)
Sure, thanks! It's in my profile too by the way: 14wHehBtFt321WTV15khon8Juaxh9drnfJ |
|
|
|
Thank you for both the organization of the bounty, and people who have participated in it. This means a lot to the currency, so I hope that all the developers (including myself ) are planning to continue their precious projects. I am definitely going to keep being a Monero supporter, because of all the features it provides, and the great community of Bitcoin veterans involved in it. Ohh, and I will have to rename my client in order not to cause confusion in newbies' heads. |
|
|
|
Using payment IDs instead of multiple receiving addresses is a much smoother solution. First of all, based on the amount of data requests and bandwidth taken, IDs are definitely the winner over multiple addresses (which are being used in Bitcoin). In long term, this will make Monero software perform much better than any other cryptocurrency variants. Also, using payment IDs for anonymous transactions is a clever solution, because the only balance which has to be tracked is the main one for your one and only address. These kind of identifiers could be used in many scenarios - mostly for merchandising - and the ability to use them will definitely be available in the .NET-based Monero Client (which is a wallet GUI). |
|
|
|
Wow, so lame! I am pretty much thinking at this point that the "dev team" is not capable of progressing much on this. Four weeks and still analyzing the white paper?! WTF.
Please believe me that Monero is advancing fast with great features coming aboard. Just look at the GitHub forks of the daemon, and rpcwallet. They may seem like boring stuff, but real breakthrough is happening there. Also, don't forget that you are using a brand-new technology which has to be stable enough before releasing it for a broader audience. |
|
|
|
Can I recommend that you name your client with something unique, rather than "Monero Client."
This serves a few purposes, not least making it obvious it's not an official GUI.
I'm thinking a cool name. Like Firebird Client or something.
That should not be a problem until the Monero team hasn't decided about the "official" GUI. I will be taking action as soon as it confuses people from the official solution. I have to go on a short holiday now, so the development will pause for some days. I would also like to ask the XMR team to decide about the official wallet interface within the following week. It is one of the most important steps in the lifecycle of a cryptocurrency. EDIT #1: As someone has requested before, I am working on a new balance estimation machanism which takes TX fee in account:  EDIT #2:Monero Client v0.31.0 has been released!https://github.com/Jojatekok/monero-client/releases/tag/v0.31.0Besides the balance and fee calculator implemented into the Send coins tab, this release features selection of your balances on the Overview tab. Also, we are celebrating the 15th language being added. Thanks for everyone, this is amazing! EDIT #3: Well, I've just realized that I forgot to implement real functionality when adjusting the TX fee. I would fix this ASAP, but am not near a computer with Visual Studio 2013 on it. Don't worry, this does NOT critically affect anything. |
|
|
|
New to the wallet and having an issue.
Didn't have enough room on my hardrive as blockchain was synching.
Deleted, reextracted new wallet to 2nd hard drive - but now i have 0 connections.
What gives?
The blockchain's path is not related - in any way - to the Client's path. As an SSD user, I have already been planning to implement an option to relocate the blockchain's path, so a solution will be available for you soon. v0.30.0 will introduce big core changes, so it's going to be an experimental release. EDIT: Finally, there will be a notification about this  EDIT #2:Monero Client v0.30.0 (Experimental) is here!https://github.com/Jojatekok/monero-client/releases/tag/v0.30.0Please be aware that this release is not intended for use in scenarios which require maximum stability, as this version introduces changes to the core which may affect functionality. I have successfully implemented RPC support for simplewallet, but - as it had been discussed earlier on the #monero-dev IRC channel - it may fail "silently" along with the daemon, thus, no notifications may be shown about incoming transactions. Although this is an experimental release, your wallet files are always safe and cannot be corrupted by my software. Report any bugs or crashes which you encounter: I only know about one which happens when the wallet RPC is not yet available, but the blockchain has been synced, thus, the 'Send' [transaction] button is enabled and causes a crash when pressed. |
|
|
|
Monero Client v0.29.0https://github.com/Jojatekok/monero-client/releases/tag/v0.29.0This version makes the users unable to start multiple instances of the software. Some unrequired calls and functions have also been removed, thus, resulting in performance improvement (just try out QR code generation ). The crash logger doesn't log messages on shutdown anymore. Notice that this release didn't get a "Pre-release" tag on GitHub, which means that it can - and should - be safely used.As July 1st had just passed, my entry for the bounty is still Monero Client v0.28.1 to be fair, which can be downloaded from here. It's working great. Outstanding work!!! I've created a quick start doc (With pretty pictures too  ) and pm'd you a link. Can you take a quick look to make sure my statements are correct? I wrote some quick info about what works and what to look for when sending etc. I just want to make sure I'm not making any incorrect statements. If you think it's good I can post the link in the forum. I think it would help new users out. Edit: Here it is... https://www.dropbox.com/l/b1Y5qqG7zBlMXUcLTQVO0u?Great work, as I have already told you in a PM. |
|
|
|
Great!
What are the steps to properly move our coins to a new wallet when there is an update?
Also, can you "change" password? It's greyed out (although I'm synching)
There is no need to move to a new wallet after each new version. You should just keep your WalletData folder in the application's directory, and then delete everything else there in order to be up to date with the software, Currently, I don't know about any kind of regular methods of changing the wallet's password using simplewallet.exe, so that's the reason for greying it out. |
|
|
|
Monero Client v0.29.0https://github.com/Jojatekok/monero-client/releases/tag/v0.29.0This version makes the users unable to start multiple instances of the software. Some unrequired calls and functions have also been removed, thus, resulting in performance improvement (just try out QR code generation ). The crash logger doesn't log messages on shutdown anymore. Notice that this release didn't get a "Pre-release" tag on GitHub, which means that it can - and should - be safely used.As July 1st had just passed, my entry for the bounty is still Monero Client v0.28.1 to be fair, which can be downloaded from here.
|
|
|
|
|
Show Posts
