As Emily Litella would say, "never mind". I got my wallet working again.  |
|
|
|
Hello folks! Long time. I had ran my wallet from time to time with v0.10.1.0 until I found out last night that there have been several updates and a hard fork to boot (been out of the loop). I updated to the current v0.11.0.3 but my wallet now crashes with a warning in red within a fraction of a second before it closes. It says, "Error: failed to load wallet: std::bad_alloc." It also created a "my_wallet_name.unportable" file in the binary/wallet folder. Did I miss a step? What do I need to do to get my wallet working again? Confession: I am very CLI-challenged so a step-by-step instruction would be appreciated. It was hard to catch with Print Screen on W10 but I finally got lucky after many attempts:  |
|
|
|
I restored from seed on the latest GUI v0.17.1.7 to be a cold wallet in an offline machine. I then generated a view-only wallet from it which I synced in an online machine. My balance is off. All transactions shown are "Received" (green dots). I was able to identify a recent "Send" transaction that is indicated as "Received" (green dot) so I assume the rest of my outputs over a few years (which I am unable to identify) are the same. I shouldn't complain since my balance is a bit more than it should be but I know this is gonna haunt me later down the line. Did I miss a step in setting up this cold/view-only wallet? What gymnastics do I have to do to resolve this issue?
Try exporting the key images from the offline wallet and subsequently importing them in the hot wallet. See (5): https://github.com/monero-ecosystem/monero-GUI-guide/blob/master/monero-GUI-guide.md#send-moneroThank you for your assistance. Importing the cold/offline wallet key images after the view-only/online wallet had synced did not fix my balance issue. I also consequently did "Settings>Wallet>Rescan wallet balance" but this feature did not do anything at all. I even downloaded and synced the blockchain from scratch, just in case the existing one was somehow corrupted but to no avail. To reiterate, I restored my cold/offline/air-gapped wallet from seed (i.e. from scratch) and created the view-only/online wallet from it. Since the "seed" is the ultimate in terms of crypto backup, I assumed that it would just work without any hitch right off the bat. Did I miss a step in my procedure to restore my cold/view-only wallet setup from scratch? Furthermore, several seconds after GUI v0.17.1.7 Wallet and Daemon fully sync, it would go back to syncing mode again with "Daemon blocks remaining: 2". Sometimes, it would drop to "1" momentarily then goes back up to "2" again but would never fully sync again from here on.
Please try applying the ban list: 1. Download this file and place it in the same folder as `monerod` / `monero-wallet-gui`: https://gui.xmr.pm/files/block_tor.txt2. Go to the `Settings` page -> `Node` tab. 3. Enter in `daemon startup flags` box. 4. Restart the GUI (and daemon). This worked. Thanks! Do I need to keep these (ban list file and daemon startup flag) in there from here on? If so, does the list need to be updated all the time and/or updates would be incorporated in subsequent releases? Regarding the cold wallet setup, do you know how to operate the CLI? With respect to the ban list, you should be able to run v0.17.1.9 without it. Can my balance issue be fixed via CLI then? Should be, yes. Can you have a look at this guide? https://monero.stackexchange.com/questions/2868/is-there-any-way-to-construct-a-transaction-manuallyThank you. I did it! I survived through the CLI nightmare...in my own haphazard / unpolished way including moving files around as GUI doesn't have the same default directories as CLI. Perhaps, this could be standardized or made consistent in future releases. Though the wallet balance now appears to be correct, I noticed something odd. The last send transaction which I made a couple of months ago was only for a fraction of a coin but under "Transactions" on GUI, it shows 8-figure coins and change was sent (i.e. 12345678.123456789... coins) to "Unknown recipent" while the transactions before it show correct amounts sent to valid addresses. Do you have any thoughts regarding this irregularity / discrepancy? That sounds like a bug. Do you recognize the transaction as authorized? I am certain that it is the last transaction that I did as this was how it appeared when I checked it right after the send which went through successfully as expected and the wallet balance did decrease by as much (the actual fraction-of-a-coin amount that I sent and not the erroneous 8-figure+ amount that would have rendered my current balance equal to negative 8-figure+). In other words, everything about the transaction was as expected except for its strange amount with "Unknown recipient" shown under "Transactions" in GUI wallet. I had thought that this was yet another obfuscation feature implemented in recent releases but apparently, it is not. |
|
|
|
I restored from seed on the latest GUI v0.17.1.7 to be a cold wallet in an offline machine. I then generated a view-only wallet from it which I synced in an online machine. My balance is off. All transactions shown are "Received" (green dots). I was able to identify a recent "Send" transaction that is indicated as "Received" (green dot) so I assume the rest of my outputs over a few years (which I am unable to identify) are the same. I shouldn't complain since my balance is a bit more than it should be but I know this is gonna haunt me later down the line. Did I miss a step in setting up this cold/view-only wallet? What gymnastics do I have to do to resolve this issue?
Try exporting the key images from the offline wallet and subsequently importing them in the hot wallet. See (5): https://github.com/monero-ecosystem/monero-GUI-guide/blob/master/monero-GUI-guide.md#send-moneroThank you for your assistance. Importing the cold/offline wallet key images after the view-only/online wallet had synced did not fix my balance issue. I also consequently did "Settings>Wallet>Rescan wallet balance" but this feature did not do anything at all. I even downloaded and synced the blockchain from scratch, just in case the existing one was somehow corrupted but to no avail. To reiterate, I restored my cold/offline/air-gapped wallet from seed (i.e. from scratch) and created the view-only/online wallet from it. Since the "seed" is the ultimate in terms of crypto backup, I assumed that it would just work without any hitch right off the bat. Did I miss a step in my procedure to restore my cold/view-only wallet setup from scratch? Furthermore, several seconds after GUI v0.17.1.7 Wallet and Daemon fully sync, it would go back to syncing mode again with "Daemon blocks remaining: 2". Sometimes, it would drop to "1" momentarily then goes back up to "2" again but would never fully sync again from here on.
Please try applying the ban list: 1. Download this file and place it in the same folder as `monerod` / `monero-wallet-gui`: https://gui.xmr.pm/files/block_tor.txt2. Go to the `Settings` page -> `Node` tab. 3. Enter in `daemon startup flags` box. 4. Restart the GUI (and daemon). This worked. Thanks! Do I need to keep these (ban list file and daemon startup flag) in there from here on? If so, does the list need to be updated all the time and/or updates would be incorporated in subsequent releases? Regarding the cold wallet setup, do you know how to operate the CLI? With respect to the ban list, you should be able to run v0.17.1.9 without it. Can my balance issue be fixed via CLI then? Should be, yes. Can you have a look at this guide? https://monero.stackexchange.com/questions/2868/is-there-any-way-to-construct-a-transaction-manuallyThank you. I did it! I survived through the CLI nightmare...in my own haphazard / unpolished way including moving files around as GUI doesn't have the same default directories as CLI. Perhaps, this could be standardized or made consistent in future releases. Though the wallet balance now appears to be correct, I noticed something odd. The last send transaction which I made a couple of months ago was only for a fraction of a coin but under "Transactions" on GUI, it shows 8-figure coins and change was sent (i.e. 12345678.123456789... coins) to "Unknown recipent" while the transactions before it show correct amounts sent to valid addresses. Do you have any thoughts regarding this irregularity / discrepancy? |
|
|
|
If your balance is on your wallet, it will be displayed by both CLI and GUI  And your point is...? If your balance is on that wallet, if you have the seed or the keys to your wallet then the balance will be on that respective wallet  I don't think you understood the essence of my issue but thanks for your input though. |
|
|
|
If your balance is on your wallet, it will be displayed by both CLI and GUI And your point is...? |
|
|
|
I restored from seed on the latest GUI v0.17.1.7 to be a cold wallet in an offline machine. I then generated a view-only wallet from it which I synced in an online machine. My balance is off. All transactions shown are "Received" (green dots). I was able to identify a recent "Send" transaction that is indicated as "Received" (green dot) so I assume the rest of my outputs over a few years (which I am unable to identify) are the same. I shouldn't complain since my balance is a bit more than it should be but I know this is gonna haunt me later down the line. Did I miss a step in setting up this cold/view-only wallet? What gymnastics do I have to do to resolve this issue?
Try exporting the key images from the offline wallet and subsequently importing them in the hot wallet. See (5): https://github.com/monero-ecosystem/monero-GUI-guide/blob/master/monero-GUI-guide.md#send-moneroThank you for your assistance. Importing the cold/offline wallet key images after the view-only/online wallet had synced did not fix my balance issue. I also consequently did "Settings>Wallet>Rescan wallet balance" but this feature did not do anything at all. I even downloaded and synced the blockchain from scratch, just in case the existing one was somehow corrupted but to no avail. To reiterate, I restored my cold/offline/air-gapped wallet from seed (i.e. from scratch) and created the view-only/online wallet from it. Since the "seed" is the ultimate in terms of crypto backup, I assumed that it would just work without any hitch right off the bat. Did I miss a step in my procedure to restore my cold/view-only wallet setup from scratch? Furthermore, several seconds after GUI v0.17.1.7 Wallet and Daemon fully sync, it would go back to syncing mode again with "Daemon blocks remaining: 2". Sometimes, it would drop to "1" momentarily then goes back up to "2" again but would never fully sync again from here on.
Please try applying the ban list: 1. Download this file and place it in the same folder as `monerod` / `monero-wallet-gui`: https://gui.xmr.pm/files/block_tor.txt2. Go to the `Settings` page -> `Node` tab. 3. Enter in `daemon startup flags` box. 4. Restart the GUI (and daemon). This worked. Thanks! Do I need to keep these (ban list file and daemon startup flag) in there from here on? If so, does the list need to be updated all the time and/or updates would be incorporated in subsequent releases? Regarding the cold wallet setup, do you know how to operate the CLI? With respect to the ban list, you should be able to run v0.17.1.9 without it. Can my balance issue be fixed via CLI then? |
|
|
|
I restored from seed on the latest GUI v0.17.1.7 to be a cold wallet in an offline machine. I then generated a view-only wallet from it which I synced in an online machine. My balance is off. All transactions shown are "Received" (green dots). I was able to identify a recent "Send" transaction that is indicated as "Received" (green dot) so I assume the rest of my outputs over a few years (which I am unable to identify) are the same. I shouldn't complain since my balance is a bit more than it should be but I know this is gonna haunt me later down the line. Did I miss a step in setting up this cold/view-only wallet? What gymnastics do I have to do to resolve this issue?
Try exporting the key images from the offline wallet and subsequently importing them in the hot wallet. See (5): https://github.com/monero-ecosystem/monero-GUI-guide/blob/master/monero-GUI-guide.md#send-moneroThank you for your assistance. Importing the cold/offline wallet key images after the view-only/online wallet had synced did not fix my balance issue. I also consequently did "Settings>Wallet>Rescan wallet balance" but this feature did not do anything at all. I even downloaded and synced the blockchain from scratch, just in case the existing one was somehow corrupted but to no avail. To reiterate, I restored my cold/offline/air-gapped wallet from seed (i.e. from scratch) and created the view-only/online wallet from it. Since the "seed" is the ultimate in terms of crypto backup, I assumed that it would just work without any hitch right off the bat. Did I miss a step in my procedure to restore my cold/view-only wallet setup from scratch? Furthermore, several seconds after GUI v0.17.1.7 Wallet and Daemon fully sync, it would go back to syncing mode again with "Daemon blocks remaining: 2". Sometimes, it would drop to "1" momentarily then goes back up to "2" again but would never fully sync again from here on.
Please try applying the ban list: 1. Download this file and place it in the same folder as `monerod` / `monero-wallet-gui`: https://gui.xmr.pm/files/block_tor.txt2. Go to the `Settings` page -> `Node` tab. 3. Enter in `daemon startup flags` box. 4. Restart the GUI (and daemon). This worked. Thanks! Do I need to keep these (ban list file and daemon startup flag) in there from here on? If so, does the list need to be updated all the time and/or updates would be incorporated in subsequent releases? Regarding the cold wallet setup, do you know how to operate the CLI? With respect to the ban list, you should be able to run v0.17.1.9 without it. Opening a command prompt in Windows and copying/pasting args is about the extent of my CLI proficiency unfortunately. OK, I'll try running v0.17.1.9 without it next time. |
|
|
|
I restored from seed on the latest GUI v0.17.1.7 to be a cold wallet in an offline machine. I then generated a view-only wallet from it which I synced in an online machine. My balance is off. All transactions shown are "Received" (green dots). I was able to identify a recent "Send" transaction that is indicated as "Received" (green dot) so I assume the rest of my outputs over a few years (which I am unable to identify) are the same. I shouldn't complain since my balance is a bit more than it should be but I know this is gonna haunt me later down the line. Did I miss a step in setting up this cold/view-only wallet? What gymnastics do I have to do to resolve this issue?
Try exporting the key images from the offline wallet and subsequently importing them in the hot wallet. See (5): https://github.com/monero-ecosystem/monero-GUI-guide/blob/master/monero-GUI-guide.md#send-moneroThank you for your assistance. Importing the cold/offline wallet key images after the view-only/online wallet had synced did not fix my balance issue. I also consequently did "Settings>Wallet>Rescan wallet balance" but this feature did not do anything at all. I even downloaded and synced the blockchain from scratch, just in case the existing one was somehow corrupted but to no avail. To reiterate, I restored my cold/offline/air-gapped wallet from seed (i.e. from scratch) and created the view-only/online wallet from it. Since the "seed" is the ultimate in terms of crypto backup, I assumed that it would just work without any hitch right off the bat. Did I miss a step in my procedure to restore my cold/view-only wallet setup from scratch? Furthermore, several seconds after GUI v0.17.1.7 Wallet and Daemon fully sync, it would go back to syncing mode again with "Daemon blocks remaining: 2". Sometimes, it would drop to "1" momentarily then goes back up to "2" again but would never fully sync again from here on.
Please try applying the ban list: 1. Download this file and place it in the same folder as `monerod` / `monero-wallet-gui`: https://gui.xmr.pm/files/block_tor.txt2. Go to the `Settings` page -> `Node` tab. 3. Enter in `daemon startup flags` box. 4. Restart the GUI (and daemon). This worked. Thanks! Do I need to keep these (ban list file and daemon startup flag) in there from here on? If so, does the list need to be updated all the time and/or updates would be incorporated in subsequent releases? |
|
|
|
|
I restored from seed on the latest GUI v0.17.1.7 to be a cold wallet in an offline machine. I then generated a view-only wallet from it which I synced in an online machine. My balance is off. All transactions shown are "Received" (green dots). I was able to identify a recent "Send" transaction that is indicated as "Received" (green dot) so I assume the rest of my outputs over a few years (which I am unable to identify) are the same. I shouldn't complain since my balance is a bit more than it should be but I know this is gonna haunt me later down the line. Did I miss a step in setting up this cold/view-only wallet? What gymnastics do I have to do to resolve this issue?
Furthermore, several seconds after GUI v0.17.1.7 Wallet and Daemon fully sync, it would go back to syncing mode again with "Daemon blocks remaining: 2". Sometimes, it would drop to "1" momentarily then goes back up to "2" again but would never fully sync again from here on.
|
|
|
|
I haven't really been following the mobile wallet scene. That said, is there currently one (preferably FOSS for Android) that's capable of importing a view-only wallet from monero-gui for primarily montoring incoming transactions/balances in real time while I'm out and about?
 https://www.monerujo.io/Thanks. I'll check it out. I actually installed one of the early releases of Monerujo and explored it a little bit but never got to use it. I don't think the view-only wallet feature was implemented back then. BTW, is a local node option something being considered to be implemented sometime on Monerujo? I mean, Micro SD cards are so cheap nowadays. USB OTG card readers are dirt-cheap as well and very compact nowadays. For the life of me, I just couldn't get my node at home to work (unable to remotely connect); and I've played around with it quite a bit. |
