Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 632. (Read 4670673 times)
This coin needs some promotion or a killer app, being only anon worked before but now it needs something new. Its undervalued despite how good it is.. The best crypto note project.
Could someone explain me what this means???
I upgraded to 0.9.2 on Linux 64bit and get the following WARNING/ERROR on the daemon.
I upgraded to 0.9.2 on Linux 64bit and get the following WARNING/ERROR on the daemon.
Code:
2016-Mar-21 21:52:11.035195 [P2P9]
**********************************************************************
Last scheduled hard fork time shows a daemon update is needed now.
**********************************************************************
**********************************************************************
Last scheduled hard fork time shows a daemon update is needed now.
**********************************************************************
Code:
./bitmonerod --version
Creating the logger system
Monero 'Hydrogen Helix' (v0.9.2.0-release)
Creating the logger system
Monero 'Hydrogen Helix' (v0.9.2.0-release)
In general, external nodes are frowned upon....by The Protocol. We don't want to create a culture where people connect to remote nodes for convenience. This leads to centralization, much like some bitcoiners use electrum without even realizing they're not running bitcoin. Running a node isn't that much of a bitch right now. It just requires patience. And honestly, whats the rush to get access to your coinz? Sync the blockchain. Be your own bank.
That actually makes a Lot of sense, thanks for sharing your thoughts.
Maybe I rushed into it a bit too quickly, eager to have the nodes I am running used to it's full potential. Will reverse the settings I did, as well since the option is already there if people want to through Moneroclub.com
I don't care about privacy i just don't know if that makes it possible for someone to steal my coins or not
Your coins are safe using a remote node. Take it for what it's worth from a random internet person.
I can't get it to work yet with the node I suggested. However this node from Moneroclub.com does work as an external node, just tested it myself:
Code:
simplewallet.exe --daemon-host node.moneroclub.com --daemon-port 8880
I am asking for help in the in the Monero Support topic from anyone that can help me figure out what else I need to configure to be able to act as an 'external node'.
In general, external nodes are frowned upon....by The Protocol. We don't want to create a culture where people connect to remote nodes for convenience. This leads to centralization, much like some bitcoiners use electrum without even realizing they're not running bitcoin. Running a node isn't that much of a bitch right now. It just requires patience. And honestly, whats the rush to get access to your coinz? Sync the blockchain. Be your own bank.
When you say "can't get it to work", did you open up 18081 in the firewall?
Additionally, if you continue down this route, there are other flags that are useful when opening your port. For instance, if someone connects via simplewallet to your node, they can initiate mining unless you have it disabled... i dunno what the flag is off the top of my head. --limited-rpc or something.
Ultimately the "slow initial use experience" is something that plagues ALL cryptocurrencies (unless you use second tier "fixes"). I'm hoping to put together a cogent "ideas" post in the getmonero forum that will hopefully attract a developer for the whole headers first, reverse blockchain dload, then reverse wallet refresh approach for enhancing the "first impressions" experience ...
I don't care about privacy i just don't know if that makes it possible for someone to steal my coins or not
Your coins are safe using a remote node. Take it for what it's worth from a random internet person.
I can't get it to work yet with the node I suggested. However this node from Moneroclub.com does work as an external node, just tested it myself:
Code:
simplewallet.exe --daemon-host node.moneroclub.com --daemon-port 8880
I am asking for help in the Monero Support topic from anyone that can help me figure out what else I need to configure to be able to act as an 'external node'.
Your coins are safe using a remote node. Take it for what it's worth from a random internet person.
I think 18080 is for p2p, whereas 18081 is for RPC. Also, you will need to make sure that 18081 is open on your server.
Thanks GingerAle, learning every day. Opened port 18081 on the node as well, please give it a try parker928.
Windows:
Code:
simplewallet.exe --daemon-host 185.112.158.127:18081
Linux:
Code:
./simplewallet --daemon-host 185.112.158.127:18081
I type that in the command line? without having simple wallet open and the daemon open? or does the daemon already have to be running
Type in the command line with neither simplewallet or bitmonerod running. That command will open simplewallet and tell it to use a remote daemon, so you don't need to run bitmonerod on your comp at all. (This does degrade your privacy a bit.)
I don't care about privacy i just don't know if that makes it possible for someone to steal my coins or not
I think 18080 is for p2p, whereas 18081 is for RPC. Also, you will need to make sure that 18081 is open on your server.
Thanks GingerAle, learning every day. Opened port 18081 on the node as well, please give it a try parker928.
Windows:
Code:
simplewallet.exe --daemon-host 185.112.158.127:18081
Linux:
Code:
./simplewallet --daemon-host 185.112.158.127:18081
I type that in the command line? without having simple wallet open and the daemon open? or does the daemon already have to be running
Type in the command line with neither simplewallet or bitmonerod running. That command will open simplewallet and tell it to use a remote daemon, so you don't need to run bitmonerod on your comp at all. (This does degrade your privacy a bit.)
I think 18080 is for p2p, whereas 18081 is for RPC. Also, you will need to make sure that 18081 is open on your server.
Thanks GingerAle, learning every day. Opened port 18081 on the node as well, please give it a try parker928.
Windows:
Code:
simplewallet.exe --daemon-host 185.112.158.127:18081
Linux:
Code:
./simplewallet --daemon-host 185.112.158.127:18081
I type that in the command line? without having simple wallet open and the daemon open? or does the daemon already have to be running
I think 18080 is for p2p, whereas 18081 is for RPC. Also, you will need to make sure that 18081 is open on your server.
Thanks GingerAle, learning every day. Opened port 18081 on the node as well, please give it a try parker928.
Windows:
Code:
simplewallet.exe --daemon-host 185.112.158.127:18081
Linux:
Code:
./simplewallet --daemon-host 185.112.158.127:18081
You can also use simplewallet with a remote node which should be much faster than syncing a daemon from scratch. Someone else would have to provide some names/addresses for remote-capable nodes.
Since luigi1111 made this node possible for another month, I take the liberty of offering his node
.I think it works like this:
Windows:
Code:
simplewallet.exe --daemon-host 185.112.158.127:18080
Linux:
Code:
./simplewallet --daemon-host 185.112.158.127:18080
I think 18080 is for p2p, whereas 18081 is for RPC. Also, you will need to make sure that 18081 is open on your server.
You can also use simplewallet with a remote node which should be much faster than syncing a daemon from scratch. Someone else would have to provide some names/addresses for remote-capable nodes.
Since luigi1111 made this node possible for another month, I take the liberty of offering his node
.I think it works like this:
Windows:
Code:
simplewallet.exe --daemon-host 185.112.158.127:18080
Linux:
Code:
./simplewallet --daemon-host 185.112.158.127:18080
When starting bitmonerod, the message is shown.
I thought this update would do it.
What should I do?
Quote
Last scheduled hard fork time shows a daemon update is needed now.
I thought this update would do it.
Quote
What should I do?
I just started getting the same message. I believe it was mentioned that this message is a bug and there is nothing that needs to be done. Also there is a release due out today that will address this and a few other things.
Well ok.
The synchronization has anyway been very slow. Before and after last update. It takes easily half an hour or more to sync just one days blocks. Has anyone else this problem?
mine is very slow too i have the 9.2 on a capable machine and it looks like at this rate i won't be done for about 3 days.
To all mods/devs...can someone please give a little bit more specific information on how to use the bootstrap download? i downloaded it but I don't know how to open it or what directory it should be in. I do not know how to code or use command line :/
It seems I am not the only one who feels like they are unable to access their coins despite doing everything right. hopefully one of you hero members or more experienced users can write a dummy's guide or something because this is just a little too complicated lol. I was smart enough to build an 8 gpu mining setup but somehow i have trouble with monero hahaha
A "capable machine" doesn't take 3 days to sync. Mine takes just over an hour.
I'm guessing using the import isn't going to be significantly faster than syncing. If you really want to try it, please join #monero on freenode and people there can work with you on it much more quickly than this back and forth via forum posts. https://webchat.freenode.net/
You can also use simplewallet with a remote node which should be much faster than syncing a daemon from scratch. Someone else would have to provide some names/addresses for remote-capable nodes.
I'm just going to wait for it to sync. thanks lol
When starting bitmonerod, the message is shown.
I thought this update would do it.
What should I do?
Quote
Last scheduled hard fork time shows a daemon update is needed now.
I thought this update would do it.
Quote
What should I do?
I just started getting the same message. I believe it was mentioned that this message is a bug and there is nothing that needs to be done. Also there is a release due out today that will address this and a few other things.
Well ok.
The synchronization has anyway been very slow. Before and after last update. It takes easily half an hour or more to sync just one days blocks. Has anyone else this problem?
mine is very slow too i have the 9.2 on a capable machine and it looks like at this rate i won't be done for about 3 days.
To all mods/devs...can someone please give a little bit more specific information on how to use the bootstrap download? i downloaded it but I don't know how to open it or what directory it should be in. I do not know how to code or use command line :/
It seems I am not the only one who feels like they are unable to access their coins despite doing everything right. hopefully one of you hero members or more experienced users can write a dummy's guide or something because this is just a little too complicated lol. I was smart enough to build an 8 gpu mining setup but somehow i have trouble with monero hahaha
A "capable machine" doesn't take 3 days to sync. Mine takes just over an hour.
I'm guessing using the import isn't going to be significantly faster than syncing. If you really want to try it, please join #monero on freenode and people there can work with you on it much more quickly than this back and forth via forum posts. https://webchat.freenode.net/
You can also use simplewallet with a remote node which should be much faster than syncing a daemon from scratch. Someone else would have to provide some names/addresses for remote-capable nodes.
Hi! Which miner for XMR the best?
Do you have AES-NI on your CPU?
Wolf's CPU miner
https://ottrbutt.com/cpuminer-multi/cpuminer-multi-wolf-06-09-2014.zip
if not,
I like YAMs
https://mega.co.nz/#F!h0tkXSxZ!f62uoUXogkxQmP2xO8Ib-g
for YAMs, you still have to identify your CPU architecture.
http://stackoverflow.com/questions/10595312/how-to-get-cpus-model-number-like-core-i7-860-on-windows
then google the model # that comes up, and you should be able to figure out if you have ivy bridge, nehalem, core2 etc.
Hi! Which miner for XMR the best?
@parker928
Most likely invalid address means you typed in the address wrong. It is also possible you put the argument in the wrong order.
You should wait for it to finish syncing before trying to transfer though.
Most likely invalid address means you typed in the address wrong. It is also possible you put the argument in the wrong order.
You should wait for it to finish syncing before trying to transfer though.
Thought so. can you please remind me what the exact format is, i forgot where exactly the spaces go or if there are commas and parentheses etc. i have been holding for 18 months so its hard to remember how to work this damn thing
transfer [mixin] address amount [payment-id]
The items in [brackets] are optional.
how do i use -- verify command?
I typed exactly that "--verify 0" and "-verify 0" and "verify 0" none of those helped to speed anything up! i must be missing something
It is used with blockchain_import and the downloaded bootstrap.
blockchain_import --verify 0 blockchain.raw
I think. May be slightly off, in which case hopefully someone will correct it.
I'm not really sure what that means...
You download the file blockchain.raw from getmonero.org. Instead of syncing the daemon, you use the blockchain_import utility to import the raw file. The optional '--verify 0' option makes the process go much faster but skips all safety checks.
If you aren't comfortable with a procedure like this the best thing to do is be patient and let the daemon sync by itself.
EDIT: The correct format for the blockchain_import command (with '--verify 0' added optionally) is
blockchain_import --input-file blockchain.raw
Thanks a lot I can see you're really trying to help. i still can't do it. i'm missing something. can you make a video or something?
When starting bitmonerod, the message is shown.
I thought this update would do it.
What should I do?
Quote
Last scheduled hard fork time shows a daemon update is needed now.
I thought this update would do it.
Quote
What should I do?
I just started getting the same message. I believe it was mentioned that this message is a bug and there is nothing that needs to be done. Also there is a release due out today that will address this and a few other things.
Well ok.
The synchronization has anyway been very slow. Before and after last update. It takes easily half an hour or more to sync just one days blocks. Has anyone else this problem?
mine is very slow too i have the 9.2 on a capable machine and it looks like at this rate i won't be done for about 3 days.
To all mods/devs...can someone please give a little bit more specific information on how to use the bootstrap download? i downloaded it but I don't know how to open it or what directory it should be in. I do not know how to code or use command line :/
It seems I am not the only one who feels like they are unable to access their coins despite doing everything right. hopefully one of you hero members or more experienced users can write a dummy's guide or something because this is just a little too complicated lol. I was smart enough to build an 8 gpu mining setup but somehow i have trouble with monero hahaha
When starting bitmonerod, the message is shown.
I thought this update would do it.
What should I do?
Quote
Last scheduled hard fork time shows a daemon update is needed now.
I thought this update would do it.
Quote
What should I do?
I just started getting the same message. I believe it was mentioned that this message is a bug and there is nothing that needs to be done. Also there is a release due out today that will address this and a few other things.
Well ok.
The synchronization has anyway been very slow. Before and after last update. It takes easily half an hour or more to sync just one days blocks. Has anyone else this problem?
When starting bitmonerod, the message is shown.
I thought this update would do it.
What should I do?
Quote
Last scheduled hard fork time shows a daemon update is needed now.
I thought this update would do it.
Quote
What should I do?
I just started getting the same message. I believe it was mentioned that this message is a bug and there is nothing that needs to be done. Also there is a release due out today that will address this and a few other things.
Jump to: