jtgrassie / monero-pool

A Monero mining pool server written in C
BSD 3-Clause "New" or "Revised" License
344 stars 125 forks source link

more info on configure #6

Closed edwardgug closed 5 years ago

edwardgug commented 5 years ago

hey JT great work! I've broken a block with 30mh

I was wondering about some further details on pool.conf

Can we get a breakdown of the settings? If you post I'll send you some xmr as a thanks

Ed

jtgrassie commented 5 years ago

Thank you.

setting description
pool-port the port your miners connect to
rpc-host the IP of your monerod
rpc-port the daemon RPC port
rpc-timeout timeout in seconds for daemon RPC calls
wallet-rpc-host the IP of your monero-wallet-rpc
wallet-rpc-port the port of your monero-wallet-rpc
pool-wallet the monero address of your pool wallet (the wallet loaded in your monero-wallet-rpc)
pool-start-diff the initial target for new miner connections
share-mul the PPLNS share multiplier
pool-fee fee deducted for the pool from any mined blocks
payment-threshold minimum XMR a miner has to accumulate before the pool pays them
log-level log level (0 least logging to 5 most logging)
webui-port the port of the pools web interface
edwardgug commented 5 years ago

paying today, last question - is there a way to increase the block size submission?

Ed

jtgrassie commented 5 years ago

Thanks.

is there a way to increase the block size submission?

Can you explain? I'm not quite understanding the question. Do you mean have the pool create bigger blocks (i.e. stuff in more transactions than default)?

edwardgug commented 5 years ago

Sorry, not an expert by any means - but I believe block sizes can be increased when mining and you pay a penalty if the block is submitted (the reward is less).

jtgrassie commented 5 years ago

The pool uses the daemons get_block_template method which builds the optimal size of the block (e.g. to not incur penalty and maximize amount of txs included).

edwardgug commented 5 years ago

thanks, sorry I haven't sent you that xmr yet. Will do, just crazy busy here. I'll send a couple of payments, keep up the great work :)

jtgrassie commented 5 years ago

Thank you, much appreciated.

edwardgug commented 5 years ago

I just sent through another payment as we broke another block. Thanks, dude. I am running mine on a supercomputer so the monerod daemon passes the blocks straight to the gpus on the same machine, no network delay. The block notified function really helps. I think block submission time is often overlooked by devs so good work on that. Keep up the great work, we will test any new features and share the results (and some of the profits) with you!

jtgrassie commented 5 years ago

Thank you again!

edwardgug commented 5 years ago

No dramas, as a suggestion could you look at the block submission size. Again not my area of full understanding - but I believe we miners can submit larger blocks and pay a penalty for doing so. The benefit being that there is an increased chance of block approval. This might be something I can do at the Monerod Daemon but the documentation is lacking and it isn't completely clear how to do this.

Also, seeing that you are such a genius at his stuff, at miner that connect straight to the daemon would also theoretically help to distribute hashes more evenly. I think most people aren't willing to go the distance on building their own pool.

Ed

jtgrassie commented 5 years ago

Hey Ed,

but I believe we miners can submit larger blocks and pay a penalty for doing so

This is correct.

The benefit being that there is an increased chance of block approval.

This is incorrect. The highest difficulty and earliest time submitted has the highest chance of getting accepted onto the main chain, and thus rewarded. Size of the block is irrelevant other than deciding if a penalty should be issued.

There is thus no benefit to creating bigger blocks than the network is expecting. Only a downside of less reward ;)

btw I can chat on IRC or email, better than here on an issue thread ;)

edwardgug commented 5 years ago

Oh great, What is your handle? You don't use Signal messenger by any chance do you? Ed

HotSwapp commented 3 years ago

Thank you.

setting description pool-port the port your miners connect to rpc-host the IP of your monerod rpc-port the daemon RPC port rpc-timeout timeout in seconds for daemon RPC calls wallet-rpc-host the IP of your monero-wallet-rpc wallet-rpc-port the port of your monero-wallet-rpc pool-wallet the monero address of your pool wallet (the wallet loaded in your monero-wallet-rpc) pool-start-diff the initial target for new miner connections share-mul the PPLNS share multiplier pool-fee fee deducted for the pool from any mined blocks payment-threshold minimum XMR a miner has to accumulate before the pool pays them log-level log level (0 least logging to 5 most logging) webui-port the port of the pools web interface

I would highly suggest putting this all in the readme file.