|
|
|
A classic "pot calling the kettle black" . |
|
|
|
I haven't really been following the mobile wallet scene. That said, is there currently one (preferably FOSS for Android) that's capable of importing a view-only wallet from monero-gui for primarily montoring incoming transactions/balances in real time while I'm out and about?
https://www.monerujo.io/Thanks. I'll check it out. I actually installed one of the early releases of Monerujo and explored it a little bit but never got to use it. I don't think the view-only wallet feature was implemented back then. |
|
|
|
|
I haven't really been following the mobile wallet scene. That said, is there currently one (preferably FOSS for Android) that's capable of importing a view-only wallet from monero-gui for primarily montoring incoming transactions/balances in real time while I'm out and about?
|
|
|
|
...and what do the blue ones mean?  |
|
|
|
Though status says it is synced and mining, I consequently get these:  Does it mean my entries to the lottery are invalid and therefore doesn't have a chance in hitting the jackpot? Are you staying up to date with a block explorer or pool in terms of block height? Did you upgrade on latest hardfork? Yes and yes (v0.6.1.1). It syncs and mines all right (so it seems) but I just get these messages in red. Perhaps these screenshots (from two different machines) tell a better story:   |
|
|
|
Though status says it is synced and mining, I consequently get these: Does it mean my entries to the lottery are invalid and therefore doesn't have a chance in hitting the jackpot? |
|
|
|
Interesting. I have a Ryzen 1700 as well with a persistent OC of 4GHz that does up to 600 h/s with the current XMR algo with no issues whatsoever but only getting 670 h/s on randomwow. From what I've gathered, this should be doing around 4 kh/s.
Someone else was having issues with overclock. Have you tried stock speeds? I will as soon as I get the chance. Would that be stock as in default 3.0 GHz with 3.7 GHz Turbo or set it up at a persistent 3.0GHz explicitly? I dunno. The best place to ask is probably #monero-pow channel in freenode. I haven't had any issues running with Intel, and I've heard that ryzen should be even better. So I'd expect you should get at least 3-4x your CN hashrate. I have a box with a very old Intel chip that is OC'd but it properly scales up from its XMR hash rate to a factor of 5.5x with randomwow. Apparently, it has no issue with an OC'd Intel chip. Incidentally, I have an older FX 8120 that is also OC'd to 4GHz that does around 270 h/s with XMR but only 360 h/s with randomwow; failed to scale up to the expected hash rate just like my OC'd Ryzen 1700. I still haven't gotten the chance to try it with stock clocks as you suggested but hopefully soon and will report then. |
|
|
|
Interesting. I have a Ryzen 1700 as well with a persistent OC of 4GHz that does up to 600 h/s with the current XMR algo with no issues whatsoever but only getting 670 h/s on randomwow. From what I've gathered, this should be doing around 4 kh/s.
Someone else was having issues with overclock. Have you tried stock speeds? I will as soon as I get the chance. Would that be stock as in default 3.0 GHz with 3.7 GHz Turbo or set it up at a persistent 3.0GHz explicitly? |
|
|
|
|
Interesting. I have a Ryzen 1700 as well with a persistent OC of 4GHz that does up to 600 h/s with the current XMR algo with no issues whatsoever but only getting 670 h/s on randomwow. From what I've gathered, this should be doing around 4 kh/s.
|
|
|
|
|
Show Posts
