no way i can get just a simple gui wallet like all these other coins ?!
There are two "simple gui" wallets, but bear in mind that Monero is not "like all these other coins"  From the OP: GUIAll current GUIs are in beta, but they should be fairly safe to use because they work through bitmonerod and simplewallet from the main code.qt gui needs to be compiled ?! Yes, but compiling it on Mac or Linux is not really a big deal (also, you can find some compiled test versions in the GUI bounty thread). For Windows, I have all the releases tagged and compiled on GitHub, including an alpha release which utilizes rpcwallet with the new daemon. |
|
|
|
Monero Client .NET v0.39.0-alpha.1 has been released!Please be aware that this is a test release, thus, it isn't being beamed by auto-update. You can download it from here.This release is experimental and should not be used in production, but for testing purposes only. It is meant to bring the core development team a bigger tester base for using the new daemon and rpcwallet which offer a lot more opportunities (like using Windows services) waiting besides my current implementation. Also, I have set the client to request administrator mode on startup to avoid issues accessing the registry, and allow more developments to be done in the future. There are some known bugs in this version which are already being worked on by the core development team: - You must wait for the daemon to initialize its RPC service before entering your wallet password
(Wait for the synchronization status icon to appear in the main window)
- You cannot create a new wallet, but use an already existing one
Have fun using the new build, and please give feedback about it, as it would be valuable for the entire Monero team. I'm going on a 3-week holiday today, so the development will be paused from my side for now. If I have the opportunity, I'll try to answer questions here as soon as possible.
|
|
|
|
Monero Client .NET v0.39.0-alpha.1 has been released!Please be aware that this is a test release, thus, it isn't being beamed by auto-update. You can download it from here.This release is experimental and should not be used in production, but for testing purposes only. It is meant to bring the core development team a bigger tester base for using the new daemon and rpcwallet which offer a lot more opportunities (like using Windows services) waiting besides my current implementation. Also, I have set the client to request administrator mode on startup to avoid issues accessing the registry, and allow more developments to be done in the future. There are some known bugs in this version which are already being worked on by the core development team: - You must wait for the daemon to initialize its RPC service before entering your wallet password
(Wait for the synchronization status icon to appear in the main window)
- You cannot create a new wallet, but use an already existing one
Have fun using the new build, and please give feedback about it, as it would be valuable for the entire Monero team. I'm going on a 3-week holiday today, so the development will be paused from my side for now. If I have the opportunity, I'll try to answer questions here as soon as possible.
|
|
|
|
monero devs seems to be absolutely beginners - your accusations and anger touched us, here is a result of 10 min research of your kiddy coding, concerning Payments ID and games with your kiddy coin wallet: Second chapter of any average "Beginners in C++ guide" says that arguments can be passed to parameters either by value or by reference. Looks like monero devs did not noticed that, when they recently read that kind of books. Lets look at this playground: https://github.com/monero-project/bitmonero/commit/d433a696e527a01c1cbef48495652335140f0bb2With "Monero golden ampersand bug" made by monero devs, monero devs missed some &, wuuups: bool validate_transfer(const std::list<wallet_rpc::transfer_destination> destinations, const std::string payment_id, std::vector<cryptonote::tx_destination_entry>& dsts, std::vector<uint8_t> & extra, epee::json_rpc::error& er); bool wallet_rpc_server::validate_transfer(const std::list<wallet_rpc::transfer_destination> destinations, const std::string payment_id, std::vector<cryptonote::tx_destination_entry>& dsts, std::vector<uint8_t> & extra, epee::json_rpc::error& er)
Affects: Monero simplewallet since at least June 18 just lose all Payment ID data, so people can lost their money if they use your so called monero RPC "features". Again - all transfers in monero network made with JSON-RPC Payment ID, EG from Poloniex exchange to Bittrex exchange was made wrong if they use monero latest main kiddy code, or may be just lost. Qua, qua, qua ...Users, be careful with kiddy coders. Remember the good old game Duck Hunt? Well, it's time for some nostalgia by clarifying some things. First of all, you seem to forget the main point of cryptocurrency by trying to "fight" other coins for your own profit. That's just simply unacceptable, period. Also, test releases - surprisingly - mean that they are not ready for real-world use, and may cause harm for the brave man who take time trying to improve software by using it and notifying the developers about errors. On the other hand, can you explain the reason behind plagiarizing Monero's repositories without letting anyone know? You've just tried to evade Fluffypony's question, but I'll make sure you answer it here and now, in front of your own fans. Public apologies are welcome and accepted. |
|
|
|
v0.38.1
it keeps crashing any idea?
Please provide me as much resources as you can about the case (othersiwe, I cannot help...): - When does it crash?
- How does it crash? (silently or not)
- Did the previous version work with the same configuration?
- If available, please send me the 'CrashLogs.txt' file found in the application's directory
|
|
|
|
Monero Client .NET v0.38.0 has been released!
Get ready for merchandising - Start receiving payments using QR codes!Download the new version from here, or just use the auto-update function introduced in the previous release. - Implemented support for the 'monero:' protocol
- Added an option to show QR codes in large (just double-click on them)
- Improved the code for being a single-instanced application
- Updated the QR code generator's URI scheme
- Changed the default behavior of double-clicking on a contact in the Address book (it shows the QR code generation window from now)
- Fixed some localization-related issues (punctuation characters should now be all right)
- Deprecated simpleminer's path setting
Hello, do anybody have any idea why my balance is still on 0 in the wallet when im suppose to have around 1. The wallet have over 100 connection to the network and it is in sync.
any idea how to fix this?
This seems to be a problem with bitmonerod, the developers are already working on a workaround. |
|
|
|
Has anyone been using this for enough time and for enough transactions (including transactions to exchanges like Poloniex then withdrawing and sending back to the wallet) to constante this is in fact legit and reliable? I've heard people stories about lossing coins when withdrawing from Poloniex on the original wallet, I don't remember the reason but it happened. Im pretty scared to lose coins because I do something wrong within the GUI wallet.
I know that my opinion is not representative, but I have been using my own GUI wallet to transfer and receive funds to and from people/exchanges - even with payment IDs given. Basically, the application is a wrapper around 'bitmonerod.exe' and 'simplewallet.exe': The GUI communicates with both through RPC, thus, messed up transactions can only be considered user or core errors. If you are afraid of your wallet files being compromised, you can check the project's source code here, compile it by yourself, and disable automatic updates by setting the '-noupdate' flag for 'MoneroClient.Net.exe'. In most of the cases (whenever people try to set the TX fee below 0.005 XMR [which I have disabled in the current release]), re-indexing the wallet file solves all the issues. Application crashes cannot do any harm to your wallet, based on the nature of its saving mechanism. You may also use the built-in Backup Manager to ensure the safety of your digital commodities. |
|
|
|
Monero Client .NET v0.37.0 has been released!Download it from here!- Added auto-update (executing in the background)
- Added a minimum value of 0.005 for the transaction fee
- Made the icon look smoother
- Fixed a value conversion bug
I'll be on a 3-week vacation from next Wednesday, so please report all the bugs (if there are any ) as soon as possible! 
Like the client so far. Is there anyway to speed up the client startup? bitmonerod starts and syncs fairly quickly,
but simplewallet always takes forever to finish syncing. Is there a way to speed up the simplewallet startup?
I found lots of things about speeding up bitmonerod startup, but not simplewallet.
Sorry, but this does not depend on me, neither the GUI. I will implement support for rpcwallet as soon as it releases. Wallet seems to be working well but how come the incoming and outgoing transactions are showing up as the same.
I do notice this issue as well. I have already tried to deserialize TX blobs from the daemon's "gettransactions" call, but failed because the byte array serialization is dependent on the Boost library which is written in C++. I have made a draft of a proposed new RPC schema supporting more functions, and have already contacted the developers about its implementation. I just don't want to share it here for the public, because some other currencies may copy it. Nice thing! But is it possible to start it without starting bitmonerod? I need only convenient wallet. Console command report that mining is stopped, but bitmonerod process still exist and do something with my CPU.  If you mean a solution like this, then it may be an interesting idea. Otherwise, the daemon is required to run with the GUI wallet, as my application gets data from RPC services.
|
|
|
|
Well I ran into a problem last night and am working with Poloniex on trying to find out the issue. I sent an XMR payment of 1.0 XMR (including 0.001 fee) and I included the required payment ID. Poloniex says it didn't arrive in their wallet and on the blockchain there in no payment ID. This is my transaction has: http://monerochain.info/tx/ee635cbdbcaa1634867cdc6bd63003f9ef08032b106e11d8fd40c09d10561f18Here is a screenshot showing the send: Any ideas what is going on? I manually reduced the default fee from 0.005 to 0.001 and was just curious to see what would happen - did that mess something up? Currently, the specification does not allow fees lower than 0.005, but to avoid confusion, I'll make it a minimum in the next release. I also did this by curiosity, and suggest that you should re-index your wallet in the following way: - Make sure you have a backup of all your wallet files, just in case...
- Close Monero Client
- In the wallet data folder, delete the 'wallet.bin' file (but keep the '.keys', and if exists, the '.address.txt' file)
- Restart Monero Client, and wait about 20 or 30 minutes until simplewallet re-indexes your wallet and makes it usable again. Before closing the client, make sure that wallet ('.bin' file) autosave has happened.
I deleted the bin file, relaunched it and it only took a couple minutes to reindex it (i7 laptop & SSD). It still shows the 1.0 transaction in my history but it looks like my wallet has the correct amount now. Is there anything I should be worried about with those 1.0 coins? Was it a failed send? I'll leave it at the default send fee from now on, but we should probably post a warning or make it minimum as you noted. Well, you should retry reindexing it in 3 or 4 days if that matters, so the invalid TX can fall out of the mempool, and will be credited to your account again. |
|
|
|
Well I ran into a problem last night and am working with Poloniex on trying to find out the issue. I sent an XMR payment of 1.0 XMR (including 0.001 fee) and I included the required payment ID. Poloniex says it didn't arrive in their wallet and on the blockchain there in no payment ID. This is my transaction has: http://monerochain.info/tx/ee635cbdbcaa1634867cdc6bd63003f9ef08032b106e11d8fd40c09d10561f18Here is a screenshot showing the send:  Any ideas what is going on? I manually reduced the default fee from 0.005 to 0.001 and was just curious to see what would happen - did that mess something up? Currently, the specification does not allow fees lower than 0.005, but to avoid confusion, I'll make it a minimum in the next release. I also did this by curiosity, and suggest that you should re-index your wallet in the following way: - Make sure you have a backup of all your wallet files, just in case...
- Close Monero Client
- In the wallet data folder, delete the 'wallet.bin' file (but keep the '.keys', and if exists, the '.address.txt' file)
- Restart Monero Client, and wait about 20 or 30 minutes until simplewallet re-indexes your wallet and makes it usable again. Before closing the client, make sure that wallet ('.bin' file) autosave has happened.
|
|
|
|
I reviewed and finished the french translation. I'm also runing the 0.36.0. So far no random crash but... Object reference not set to an instance of an object.
at Jojatekok.MoneroGUI.ConverterCoinAtomicValueToNullableDisplayValue.ConvertBack(Object value, Type targetType, Object parameter, CultureInfo culture)
at System.Windows.Data.BindingExpression.ConvertProposedValue(Object value)
at System.Windows.Data.BindingExpressionBase.UpdateValue()
at System.Windows.Data.BindingExpressionBase.Dirty()
at System.Windows.Data.BindingExpressionBase.SetValue(DependencyObject d, DependencyProperty dp, Object value)
at System.Windows.DependencyObject.SetValueCommon(DependencyProperty dp, Object value, PropertyMetadata metadata, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType, Boolean isInternal)
at System.Windows.DependencyObject.SetValue(DependencyProperty dp, Object value)
at Xceed.Wpf.Toolkit.Primitives.UpDownBase`1.SyncTextAndValueProperties(Boolean updateValueFromText, String text, Boolean forceTextUpdate)
at Xceed.Wpf.Toolkit.Primitives.InputBase.OnTextChanged(DependencyObject o, DependencyPropertyChangedEventArgs e)
at System.Windows.DependencyObject.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
at System.Windows.FrameworkElement.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
at System.Windows.DependencyObject.NotifyPropertyChange(DependencyPropertyChangedEventArgs args)
at System.Windows.DependencyObject.UpdateEffectiveValue(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType)
at System.Windows.DependencyObject.SetValueCommon(DependencyProperty dp, Object value, PropertyMetadata metadata, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType, Boolean isInternal)
at Xceed.Wpf.Toolkit.Primitives.UpDownBase`1.TextBox_TextChanged(Object sender, TextChangedEventArgs e)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at Xceed.Wpf.Toolkit.AutoSelectTextBox.OnTextChanged(TextChangedEventArgs e)
at System.Windows.Controls.Primitives.TextBoxBase.OnTextContainerChanged(Object sender, TextContainerChangedEventArgs e)
at System.Windows.Controls.TextBox.OnTextContainerChanged(Object sender, TextContainerChangedEventArgs e)
at System.Windows.Documents.TextContainerChangedEventHandler.Invoke(Object sender, TextContainerChangedEventArgs e)
at System.Windows.Documents.TextContainer.EndChange(Boolean skipEvents)
at System.Windows.Documents.TextRangeBase.EndChange(ITextRange thisRange, Boolean disableScroll, Boolean skipEvents)
at System.Windows.Documents.TextRange.ChangeBlock.System.IDisposable.Dispose()
at System.Windows.Documents.TextEditorTyping.OnBackspace(Object sender, ExecutedRoutedEventArgs args)
at System.Windows.Input.CommandBinding.OnExecuted(Object sender, ExecutedRoutedEventArgs e)
at System.Windows.Input.CommandManager.ExecuteCommandBinding(Object sender, ExecutedRoutedEventArgs e, CommandBinding commandBinding)
at System.Windows.Input.CommandManager.FindCommandBinding(CommandBindingCollection commandBindings, Object sender, RoutedEventArgs e, ICommand command, Boolean execute)
at System.Windows.Input.CommandManager.FindCommandBinding(Object sender, RoutedEventArgs e, ICommand command, Boolean execute)
at System.Windows.Input.CommandManager.OnExecuted(Object sender, ExecutedRoutedEventArgs e)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args)
at System.Windows.Input.RoutedCommand.ExecuteImpl(Object parameter, IInputElement target, Boolean userInitiated)
at System.Windows.Input.CommandManager.TranslateInput(IInputElement targetElement, InputEventArgs inputEventArgs)
at System.Windows.UIElement.OnKeyDownThunk(Object sender, KeyEventArgs e)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args)
at System.Windows.Input.InputManager.ProcessStagingArea()
at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)
at System.Windows.Interop.HwndKeyboardInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawKeyboardActions actions, Int32 scanCode, Boolean isExtendedKey, Boolean isSystemKey, Int32 virtualKey)
at System.Windows.Interop.HwndKeyboardInputProvider.ProcessKeyAction(MSG& msg, Boolean& handled)
at System.Windows.Interop.HwndSource.CriticalTranslateAccelerator(MSG& msg, ModifierKeys modifiers)
at System.Windows.Interop.HwndSource.OnPreprocessMessage(Object param)
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 System.Windows.Threading.Dispatcher.Invoke(DispatcherPriority priority, Delegate method, Object arg)
at System.Windows.Interop.HwndSource.OnPreprocessMessageThunk(MSG& msg, Boolean& handled)
at System.Windows.Interop.ComponentDispatcherThread.RaiseThreadMessage(MSG& msg)
at System.Windows.Threading.Dispatcher.TranslateAndDispatchMessage(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()
Exception has been thrown by the target of an invocation.
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Delegate.DynamicInvokeImpl(Object[] args)
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()
Exception has been thrown by the target of an invocation.
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Delegate.DynamicInvokeImpl(Object[] args)
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 got those trying to send to my BITtrex wallet. Interesting, I will look after this, as I know the cause. Thanks for the report, and also putting a lot of effort into translation! EDIT: I forgot to check for null values before multiplication at conversion, but the next release will fix the fault. |
|
|
|
EDIT #4: Please ensure that the ports 18081 and 18082 are open on your network, otherwise, the daemon and wallet RPCs cannot work. Check your firewall settings too, and also, you can change the host and port settings in the options menu.
Please do not do this. Only port 18080 (p2p) should be open to outside connections (inside connections are generally okay though), the rest should be closed to outside access. You don't want random people on the internet making RPC requests against your node or wallet. Sorry for the misleading instruction and thanks for the immediate correction: I meant to check whether there are no conflicting programs on the same ports. |
|
|
|
I just tried this wallet out and I'm not getting any connections. I'm using the latest version and it just constantly shows 0 connections. What am I doing wrong?
I got it to finally work. I copy and pasted the following files: .bin, .bin.keys and bin.address.txt from the cli wallet. I pasted into the .NET xmr client folder under Resources/Software. Now it synced up and runs ok, little buggy still and resource hungry on the system memory. I have already told everyone that the wallet's sync problem is none of my business, but the core development team's. As the new RocksDB implementation will release, everything will get solved automatically. But I can see that there is big demand for a quick fix, so I'll try my best and try to avoid this problem. EDIT #3: Fixed, see the release below.  As for this exception: Object reference not set to an instance of an object.
at Jojatekok.MoneroAPI.ProcessManagers.DaemonManager.JsonQueryData[T](JsonRpcRequest jsonRpcRequest)
at Jojatekok.MoneroAPI.ProcessManagers.DaemonManager.QueryNetworkInformation()
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.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.TimerQueue.FireNextTimers()
I got an idea about how to fix it: Not sure though, but it will probably work. EDIT: It seems that I finally caught the bug. Expect a new release today!  EDIT #2: Here we go! Monero Client .NET v0.36.0 has been released!Download it from here!- Added ability to change the blockchain's path
- Added a new "Up to date" sync status indicator
- Added a tooltip for sync status icons
- Improved support for asian languages with special punctuation symbols
- Changed the default wallet RPC port to 18082
- Fixed a bug that made the user unable to restore wallets from '.keys' files
Please help localizing the client! Most of the translations are almost done, they just need a little touch https://www.transifex.com/organization/jojatekok/dashboard/monero-client-netI just tried this wallet out and I'm not getting any connections. I'm using the latest version and it just constantly shows 0 connections. What am I doing wrong?
EDIT #4: Please ensure that the ports 18081 and 18082 are open on your network, otherwise, the daemon and wallet RPCs cannot work. Check your firewall settings too, and also, you can change the host and port settings in the options menu. Please see the corrected instructions below! |
|
|
|
First of all thanks a lot for setting up this ultra clean wallet. I do have a question. I have random crash with earlier version and with last version. Object reference not set to an instance of an object.
at Jojatekok.MoneroAPI.ProcessManagers.DaemonManager.JsonQueryData[T](JsonRpcRequest jsonRpcRequest)
at Jojatekok.MoneroAPI.ProcessManagers.DaemonManager.QueryNetworkInformation()
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.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.TimerQueue.FireNextTimers()
Object reference not set to an instance of an object.
at Jojatekok.MoneroAPI.ProcessManagers.DaemonManager.JsonQueryData[T](JsonRpcRequest jsonRpcRequest)
at Jojatekok.MoneroAPI.ProcessManagers.DaemonManager.QueryNetworkInformation()
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.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.TimerQueue.FireNextTimers()
Here's crashlog.txt With 8GB of ram could it be a RAM issue? No, this is definitely not a RAM issue. Are you using v0.35.0? Because I fixed a bug straightly related to that recently if I recall correctly... |
|
|
|
Luv the client been using daily and have to say good job 4 sure
can i donate 5000 XMR to 47hK4gehaMrFTQCiV5FEmM54hpqTrdHudb9nUBG88NicBDpxH4TGuh3TmW84Dc6dpMiEiBLGvJCuT3x C3LNHctmx7mG8NLM ?
~CfA~
Whoa, that seems like an ultimately huge amount...  I would be very thankful, though, and would never forget your name! |
|
|
|
Thanks! Without this I couldn't import my old wallet.
I tried the method described in your guide but that didn't work, first it kept freezing then after a couple times it said it worked but I never had to enter my password or something and nothing happened.
I noticed that my .keys file was named wallet.keys instead of wallet.bin.keys, maybe that was the issue?
The '.keys' file is the most important, and must be strictly named after the wallet file (which is - by default - 'wallet.bin'). So that could be a problem, yes. |
|
|
|
Monero Client .NET v0.35.0 has been released!Download it from here!Features aboard: Now, you are able to switch the RPC host and ports being used in the Options menu. Please be reminded that every single addition of new functions require updating the localization files listed here. Also, I made the progress bar green for everyone (even for people who use classic Windows themes), in order to make the text on it more readable.
I'll update my user guide later but thought I'd share my experience with importing old wallets first of all:
... Thank you for providing an in-depth guide about this!
I was planning to add timestamp display for transactions in this release, but - as mentioned here - I wasn't able to deserialize TX BLOBs. Thus, I decided to start a project involving developers of the Monero community to redesign the whole JSON RPC scheme. Succeeding would mean the end of unorganized and bloated functions, allowing anyone to work with the new API easily out of the box, and improving the scalability for future needs.
|
|
|
|
All of the XMR distributions from the bounty fund are now complete. Transaction details have been sent to the winners. There was fortunately no need for any additional deduction from neozaru's payment. All four payments were made in the exact amount specified (less standard 0.005 XMR fee), leaving a remaining balance in the bounty fund wallet of zero: [wallet 4BBi2m]: refresh
Starting refresh...
Refresh done, blocks received: 3
balance: 0.000000000000, unlocked balance: 0.000000000000
Thank You and the whole team for being so honest and transparent! It really has strenghtened my belief in Monero, thus, I will definitely keep developing my GUI wallet. |
|
|
|
I have no idea how to update my wallet and so I've been stuck on version 0.29.  First of all, you should backup your 'WalletData' folder to a safe storage other than the default location.After that, delete everything from the original folder except the 'WalletData' directory, then download the latest version of the client, placing all the files in the zip file into the root directory of Monero Client .NET. |
|
|
|
This is not only impressive, but irresistibly fantastic! I'll make sure to include this in the original post with a credit given to you and your pool. For the others: Please be reminded that the GUI wallet can only be as stable as the daemon and wallet console software. Thus, restoring 'wallet.bin' files from '.keys' may not work due to the daemon's automatic blockchain saving which blocks its RPC. As soon as RocksDB will be used for the new daemon, and rpcwallet will be considered stable, the GUI is going to be a lot more reliable too. |
|
|
|
|
Show Posts
