binaryFate < binaryfate@getmonero.org> ... Add ZMQ/Pub support for txpool_add and chain_main events Various bug fixes and performance improvements Can someone explain "Enforce claiming maximum coinbase amount monero" please. Is it both CLI and GUI ? It is a protocol rule. Thus, it will affect all wallets. I just cut the message to make it shorter, my question is not related to the network changes but to the wallet itself. Is it CLI or both CLI and GUI ? Can you elaborate? 'Enforce claiming maximum coinbase amount monero' is a protocol rule and therefore applies to all participants (and by extension, wallets). Note that it only affects miners, not 'standard' users. |
|
|
|
binaryFate < binaryfate@getmonero.org> ... Add ZMQ/Pub support for txpool_add and chain_main events Various bug fixes and performance improvements Can someone explain "Enforce claiming maximum coinbase amount monero" please. Is it both CLI and GUI ? It is a protocol rule. Thus, it will affect all wallets. |
|
|
|
running Nitrogen Nebula 16.0.1 I keep getting "failed to find tx meta" status
Height: 2153319/2153319 (100.0%) on mainnet, not mining, net hash 1.46 GH/s, v12, 8(out)+0(in) connections, uptime 0d 0h 1m 4s
2020-07-30 06:00:27.284 E failed to find tx meta
2020-07-30 06:00:27.291 W Background mining controller thread started
2020-07-30 06:00:27.291 I Miner thread was started [0]
2020-07-30 06:00:27.692 I background mining is enabled, but not started, waiting until start triggers
2020-07-30 06:00:45.398 E failed to find tx meta
2020-07-30 06:00:55.427 E failed to find tx meta
2020-07-30 06:01:20.456 E failed to find tx meta
2020-07-30 06:01:24.262 E failed to find tx meta
2020-07-30 06:01:35.478 E failed to find tx meta
2020-07-30 06:01:48.500 E failed to find tx meta
2020-07-30 06:02:05.486 E failed to find tx meta
2020-07-30 06:02:10.504 E failed to find tx meta
2020-07-30 06:02:15.536 E failed to find tx meta
2020-07-30 06:02:25.545 E failed to find tx meta
2020-07-30 06:02:35.553 E failed to find tx meta
2020-07-30 06:02:40.561 E failed to find tx meta
2020-07-30 06:03:00.570 E failed to find tx meta
2020-07-30 06:03:15.580 E failed to find tx meta
2020-07-30 06:03:25.591 E failed to find tx meta
2020-07-30 06:03:40.603 E failed to find tx meta
2020-07-30 06:03:50.622 E failed to find tx meta
2020-07-30 06:04:05.881 E failed to find tx meta Annoying. Is there some way to fix this? Did a search, but I don't understand the discussion on github. https://github.com/moneroexamples/openmonero/issues/169You can safely ignore the warnings, they are related to the pruning code. |
|
|
|
he bi yearly forks were a net negative in my humble opinion. I was glad the consensus was to stop them after the final try at RandomX. And that we felt the need to call the hard forks "network upgrades" was sort of proof that we knew we were doing something that is anti-decentralization for the tradeoff of defeating ASICS. As much as I loved taking out bitmain on that first algorithm tweak, it was a bit of a defeat to keep doing that.
We basically switched to the term scheduled network upgrade, because people associated the term hard-fork with a chain split that would create a new coin (and thus holders would be eligible for some kind of dividend). There used to be tons of questions on Reddit whether users would be getting some kind of dividend / new coin. Wait so are we not doing it biannually anymore? I do like the terminology “network upgrade” too. The idea is to merely perform a scheduled protocol upgrade when it is needed (i.e. there are significant consensus changes). I guess, in practice, this implies forking every nine to twelve months. The six months forks were, in my opinion, too much of a strain on the ecosystem, even if they don't include a PoW change. |
|
|
|
he bi yearly forks were a net negative in my humble opinion. I was glad the consensus was to stop them after the final try at RandomX. And that we felt the need to call the hard forks "network upgrades" was sort of proof that we knew we were doing something that is anti-decentralization for the tradeoff of defeating ASICS. As much as I loved taking out bitmain on that first algorithm tweak, it was a bit of a defeat to keep doing that.
We basically switched to the term scheduled network upgrade, because people associated the term hard-fork with a chain split that would create a new coin (and thus holders would be eligible for some kind of dividend). There used to be tons of questions on Reddit whether users would be getting some kind of dividend / new coin. |
|
|
|
Good to hear DStefanov and thanks for confirming.
Can you perhaps explain dEBRUYNE why in this case being connected to a remote node has a different result than being connected to your own?
The amount of inputs a transaction can use is limited in case of utilizing a remote node (I do not remember the exact reason off the top of my hat). No such limit is in place in case of using a local node. Note that the threshold is quite high and is typically not reached by a user, especially after RingCT was introduced. |
|
|
|
Everything happened as you wrote. I managed to transfer all the coins to the exchange.
Thanks a lot @dEBRUYNE.
Glad to hear it resolved your issue and you're welcome. |
|
|
|
I understand, but the "sweep" option is activated !!! I guess everyone sees this !!! In my case, what else should I do? When I press the "sweep" button it gives me this error: Can anyone describe step by step what I need to do to withdraw funds from this damn wallet? The error message shows that the 'unmixable' outputs you possess can only be transferred whilst using a local node. Which operating system are you using? Then I can provide specific instructions. The operating system I use is Windows 10 Pro x64. Thank you in advance @dEBRUYNE. Try these steps: 1. Close all Monero related software. 2. Reboot your system. 3. Open monerod.exe 4. This will start the sync of the local node. You can type status into the command prompt window to get a status overview. If you have to exit the software, make sure to type exit in order to stop it gracefully. 5. Note that you can sync periodically. The sync will simply pick up where it left off. 6. Once you are fully synced, you can open the GUI (the GUI will automatically connect to the daemon (monerod) that is running separately). 7. You should now be able to perform your transaction. Let me know if you have any further questions. Thank you for the instructions. I let it sync, but obviously it will take a long time. The only thing that impressed me was that monerod.exe had to run it as an administrator. Once it syncs I will write what I did Thanks a lot @dEBRUYNE. You're welcome and let me know if you need any further assistance. |
|
|
|
I understand, but the "sweep" option is activated !!! I guess everyone sees this !!! In my case, what else should I do? When I press the "sweep" button it gives me this error: Can anyone describe step by step what I need to do to withdraw funds from this damn wallet? The error message shows that the 'unmixable' outputs you possess can only be transferred whilst using a local node. Which operating system are you using? Then I can provide specific instructions. The operating system I use is Windows 10 Pro x64. Thank you in advance @dEBRUYNE. Try these steps: 1. Close all Monero related software. 2. Reboot your system. 3. Open monerod.exe 4. This will start the sync of the local node. You can type status into the command prompt window to get a status overview. If you have to exit the software, make sure to type exit in order to stop it gracefully. 5. Note that you can sync periodically. The sync will simply pick up where it left off. 6. Once you are fully synced, you can open the GUI (the GUI will automatically connect to the daemon (monerod) that is running separately). 7. You should now be able to perform your transaction. Let me know if you have any further questions. |
|
|
|
I understand, but the "sweep" option is activated !!! I guess everyone sees this !!! In my case, what else should I do? When I press the "sweep" button it gives me this error:  Can anyone describe step by step what I need to do to withdraw funds from this damn wallet? The error message shows that the 'unmixable' outputs you possess can only be transferred whilst using a local node. Which operating system are you using? Then I can provide specific instructions. |
|
|
|
@Phishead, It important to go beyond surface research about crypto but diversfy investment others coin to make short term profit is not a bad idea if an investor know how to keep his fund safe.
When will Monero 0.16.0.0 Nitrogen Nebula be activate?
#I respect XMR 🎓
The CLI release binaries for v0.16 have already been published on the website. GUI v0.16 is forthcoming. |
|
|
|
Why don't you upgrade to 15.0.5  Didn't know there was a new version! Thanks for telling me, upgraded and running 15.0.5 now. I guess it wasn't publicized because it's not a hard fork? There have been announcements regarding the new point release. However, you may have missed them. |
|
|
|
This probably isn't a problem, but thought I'd ask anyway. I'm curious what makes monerod print this error. I am using --prune-blockchain 2020-04-20 08:56:45.483 W [51.77.152.156:28414 INC] peer claims higher version that we think (13 for 2063919 instead of 12) - we may
be forked from the network and a software upgrade may be needed
2020-04-20 09:04:57.918 I Last scheduled hard fork time suggests a daemon update will be released within the next couple months.
2020-04-20 09:09:43.044 W [51.77.152.156:29878 INC] peer claims higher version that we think (13 for 2063919 instead of 12) - we may
be forked from the network and a software upgrade may be needed
and it continued printing that error over and over again. I exited the daemon and started it again, no error this time. I am running $ monerod --version
Monero 'Carbon Chamaeleon' (v0.15.0.1-release) You can safely ignore the message as long as you are running one of the v0.15 release versions (which you are). |
|
|
|
|
Show Posts
