[XMR] Monero - A secure, private, untraceable cryptocurrency

[jamieb81]

Hmm Installed the wallet and the bat file, wallet starts but cannot make it to mine, I get error refresh failed : deamon is busy please try later
blocks received 0

Ok just saw someone else with the same problem.

so basically just have to wait?

[1713505400]

1713505400

[1713505400]

1713505400

[1713505400]

1713505400

[1713505400]

1713505400

[tacotime]

Hmm Installed the wallet and the bat file, wallet starts but cannot make it to mine, I get error refresh failed : deamon is busy please try later
blocks received 0

Ok just saw someone else with the same problem.

so basically just have to wait?

you need to wait for the network to synchronize, in the daemon type "set_log 1" and you can see what height you're currently on, synced is height 10000+

[mickey_miner]

Wallet:
Error: refresh failed: daemon is busy. Please try later. Blocks received: 0

bitmonerod:

set_log 1 active and it downloading blocks, how long do I have to wait to refresh and/or start mining?

You must wait until sync finish.  You will get message in bitmonerod:

You are now synchronized with the network. You may now start simplewallet.

Please note, that the blockchain will be saved only after you quit the daemon wi
th "exit" command or if you use "save" command.
Otherwise, you will possibly need to synchronize the blockchain again.

Then you start wallet and mining.

Remember to type save in bitmonerod after sync to write blockchain to hard drive and use exit in bitmonerod when closing to save blockchain on hard drive.  It does not write to hard drive automatic.

[jamieb81]

so it seems to be doing something,

is this good :




Edit : from 11 days behind now 10 days behind, this is going to take a while heheh

[eizh]

Edit : from 11 days behind now 10 days behind, this is going to take a while heheh

By the way, this is a bug (the estimate is double the actual time). This coin was launched on April 18, which you can check on the blockchain timestamps after synchornizing.

[jamieb81]

Edit : from 11 days behind now 10 days behind, this is going to take a while heheh

By the way, this is a bug (the estimate is double the actual time). This coin was launched on April 18, which you can check on the blockchain timestamps after synchornizing.

oh well, at least I got it to work, let's see if after downloading it will mine something.

[smooth]

One minute blocks that are of size ~1 KB (most of the blocks right now) double the likelihood of a miner getting a block. Selfish mining only becomes a severe issue when blocksize becomes large.

You're the one who is concerned about the reward being too small in 10-20 years??!!

Obviously the goal is to create a design that is sound for the long term, not focus on a couple of weeks of easy mining when there are hardly any transactions on the network. As was pointed out before, solo mining for small (one computer) miners will sooner or later (most likely sooner) become non-viable whether blocks are one minute or two minute blocks. Maybe not in the first week, but if the coin thrives, it won't be long at all. This was a very short-sighted reason to speed up the blocks.

I'm not referring to selfish mining in any case, just regular (random) orphans. If it takes 3 seconds to propagate a block across the network, then with 60 second blocks you will have about 5% random orphans (where two different people solve a block at the same time; only one will survive). This gets much worse when the blocks get bigger (take longer to verify and forward at each hop). If it takes 10 seconds to propagate you are looking at 16% orphans.

Pools reduce orphans by concentrating hash rate and directly communicating with the hashers in a star pattern instead of a p2p. You won't be solving a block at the same time as one of your pool-mates very often (due to longpoll/stratum) and the pool will solve on top of its own blocks more quickly than any foreign blocks, so it will win more races. These effects combine to give pools a huge economy of scale.

Even with those 1k blocks you describe, there are already plenty of orphans, just look at the daemon output. Bytecoin with 2 minute blocks still has a lot of orphans too.

Satoshi was no idiot when he picked 10 minutes, and didn't just pull that number out of his ass. That may be slight overkill but 1 minute is going way too far in the other direction.

[surfer43]

Code:

$ tsocks ssh -N -f -D 18080 user@myIP

$ ./bitmonerod

2014-Apr-25 14:51:39.170760 Initializing p2p server...
2014-Apr-25 14:51:39.170951 Binding on 0.0.0.0:18080
... what=bind: Address already in use

How can I reverse tunnel with Monero?

[smooth]

Looks like I have hundreds of outgoing connections, most of them to the same place. Anybody else seeing this:

Small subset shown below. This is the output from print_cn

Code:

[OUT]27.32.51.54:18080   0                   71(292501)/43(292502)    state_befor_handshake    292502              
[OUT]27.32.51.54:18080   0                   71(275834)/43(275835)    state_befor_handshake    275835              
[OUT]27.32.51.54:18080   0                   71(301611)/43(301612)    state_befor_handshake    301612              
[OUT]27.32.51.54:18080   0                   71(266446)/43(266447)    state_befor_handshake    266447              
[OUT]27.32.51.54:18080   0                   71(328905)/43(328906)    state_befor_handshake    328906              
[OUT]27.32.51.54:18080   0                   71(263989)/43(263990)    state_befor_handshake    263990              
[OUT]27.32.51.54:18080   0                   71(261053)/43(261053)    state_befor_handshake    261053              
[OUT]27.32.51.54:18080   0                   71(248175)/43(248176)    state_befor_handshake    248176              
[OUT]27.32.51.54:18080   0                   71(337317)/43(337317)    state_befor_handshake    337317              
[OUT]27.32.51.54:18080   0                   71(249778)/43(249779)    state_befor_handshake    249779              
[OUT]27.32.51.54:18080   0                   71(325645)/43(325646)    state_befor_handshake    325646              
[OUT]27.32.51.54:18080   0                   71(250469)/43(250470)    state_befor_handshake    250470              
[OUT]27.32.51.54:18080   0                   71(327231)/43(327232)    state_befor_handshake    327232              
[OUT]27.32.51.54:18080   0                   71(328115)/43(328116)    state_befor_handshake    328116              
[OUT]27.32.51.54:18080   0                   71(284679)/43(284680)    state_befor_handshake    284680              
[OUT]27.32.51.54:18080   0                   71(244825)/43(244825)    state_befor_handshake    244825              
[OUT]27.32.51.54:18080   0                   71(334726)/43(334726)    state_befor_handshake    334726              
[OUT]27.32.51.54:18080   0                   71(269099)/43(269099)    state_befor_handshake    269099              
[OUT]27.32.51.54:18080   0                   71(326648)/43(326649)    state_befor_handshake    326649              
[OUT]27.32.51.54:18080   0                   71(272517)/43(272518)    state_befor_handshake    272518              
[OUT]27.32.51.54:18080   0                   71(245019)/43(245019)    state_befor_handshake    245019      

