p2pool-rav
p2pool-rav copied to clipboard
Rav3nPL
[MOON] RPC-connection
Hi Rav3nPL,
could I ask you to help Mooncoin again with tuning p2pool-rav according to the new wallet/client? That would be great.
The new wallet ( --> https://github.com/mooncoincore/wallet ) was compiled and installed alongside a freshly cloned p2pool-rav. But obviously an RPC-call is not possible.
I have found this one: https://github.com/litecoin-project/litecoin/issues/371 where the user also has problems with the latest Litecoin-wallet to make it possible to work together with a p2pool-code. Since the newest Mooncoin-wallet is based on the latest Litecoin (as far as I know), could it be, that the linked solution would work in your p2pool-version for Mooncoin, too? See here: https://github.com/ilsawa/p2pool-ltc/commit/2af67a8cc7d0c498479f080f0652e02c4c826497
Since I don't know what the correct value for the Mooncoin-genesis-block would be, could you test that and possibly change the relevant passages in your pool-script to be correct? That would be really nice.
Notice: The new dev has changed back to the "official" naming conventions, meaning, that the paths that the Mooncoin-wallet creates, are with small letters again. Maybe this is of help for your updates of the code.
Thank you very much.
RPC command "help" is no longer throwing back required string. I`ll try t change it to check for genesis block hash (like in BTC some time ago).
try https://github.com/Rav3nPL/p2pool-rav/commit/9a00696c40126d0a16c176e4f0bc16ea2cb44feb
Just cloned again freshly. Then starting p2pool it gives me: ... yield helper.check_genesis_block(bitcoind, 'bd687cbbac4842724d4b1dfd2e1a6ce35d765db05635b3ebd3810ba66ac5aee9'))) ^ SyntaxError: invalid syntax ...
I`ll check it later, probably missing comma or smth.
2017-12-18 17:02 GMT+01:00 coinflow [email protected]:
Just cloned again freshly. Then starting p2pool it gives me: ... yield helper.check_genesis_block(bitcoind, 'bd687cbbac4842724d4b1dfd2e1a6c e35d765db05635b3ebd3810ba66ac5aee9'))) ^ SyntaxError: invalid syntax ...
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Rav3nPL/p2pool-rav/issues/105#issuecomment-352470832, or mute the thread https://github.com/notifications/unsubscribe-auth/ABCxi_sJez_1LehiL_czQ16f-Cx8GhHEks5tBoyGgaJpZM4RFivP .
This seems to work:
RPC_CHECK = defer.inlineCallbacks(lambda bitcoind: defer.returnValue( (yield helper.check_genesis_block(bitcoind, 'bd687cbbac4842724d4b1dfd2e1a6ce35d765db05635b3ebd3810ba66ac5aee9')) )) SUBSIDY_FUNC = lambda height: 2000000*100000000
So the problem was obviously in number and position of the brackets.
Could you consolidate the networks-files for Mooncoin? In ../p2pool/bitcoin/networks there are Mooncoin.py and mooncoin.py (and *.pyc) Also both versions in ../p2pool/networks
So it would be great to have this consolidated based on mooncoin.py, I assume?
Changed brackets https://github.com/Rav3nPL/p2pool-rav/commit/c78d7f2c6b67f83a97af97031bbe7104e87079b3 Two Mooncoin.py are necessary, this is how p2pool is build. One is for daemon data, second to pool data.
Done. It was because at some point I do commit from Windoze, it is case-insensitive ;]
I tried using the new mooncoin.py and recomplied but I am getting crazy DOA shares, and my miner is showing that I found 70,000 Blocks, and then my time to block is showing 14038880326535135797651516507108282486575107470786560.0 years Something isn't working, any thoughts?
still not working, and I have a lot of people that would like to use or create Mooncoin Nodes. Can we do some testing?
Hi gblass,
do you mean the miner found 70000 blocks, or shares? A very high rate of DOA-shares at the beginning is normal. That should level out over time. At least here it is.
Have you opened the relevant ports (see the code), so that your node can connect with others and get in sync?
The time to block is indeed strange, but I assumed, that is normal, if the sharechain is new/reset and the first block not found already ...??
Rav3nPL? What are your thoughts? Could you set up a test node and connect to the Mooncoin P2Pool, in order to check whether everything runs correctly?
I'll try to run mooncoin node (core and p2pool) today. Will see.
27.12.2017 9:36 AM "coinflow" [email protected] napisał(a):
Maybe the same problem like here: #106 https://github.com/Rav3nPL/p2pool-rav/issues/106 ?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Rav3nPL/p2pool-rav/issues/105#issuecomment-354076123, or mute the thread https://github.com/notifications/unsubscribe-auth/ABCxiyjgYjA7I0SmOpXHenDNQ6bBEZFPks5tEgGNgaJpZM4RFivP .
@Rav3nPL Hi, I'm Vassilis the new official mooncoin dev. if you need any help I'm here! My email also is [email protected]!
if you are with just a software miner everything is fine.. if you connect with antminer(support Scrypt) for example (500MH/s) in few secs.. in miner status page you got few thousands "Found Blocks". @coinflow do you get any real blocks as pool?
Just updated repo, It is working on my side, connected to 3 P2Pool peers, reorganized sharechain. Try pull and restart pool and miners. At start it WILL throw wazillion DOA shares, until it adjust diff to miner. My node: http://rav3n.dtdns.net:9664
2017-12-27 22:37:30.822790 P2Pool: 3531 shares in chain (1795 verified/3532 total) Peers: 3 (2 incoming)
2017-12-27 21:37:48 UpdateTip: hash=3faf50b0d.. height=1179321 diff=1b404e86 algo=scrypt ver=0x00000001 log2_work=57.365018 tx=2032684 date='2017-12-27 21:40:05' prog=1.000015 cache=43.6MiB(193623tx)
I just connected my antminer to test. Still getting tons of found block son the miner.
Miner is probably interpreting accepted shares as blocks found. Or maybe something in diff reporting on pool side.
its antminer L3+ 505MH/s its connected on raven test pool http://rav3n.dtdns.net:9664
Pool log:
2017-12-27 22:50:27.378941 P2Pool: 3564 shares in chain (1829 verified/3566 total) Peers: 3 (2 incoming)
2017-12-27 22:50:27.379072 Local: 458MH/s in last 10.0 minutes Local dead on arrival: ~1.5% (1-3%) Expected time to share: 1.8 minutes
2017-12-27 22:50:27.379105 Shares: 8 (0 orphan, 0 dead) Stale rate: ~0.0% (0-33%) Efficiency: ~171.5% (115-172%) Current payout: (0.0000)=0.0000 MOON
2017-12-27 22:50:27.379139 Pool: 1348MH/s Stale rate: 41.7% Expected time to block: 5396623891178943933527132785432502450478847480561664.0 years
2017-12-27 22:50:30.389047 P2Pool: 3564 shares in chain (1829 verified/3566 total) Peers: 3 (2 incoming)
2017-12-27 22:50:30.389181 Local: 461MH/s in last 10.0 minutes Local dead on arrival: ~1.5% (1-3%) Expected time to share: 1.8 minutes
2017-12-27 22:50:30.389214 Shares: 8 (0 orphan, 0 dead) Stale rate: ~0.0% (0-33%) Efficiency: ~171.5% (115-172%) Current payout: (0.0000)=0.0000 MOON
2017-12-27 22:50:30.389247 Pool: 1348MH/s Stale rate: 41.7% Expected time to block: 5396623891178943933527132785432502450478847480561664.0 years
Block ETA is odd, need look into current P2Pool LTC code, maybe I`m missing something.
Well, I`m not 100% sure but this code is basing on older P2Pool, it is not prepared for SegWit and it can produce invalid blocks... We need hit at least one block to verify that, probably I need to move to new P2Pool code base that supports SegWit.
@coinflow do you get any real blocks as pool?
Not with the new wallet yet. With the older ones we found a lot of blocks. The last block was this one: https://chainz.cryptoid.info/moon/block.dws?1151546.htm See here for further stats of P2Pool-blocks: https://chainz.cryptoid.info/moon/extraction.dws?1.htm
I can confirm with @coinflow we used to get blocks often, nothing since use of the new wallet.
If no one mine coin I can't resolve anything. My node will be up few more days. If no one use this P2Pool I'll kill it.
Do you want me to reconnect? I dont mind, but I have ran this one on my own node for almost 24 hours and no change.
Please let me know
Sent from my iPhone
On Dec 28, 2017, at 11:08 AM, Rav3nPL [email protected] wrote:
If no one mine coin I can't resolve anything. My node will be up few more days. If no one use this P2Pool I'll kill it.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
https://bitcointalk.org/index.php?topic=1733963.msg27112792#msg27112792 Hopefully some miners will find the way to your node, Rav3nPL.