[mickey_miner]

Looks like I have hundreds of outgoing connections, most of them to the same place. Anybody else seeing this:

Small subset shown below. This is the output from print_cn

Code:

[OUT]27.32.51.54:18080   0                   71(292501)/43(292502)    state_befor_handshake    292502              
[OUT]27.32.51.54:18080   0                   71(275834)/43(275835)    state_befor_handshake    275835              
[OUT]27.32.51.54:18080   0                   71(301611)/43(301612)    state_befor_handshake    301612              
[OUT]27.32.51.54:18080   0                   71(266446)/43(266447)    state_befor_handshake    266447              
[OUT]27.32.51.54:18080   0                   71(328905)/43(328906)    state_befor_handshake    328906              
[OUT]27.32.51.54:18080   0                   71(263989)/43(263990)    state_befor_handshake    263990              
[OUT]27.32.51.54:18080   0                   71(261053)/43(261053)    state_befor_handshake    261053              
[OUT]27.32.51.54:18080   0                   71(248175)/43(248176)    state_befor_handshake    248176              
[OUT]27.32.51.54:18080   0                   71(337317)/43(337317)    state_befor_handshake    337317              
[OUT]27.32.51.54:18080   0                   71(249778)/43(249779)    state_befor_handshake    249779              
[OUT]27.32.51.54:18080   0                   71(325645)/43(325646)    state_befor_handshake    325646              
[OUT]27.32.51.54:18080   0                   71(250469)/43(250470)    state_befor_handshake    250470              
[OUT]27.32.51.54:18080   0                   71(327231)/43(327232)    state_befor_handshake    327232              
[OUT]27.32.51.54:18080   0                   71(328115)/43(328116)    state_befor_handshake    328116              
[OUT]27.32.51.54:18080   0                   71(284679)/43(284680)    state_befor_handshake    284680              
[OUT]27.32.51.54:18080   0                   71(244825)/43(244825)    state_befor_handshake    244825              
[OUT]27.32.51.54:18080   0                   71(334726)/43(334726)    state_befor_handshake    334726              
[OUT]27.32.51.54:18080   0                   71(269099)/43(269099)    state_befor_handshake    269099              
[OUT]27.32.51.54:18080   0                   71(326648)/43(326649)    state_befor_handshake    326649              
[OUT]27.32.51.54:18080   0                   71(272517)/43(272518)    state_befor_handshake    272518              
[OUT]27.32.51.54:18080   0                   71(245019)/43(245019)    state_befor_handshake    245019      

That not what I see. 

[Coodex]

I can't seem to be able to paste the address into the daemon to start mining.

Is there a way to do this without entering the address manually? :S

EDIT:

Started mining from wallet lol

[smooth]

I can't seem to be able to paste the address into the daemon to start mining.

Is there a way to do this without entering the address manually? :S

You can start the mining from the wallet without needing to type your address

[tacotime]

Code:

$ tsocks ssh -N -f -D 18080 user@myIP

$ ./bitmonerod

2014-Apr-25 14:51:39.170760 Initializing p2p server...
2014-Apr-25 14:51:39.170951 Binding on 0.0.0.0:18080
... what=bind: Address already in use

How can I reverse tunnel with Monero?

You need to bind it for the daemon separately, see the arguments you can give it from --help

[mickey_miner]

I can't seem to be able to paste the address into the daemon to start mining.

Is there a way to do this without entering the address manually? :S

You can start the mining from the wallet without needing to type your address

Yes.  Just "start_mining" from wallet after bitmonerod sync and wallet is running.

[Coodex]

Getting 8.5 hash rate per thread (total 12 threads) is that good?

[smooth]

Getting 8.5 hash rate per thread (total 12 threads) is that good?

That sounds extremely high to me. What output do you get from show_hr?

[Coodex]

Getting 8.5 hash rate per thread (total 12 threads) is that good?

That sounds extremely high to me. What output do you get from show_hr?

https://i.imgur.com/JZHOIjl.png

Hexacore i7 4930k

or am I getting 8.5ish in total ?

[smooth]

I think that is your total hash rate (all threads combined), but I'm not positive.

BTW, use "hide_hr" to turn off the display if you don't know that.

[Coodex]

I think that is your total hash rate (all threads combined), but I'm not positive.

BTW, use "hide_hr" to turn off the display if you don't know that.

Thanks, didn't know that.

I was actually running 10 threads, almost 10 hash rate with all threads now

https://i.imgur.com/ddj0Zeh.png

[mickey_miner]

Getting 8.5 hash rate per thread (total 12 threads) is that good?

That sounds extremely high to me. What output do you get from show_hr?

Hexacore i7 4930k

or am I getting 8.5ish in total ?

That is total. Not bad.  Should find blocks.